Skip to content
Accessibility Scanner

WCAG explained

WCAG 2.2 checklist

WCAG 2.2 has 56 success criteria across Level A and AA. This is the working checklist, grouped the way you actually fix things, with an honest note on which items a scanner can verify and which need a person. Scan a page below to check the automatable ones in seconds.

Scan a page against WCAG 2.2 A & AA, free, no signup.

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: headings are sequential and meaningful; lists, tables, and landmarks use correct markup (1.3.1, 2.4.6, 2.4.10).
  • 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, heading order, ARIA misuse, and more. That is roughly a third of the criteria by count, but it catches the majority of the issues actually present on a typical page. The rest, like whether alt text is meaningful or whether focus order makes sense, needs human judgement. An honest tool tells you which is which.

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?

WCAG 2.2 has 56 success criteria across Levels A, AA, and AAA. Level A and AA together are what you target for compliance.

What did WCAG 2.2 add over 2.1?

Nine new criteria, including focus appearance, focus not obscured, target size minimum (24x24px), dragging alternatives, and accessible authentication.

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

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 scan

Last updated 2026-06-23.