Which standards does this checklist draw from?

It combines the mobile-relevant success criteria of WCAG 2.1 and 2.2 at AA, the W3C Mobile Web Best Practices, and platform guidance from iOS and Android. Each item cites the relevant success criterion or guideline so you can trace it back to the source.

What is the minimum touch target size?

WCAG 2.2 added Target Size (Minimum) at 24 by 24 CSS pixels for AA, while the older Target Size (Enhanced) and platform guidance recommend at least 44 by 44 pixels. Aim for 44 pixels where you can, treat 24 as the absolute floor, and always leave spacing between adjacent targets.

Is my progress saved?

Yes. Your ticked items are stored in this browser using localStorage, so closing and reopening the page keeps your progress. Clearing site data or using a different browser or device starts a fresh checklist.

Does passing this checklist guarantee compliance?

No. A manual checklist is a strong guide but not a substitute for testing with real assistive technology and real users. Pair it with VoiceOver and TalkBack walkthroughs, an automated scan such as axe-core, and ideally a usability test with disabled users.

Why do mobile sites need a separate accessibility pass?

Mobile introduces issues desktop rarely faces: small touch targets, orientation changes, path-based gestures, motion actuation, on-screen keyboards, and reflow at narrow widths. These checks focus on exactly those mobile-specific failure modes.

WCAG Mobile Accessibility Checklist

Mobile accessibility fails in ways desktop never does — targets too small to tap, gestures with no alternative, content locked to portrait, keyboards that hide the field you are typing in. This interactive checklist walks you through 40 mobile-specific checks drawn from WCAG 2.1/2.2 and the W3C Mobile Web Best Practices, and remembers your progress so an audit can span several sessions.

How it works

The 40 checks are grouped into seven areas that map to the most common mobile failure modes:

Touch targets & pointers — size, spacing, gesture alternatives, accidental activation.
Orientation & reflow — portrait/landscape support, single-column reflow at 320px, zoom enabled.
Visual & contrast — 4.5:1 text contrast, 3:1 for components, not relying on colour alone.
Input & forms — correct keyboard type, autocomplete, associated labels, helpful errors.
Screen reader & focus — accessible names, logical order, focus management, live regions.
Motion, media & timing — reduced motion, flash limits, captions, adjustable time limits.
Navigation & structure — titles, headings, language, bypass blocks, consistent navigation.

Each item cites its WCAG success criterion or MWBP guideline. As you tick checks, the per-section and overall counts update, and your state is written to localStorage under a single key so it survives a page reload. The reset button clears everything.

Tips for testing

Test on a real device with a real screen reader (VoiceOver on iOS, TalkBack on Android) — the emulator experience diverges from how assistive tech actually behaves.
Check reflow by setting the viewport to 320 CSS px and confirming no horizontal scroll appears.
Verify you have not disabled pinch-zoom: a viewport meta with user-scalable=no or maximum-scale=1 is a frequent, easily-missed failure.
Re-run the touch-target and contrast checks after any visual redesign — they regress quietly.

Notes

This checklist is a guide, not a certificate. Combine it with an automated scanner for the machine-detectable issues, manual screen-reader walkthroughs for the rest, and, where possible, testing with people who use assistive technology day to day.