The WCAG 2.2 quick check
Work through the 55 criteria below, grouped by principle. Each one shows its level (A or AA) and, once you have ticked some, the summary tells you how many of the criteria a tool like axe-core can check on its own and how many need a person to judge. This is one part of ShipperAG's wider 13 quality areas, the human experience area in particular.
Your progress
0% 0 of 55 checked
Perceivable 0/20 · Operable 0/20 · Understandable 0/13 · Robust 0/2
0 of the 23 criteria a tool like axe-core can check are ticked; 0 of the 32 that need a person are ticked. See the 32, and what each needs from a person →
Gaps to close
Every function works from a keyboard alone
You can always tab out of every widget and modal
Single-character shortcuts can be turned off, remapped or need focus
Time limits can be turned off, adjusted or extended
Moving, blinking or auto-updating content can be paused or stopped
Nothing flashes more than three times per second
A skip link or landmark lets users bypass repeated content
Every page has a clear, descriptive title
Tab order follows the meaning and operation of the page
Link text, with its context, makes the destination clear
There is more than one way to find a page: nav, search, sitemap
Headings and labels describe what follows accurately
A visible focus indicator appears on every control
Sticky headers or chat widgets never fully hide the focused control
Multi-point or path-based gestures have a single-pointer alternative
Pointer actions fire on release and can be cancelled
The visible label text is included in the accessible name
Motion-triggered actions have a conventional alternative and can be disabled
Every drag interaction has a single-tap or click alternative
Pointer targets are at least 24 by 24 CSS pixels, with exceptions
The page's language is set in code
Passages in a different language are marked up as such
Nothing changes context just because an element receives focus
Nothing submits, navigates or reorders the page from an input alone
Repeated navigation stays in the same relative order across pages
Components with the same function are labelled the same way
Help appears in the same place on every page that has it
Errors are described in text and identify the field
Form fields have visible labels or instructions
Error messages suggest how to fix the problem, where known
Legal, financial or data-deleting actions are reversible, checked or confirmed
Multi-step processes don't ask again for information already given
Sign-in doesn't require a cognitive test with no alternative
Custom controls expose a correct name, role and state
Status messages are announced by a screen reader without moving focus
The 55 criteria, grouped by principle
WCAG 2.2 organises its success criteria under four principles: content must be perceivable, interfaces must be operable, information must be understandable, and content must be robust enough to work with assistive technology. At Level A and AA, the levels most laws and internal policies reference, that is 55 criteria in total: 31 at Level A and 24 at Level AA.
| Principle | Level A | Level AA | Total |
|---|---|---|---|
| 1. Perceivable | 9 | 11 | 20 |
| 2. Operable | 14 | 6 | 20 |
| 3. Understandable | 7 | 6 | 13 |
| 4. Robust | 1 | 1 | 2 |
| Total | 31 | 24 | 55 |
Level AAA adds a further set of criteria, but almost no law or policy requires it site-wide, so it is out of scope for this checklist, in line with the W3C's own guidance for most organisations.
What a tool catches, and what needs a person
Of the 55 criteria above, a tool can settle 23 on its own. axe-core 4.10.3, the accessibility engine behind most scanners, carries rules tagged to 23 of the 55 WCAG 2.2 Level A and AA success criteria. The other 32 have no rule tagged to them at all, because they ask whether something makes sense rather than whether it exists: whether a heading is honest, an error message helps, or a focus order preserves meaning. Our full breakdown of the 32 checks automation cannot make lists each one with what a person has to do, and the method behind the count.
Want these checks run against a real release, with a verifier and an evidence report attached? Start with a free 45-day trial, no card.
Work email only. We keep your email, team size, plan choice and the page you joined from, only to contact you about the ShipperAG pilot. No spam.
What's new in WCAG 2.2
WCAG 2.2 became a W3C Recommendation in October 2023. It keeps every WCAG 2.1 success criterion except 4.1.1 Parsing, which the W3C removed as obsolete, and adds nine new ones. Six of the nine apply at Level A or AA and are included in the 55 above: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum). The other three (Focus Not Obscured Enhanced, Focus Appearance, and Accessible Authentication Enhanced) are Level AAA and outside most teams' scope. For where WCAG 2.2 fits into EU and UK law, see our European Accessibility Act testing guide.
How to use this checklist
- Pick a page or a release. Run the checklist against one page or one release at a time, not the whole product at once, so a tick means something specific.
- Start with the 23 a tool can check. Run an automated scan first and tick off what it confirms; that clears the mechanical third quickly and leaves your attention for the rest.
- Work the 32 that need a person. Tab through with a keyboard, trigger every error state, and compare navigation and labelling across more than one page. Our guide to AI accessibility testing covers how an agent can do the running while a person still makes the judgement calls.
- Write down what you skipped. An honest "not checked" next to a criterion is worth more than a tick nobody can back up. The same habit runs through our website QA checklist and release readiness checklist.
- Keep the record with the release. Save or print your result (use your browser's print dialogue) and file it with the build it applies to, so the next review starts from where this one left off.
None of this is a substitute for a full accessibility audit or a formal accessibility statement, and it does not make any claim about legal compliance. It is a working checklist: a faster way to see what a release still needs before you ask someone to assess it properly. Browse the rest of our guides and resources for the checklists, templates and comparisons behind it.
Sources: W3C, Web Content Accessibility Guidelines (WCAG) 2.2; W3C WAI, What's new in WCAG 2.2; ShipperAG, the 32 WCAG checks no tool makes for you (21 September 2026), for the axe-core 4.10.3 coverage count. Checked 27 September 2026.