Verify mobile accessibility beyond an automated score
Combine automated rules with touch, zoom, keyboard, screen-reader, and comprehension tasks.
Start with operable controls
Interactive targets need a visible label, programmatic name, predictable order, and enough space for touch. Icon-only controls should expose an accessible name and must not rely on color alone.
Test narrow widths and zoom
Check common narrow widths without horizontal overflow, then run a real 200 percent zoom task on desktop. Text should reflow, dialogs should remain reachable, and fixed navigation must not cover the active control.
Use a real task with a screen reader
A scanner cannot tell whether the spoken experience makes sense. Ask a person or trained tester to start a project, find the next action, save a backup, and return to the prior screen. Record misunderstandings as product defects.
Preserve evidence boundaries
An Android result does not prove iPhone behavior. A browser emulation does not prove a physical-device gesture. Keep each result attached to its actual environment.
Release-ready checklist
- Touch targets are large enough
- Controls have accessible names
- Content reflows at narrow width and zoom
- Dialog focus returns correctly
- Physical-device and human results are labelled
This guide is written for planning and verification. Store rules and legal requirements can change; verify official requirements before submission.