Accessibility

1. Our Commitment to Accessibility

At Allies, we believe that technology should be accessible to everyone, regardless of ability. Coparenting is challenging enough without barriers to communication and coordination. That's why we've made accessibility a core principle in everything we build.

We strive to ensure that our iOS, Android, and web applications meet WCAG 2.2 Level AA standards — the internationally recognized guidelines for web accessibility established by the World Wide Web Consortium (W3C).

2. Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

Allies is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard, and we are actively working to address these gaps.

3. Accessibility Features

We have implemented the following accessibility features across our platforms:

3.1 Visual Accessibility

• Color contrast: All text meets WCAG 2.2 AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components)
• Text scaling: Our apps support text scaling from 100% to 200% without loss of content or functionality
• Focus indicators: Visible focus states on all interactive elements for keyboard navigation
• Color independence: Information is never conveyed by color alone — we use icons, text labels, and patterns as secondary indicators
• Dark mode: Full dark mode support across all platforms to reduce eye strain and accommodate light sensitivity

3.2 Motor Accessibility

• Touch targets: All interactive elements have a minimum touch target size of 48x48 density-independent pixels
• Keyboard navigation: Full keyboard accessibility on web — all features can be accessed without a mouse
• No time limits: Sessions do not time out during active use; users are never rushed to complete actions
• Gesture alternatives: Complex gestures have single-tap or button alternatives

3.3 Cognitive Accessibility

• Clear language: We use plain language and avoid jargon wherever possible
• Consistent navigation: Navigation patterns are consistent throughout the app
• Error prevention: Confirmation dialogs for destructive actions; clear error messages with recovery suggestions
• Progress indicators: Visual feedback during loading states and multi-step processes
• Reduced motion: Animations respect the "reduce motion" system preference — users who are sensitive to motion can disable animations

3.4 Screen Reader Support

• Semantic HTML: Proper use of headings, landmarks, lists, and form labels
• ARIA labels: Descriptive labels for icons, buttons, and interactive elements
• VoiceOver (iOS): Tested and optimized for Apple's built-in screen reader
• TalkBack (Android): Tested and optimized for Android's built-in screen reader
• NVDA & JAWS (Web): Compatible with popular Windows screen readers
• Live regions: Dynamic content updates are announced to assistive technology

3.5 Form Accessibility

• Visible labels: All form fields have persistent visible labels (not just placeholder text)
• Error identification: Form errors are clearly identified with text descriptions, not just color
• Input assistance: Appropriate keyboard types for email, phone, and date fields on mobile
• Autocomplete: Standard autocomplete attributes to help password managers and assistive tools

4. Standards We Follow

Our accessibility efforts are guided by the following standards and guidelines:

• WCAG 2.2 Level AA — Web Content Accessibility Guidelines from W3C
• Section 508 — U.S. federal accessibility requirements
• ADA — Americans with Disabilities Act compliance
• Apple Human Interface Guidelines — Accessibility best practices for iOS
• Android Accessibility Guidelines — Material Design accessibility standards
• ARIA 1.2 — Accessible Rich Internet Applications specification

5. Testing & Auditing

We use a combination of automated and manual testing to ensure accessibility:

• Automated testing: Accessibility linting in our development process catches issues early
• Manual testing: Regular testing with VoiceOver, TalkBack, and keyboard-only navigation
• User testing: Feedback from users with disabilities informs our priorities
• Color contrast analyzers: All color combinations are verified against WCAG requirements
• Screen reader testing: Every major release is tested with multiple screen readers

6. Known Limitations

We are actively working to address the following known accessibility limitations:

• PDF documents: User-uploaded court documents may not be accessible; we recommend uploading text-searchable PDFs when possible
• Video calls: Live captions for video calls are not yet available but are on our roadmap
• Third-party content: Some embedded third-party content may not meet our accessibility standards
• Legacy browsers: Some accessibility features may not work fully in older browsers

We maintain an internal accessibility backlog and prioritize fixes based on user impact. If you encounter an issue not listed here, please let us know.

7. Assistive Technology Compatibility

Allies is designed to be compatible with the following assistive technologies:

8. Feedback & Contact

We welcome your feedback on the accessibility of Allies. If you encounter accessibility barriers, have suggestions for improvement, or need assistance using our platform, please contact us:

• Email: accessibility@alliesapp.com
• General support: support@alliesapp.com
• Response time: We aim to respond to accessibility feedback within 5 business days

When contacting us about an accessibility issue, please include:

• The page or feature where you encountered the issue
• The device, operating system, and browser (or app version) you were using
• Any assistive technology you were using (screen reader, magnifier, etc.)
• A description of what you expected to happen and what actually happened

9. Our Ongoing Commitment

Accessibility is not a one-time effort — it's an ongoing commitment. We pledge to:

• Include accessibility requirements in our product development process
• Train our team on accessibility best practices
• Test with real users who have disabilities
• Continuously monitor and improve accessibility
• Respond promptly to accessibility feedback
• Update this statement as we make improvements

Everyone deserves the ability to coordinate coparenting effectively. We're committed to making Allies accessible to all families, regardless of ability.