Web accessibility checklist
A practical WCAG 2.2 AA checklist covering structure, keyboard access, visual contrast, forms, and media — with what each check actually catches.
Last updated
Your ticks are saved on this device only — never uploaded, never synced.
Structure & semantics
0/5Keyboard
0/5Visual & contrast
0/5Forms
0/5Media
0/4Questions
Can an automated tool do this instead?
It catches roughly a third of issues — missing alternative text, contrast failures, absent labels. Keyboard traps, focus order and whether alternative text is actually meaningful all need a person, and those are frequently the ones that block someone entirely.
What is the fastest useful test?
Unplug the mouse and use the page. Keyboard navigation exposes focus order, invisible focus indicators and traps within a minute, and those are among the most common and most severe problems.
Which contrast ratio applies?
4.5 to 1 for normal text and 3 to 1 for large text under WCAG AA. Placeholder text and disabled controls fail this constantly, and both are frequently defended as intentional design.
Is alternative text needed on every image?
Every image needs the attribute; decorative ones should have it empty so screen readers skip them. An image described as image or photo is worse than an empty one, because it interrupts without informing.
Where should this fit in a project?
Throughout, because retrofitting is far more expensive. Most failures here are structural — heading order, semantics, focus management — and those are cheap during build and painful afterwards.