Understanding WCAG 2.2
Web Content Accessibility Guidelines (WCAG) 2.2 provides standards for making digital content accessible to people with disabilities. The guidelines are organized into four principles: Perceivable, Operable, Understandable, and Robust (POUR). Mobile apps should target Level AA compliance at minimum, with Level AAA for critical applications like healthcare or government services.
New in WCAG 2.2: Focus appearance requirements, dragging movements alternatives, target size minimums, and consistent help mechanisms. These additions specifically address mobile interaction challenges.
Screen Reader Support
Screen readers are essential for blind and low-vision users. iOS VoiceOver and Android TalkBack require proper semantic markup. Label all interactive elements with descriptive text, group related elements logically, announce dynamic content changes, provide context for icons and images, and implement proper heading hierarchy.
Over 2.2 billion people worldwide have vision impairment - making your app accessible isn't optional, it's essential.
Touch Target Sizes
WCAG 2.2 requires minimum touch target size of 24x24 CSS pixels (Level AA) or 44x44 pixels (Level AAA). iOS Human Interface Guidelines recommend 44x44 points, Android Material Design suggests 48x48 dp. Ensure adequate spacing between targets (at least 8 pixels) to prevent accidental taps. Make entire card or row tappable, not just small icons.
Color Contrast Requirements
Text must have sufficient contrast against backgrounds: 4.5:1 for normal text (Level AA), 3:1 for large text (18pt+ or 14pt+ bold), 3:1 for UI components and graphics. Never rely on color alone to convey information - use icons, patterns, or text labels as well. Test with color blindness simulators to ensure usability for all users.
Keyboard and Voice Navigation
Support external keyboard navigation for iOS and Android. Ensure logical tab order, visible focus indicators, keyboard shortcuts for common actions, and escape mechanisms for modals. Voice control (Voice Access on Android, Voice Control on iOS) should allow users to navigate and interact without touch. Label elements clearly for voice commands.
Accessibility Testing Tools
Use Xcode Accessibility Inspector for iOS, Android Lint and Accessibility Scanner for Android, and automated testing with Espresso/XCUITest accessibility APIs. Manual testing with actual screen readers is crucial - automated tools catch only 30-40% of issues. Recruit users with disabilities for usability testing.
Legal Requirements
Many countries mandate digital accessibility: Americans with Disabilities Act (ADA) in US, European Accessibility Act in EU, Equality Act in UK. Non-compliance can result in lawsuits and fines. Beyond legal requirements, accessible apps reach 15% more users and demonstrate corporate social responsibility.