Mobile accessibility
On mobile, accessibility depends on target size, zoom, orientation and the VoiceOver (iOS) and TalkBack (Android) screen readers. WCAG 2.2 now requires targets of at least 24 × 24 CSS px.
The key rules
- Large, spaced targets: 24 × 24 px minimum (WCAG 2.5.8), 44 px for key actions.
- Zoom allowed: never
user-scalable=noor a blockingmaximum-scale. - No hover dependence: hover content must be reachable by touch and keyboard.
- Orientation: don’t force portrait or landscape without need (RGAA 13.9).
- Linear navigation consistent with visual order.
- Don’t rely on an overlay: fix the code.
Code example
<meta name="viewport" content="width=device-width, initial-scale=1">
.btn { min-height: 44px; min-width: 44px; }How to test
Turn on VoiceOver or TalkBack and complete a full journey. Zoom to 200% and reflow at 320 px width. RGAA criteria: 10.4, 10.11, 13.9. Resources: MDN mobile accessibility.
Frequently asked questions
What is the minimum touch target size?
WCAG 2.2 (criterion 2.5.8, AA) requires 24 × 24 CSS px with exceptions; aiming for 44 px on key actions is good practice.
Can zoom be blocked?
No. Blocking zoom prevents low-vision users from enlarging content and breaches RGAA.