Mobile Accessibility Checklist for WCAG 2.1
Mobile-specific accessibility checklist covering touch targets, orientation, gestures, responsive design, and WCAG 2.1 criteria added specifically for mobile devices.
Detailed Explanation
Mobile Accessibility Audit
WCAG 2.1 introduced several success criteria specifically addressing mobile accessibility. Mobile auditing requires testing touch interactions, responsive layout, orientation support, and gesture alternatives.
Mobile-Specific WCAG 2.1 Criteria
| Criterion | Level | Mobile Relevance |
|---|---|---|
| 1.3.4 Orientation | AA | Content works in both portrait and landscape |
| 1.4.10 Reflow | AA | No horizontal scroll at 320px |
| 1.4.12 Text Spacing | AA | Custom text spacing does not break layout |
| 2.1.4 Character Key Shortcuts | A | Single-key shortcuts on Bluetooth keyboards |
| 2.5.1 Pointer Gestures | A | Alternatives to multipoint/path gestures |
| 2.5.2 Pointer Cancellation | A | Actions trigger on up-event, not down-event |
| 2.5.3 Label in Name | A | Visible text matches accessible name |
| 2.5.4 Motion Actuation | A | Alternatives to shake/tilt |
Touch Target Size
While WCAG 2.1 does not specify minimum touch target size (WCAG 2.2 criterion 2.5.8 requires 24x24px minimum), best practices recommend:
- Minimum 44x44 CSS pixels for touch targets (Apple HIG)
- 48x48 CSS pixels recommended (Material Design)
- Adequate spacing between adjacent targets
- Entire clickable area matches visible element
Testing Methodology
- Test on actual devices — Simulators miss touch interaction issues
- Test both orientations — Rotate between portrait and landscape
- Test at various zoom levels — Up to 200% zoom
- Test with assistive technology — VoiceOver (iOS), TalkBack (Android)
- Test with external keyboard — Bluetooth keyboard with screen reader
Responsive Layout Checks
- Content reflows at 320px viewport width (no horizontal scrollbar)
- Text is readable without zooming on small screens
- Navigation is accessible (hamburger menu must be keyboard/touch operable)
- Form fields are properly sized for mobile input
- Modals and popovers fit within the viewport
Use Case
Mobile accessibility testing is critical as mobile traffic exceeds desktop for most websites. E-commerce, healthcare, banking, and government services must be accessible on mobile devices. Include mobile accessibility in your QA test plans and consider it during responsive design reviews.
Try It — Accessibility Audit Checklist
Perceivable
Operable
Understandable
Robust
50 criteria shown · Click the status badge to cycle through Pass / Fail / N/A / Untested