Atlas › 09 Mobile & Cross-Platform Testing › Mobile Accessibility Testing☰ Read as one page
Mobile Accessibility Testing
11.1Mobile Accessibility Is Not Web AccessibilityMobile accessibility is not a subset of web accessibility. Touch interfaces, screen readers, and device-specific features introduce…11.2VoiceOver (iOS) and TalkBack (Android)Screen readers on mobile work differently from desktop screen readers. Users navigate by swiping (linear navigation) or by exploring…11.3Touch Target SizingWCAG 2.2 requires a minimum touch target size of 24x24 CSS pixels. Apple recommends 44x44 points. Google recommends 48x48 dp. These are…11.4Dynamic Type (iOS) and Font Scaling (Android)Users who increase system font size must not be punished with broken layouts. This is both an accessibility requirement and a legal…11.5Mobile Accessibility Checklist11.6Key Takeaways- Device selection is a data-driven decision -- use your analytics to build a device matrix that covers 90% of users with the minimum…11.7Interview Talking Point"My approach to mobile and cross-platform testing starts with data: I pull device and browser analytics to build a three-tier testing…