WCAG explained
WCAG 2.2 checklist
By Chris Morris · updated 2026-09-15
WCAG 2.2 has 55 success criteria at Levels A and AA, the two levels laws and contracts point to. This is a working checklist, grouped the way you actually fix things, with a note on which items a scanner can verify and which need a person. Scan a page below to check the automatable ones.
How WCAG is organised
WCAG groups criteria under four principles: content must be Perceivable, Operable, Understandable, and Robust (POUR). Each criterion has a conformance level: A (essential), AA (the standard legal target), or AAA (enhanced, rarely required site-wide). For compliance you target Level AA, which includes all of Level A.
The checklist, grouped by what you fix
- Text alternatives: every meaningful image, icon, and control has a text alternative (1.1.1).
- Colour & contrast: text meets 4.5:1 (3:1 for large text); do not rely on colour alone to convey meaning (1.4.1, 1.4.3, 1.4.11).
- Structure: text that looks like a heading is marked up as one, headings describe their section, and lists, tables and landmarks use correct markup (1.3.1, 2.4.6). Keeping heading levels in sequence is good practice, but a skipped level is not a WCAG failure on its own.
- Keyboard: everything works without a mouse, with no traps, and a visible focus indicator (2.1.1, 2.1.2, 2.4.7).
- Forms: every field has a label; errors are identified and described; required fields are marked (1.3.1, 3.3.1, 3.3.2).
- Navigation & links: link text makes sense out of context; pages have titles; focus order is logical (2.4.2, 2.4.4, 2.4.3).
- Media: captions for video, transcripts for audio (1.2.2, 1.2.1).
- New in 2.2: visible focus is not obscured (2.4.11), targets are at least 24x24px (2.5.8), no functionality needs dragging (2.5.7), and authentication does not rely on memory or puzzles (3.3.8).
What a scanner checks, and what it cannot
Automated testing reliably verifies the machine-checkable criteria: contrast, alt-text presence, form labels, accessible names, page language, ARIA misuse and target size. That is roughly a third of the criteria by count, but those criteria account for a large share of the issues found on real pages, because the same few failures repeat everywhere. The rest, like whether alt text is meaningful or whether focus order makes sense, needs human judgement. A useful report keeps the two apart.
Run the machine-testable half now
Use the free scan above to clear the automatable items first. You get every failing element outlined and mapped to its success criterion, plus the items flagged for manual review. Fix those, then do a keyboard and screen-reader pass for the human-judgement criteria.
Frequently asked questions
What is the difference between WCAG A, AA, and AAA?
A is the minimum, AA is the standard target referenced by most laws, and AAA is an enhanced level that is not expected across an entire site. Aim for AA.
How many success criteria are in WCAG 2.2?
86 in total: 31 at Level A, 24 at AA and 31 at AAA. Levels A and AA together, 55 criteria, are what laws and procurement contracts ask for. Some lists say 87 or 56 because they still count 4.1.1 Parsing, which WCAG 2.2 removed as obsolete.
What did WCAG 2.2 add over 2.1?
Nine new criteria, six of them at A or AA: focus not obscured (2.4.11), dragging movements (2.5.7), target size minimum of 24x24px (2.5.8), consistent help (3.2.6), redundant entry (3.3.7) and accessible authentication (3.3.8). It also removed 4.1.1 Parsing.
Can I become WCAG compliant with an automated scan alone?
No. A scan clears the machine-testable criteria, which is most of the volume, but full conformance still requires manual testing for the criteria a tool cannot judge.
Related guides
- ADA website compliance Compliance
- WCAG 1.1.1: Non-text Content WCAG explained
- Touch target size and WCAG 2.5.8 WCAG explained
- How to fix color contrast issues How to fix
- Fixing contrast that only breaks when you tab to it How to fix
- How to fix links with no discernible text How to fix
- How to fix skipped heading levels How to fix
- Font size and accessibility How to fix
- Keyboard navigation accessibility How to fix
- Free accessibility checker Guide
See what's actually broken on your site
Real axe-core results, every element outlined. No email wall, no fake “compliant” badge.
Run a free scanLast updated 2026-09-15.