Заявление о доступности

We believe that civic engagement should be accessible to everyone, regardless of ability. iPetition is designed with accessibility as a core principle, not an afterthought.

Our commitment includes:

• Building with semantic HTML and proper ARIA attributes from the start.
• Testing with screen readers, keyboard-only navigation, and automated accessibility tools.
• Supporting users with visual, motor, auditory, and cognitive disabilities.
• Providing multiple ways to interact with every feature.
• Continuously improving based on user feedback and evolving standards.

The following accessibility features are built into iPetition:

All functionality on iPetition is accessible via keyboard without requiring a mouse:

Petition signing, form submission, navigation, and all interactive features can be completed entirely with keyboard input.

iPetition supports users with visual impairments through:

• Dark and light themes: Toggle between themes using the theme button in the header or in Settings → Appearance. The system preference option automatically matches your OS setting.
• High contrast: All UI elements meet WCAG AA contrast ratios. Status indicators use both color and icons/text (never color alone).
• Scalable interface: The layout is fully responsive and works with browser zoom up to 400%. Text reflows without horizontal scrolling.
• No flashing content: The platform does not contain content that flashes more than three times per second.
• Motion preferences: Animations respect the prefers-reduced-motion media query. Users who prefer reduced motion see static transitions.

iPetition supports 25 languages to ensure civic participation is not limited by language barriers:

English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Russian, Arabic, Chinese, Japanese, Korean, Hindi, Turkish, Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Hungarian, Swedish, Danish, and Urdu.

• RTL support: Full right-to-left layout for Arabic, Hebrew, Farsi, and Urdu, including mirrored navigation, text alignment, and icon positioning.
• Language switching: Available via the language selector in the header on every page. The selected language is stored and persists across sessions.
• Proper HTML lang attribute: The page's lang attribute is set correctly for each locale, enabling screen readers to use the correct pronunciation.

Our mobile applications (iOS and Android) follow platform-specific accessibility guidelines:

• VoiceOver (iOS) and TalkBack (Android): All screens are navigable with screen readers. Interactive elements have accessibility labels and roles.
• Dynamic type: Text sizes respect system font size preferences on both platforms.
• Touch targets: All interactive elements meet the minimum 44x44pt touch target size recommended by WCAG and platform guidelines.
• Haptic feedback: Meaningful haptic responses on supported devices for key actions (signing, submitting).
• Dark mode: Follows system appearance setting with manual override in Settings → Appearance.

iPetition is tested for compatibility with the following assistive technologies:

iPetition aims to conform to WCAG 2.1 Level AA. This means we address the following principles:

• Perceivable: Information and UI components are presented in ways users can perceive (text alternatives, captions, adaptable layouts, sufficient contrast).
• Operable: UI components and navigation are operable via keyboard, with sufficient time, no seizure-inducing content, and clear navigation.
• Understandable: Information and operation of the UI is understandable (readable text, predictable behavior, input assistance).
• Robust: Content is robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

We conduct regular accessibility audits using both automated tools (axe, Lighthouse) and manual testing with screen readers and keyboard-only navigation.

While we strive for full accessibility, some areas may have limitations:

• Third-party embeds: Embedded content from third-party services (Stripe checkout, Google Maps) may not fully conform to WCAG standards. We provide alternative access methods where possible.
• User-generated content: Petition descriptions and comments created by users may not always include proper alternative text for images or follow accessibility best practices.
• PDF exports: Data export files may not be fully accessible. We are working on providing accessible export formats.
• Complex data visualizations: Some analytics charts may have limited screen reader support. We provide data tables as alternatives where available.

We actively work to identify and address accessibility barriers. If you encounter an issue, please let us know.

We welcome your feedback on the accessibility of iPetition. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

• Email: support@ipetition.com
• Website: https://ipetition.com

When reporting an accessibility issue, please include:

• The page URL where you encountered the issue.
• A description of the problem.
• The assistive technology and browser/device you were using.
• Any screenshots or recordings, if possible.

We aim to respond to accessibility feedback within 5 business days and to resolve reported issues within 30 days where technically feasible.