WCAG 2.2 quick check: all 55 A and AA criteria in one checklist
A WCAG 2.2 quick check is a self-assessment against the 55 Level A and AA success criteria in the W3C standard, grouped by principle so you can work through them in order. Tick the boxes below for an instant, in-browser summary. Nothing you check is sent anywhere, and a clean checklist is not the same as a full audit or an accessibility statement.
Published · ShipperAG team
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.
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.
WCAG 2.2 success criteria at Level A and AA, by principle
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.
A WCAG 2.2 checklist lists the success criteria from the W3C's Web Content Accessibility Guidelines 2.2, so a team can work through them one at a time. At Level A and AA, the levels most laws and policies reference, there are 55: 31 at Level A and 24 at Level AA, grouped under four principles: perceivable, operable, understandable and robust.
Is this WCAG 2.2 checklist tool free to use?
Yes. The checklist above is free, with no sign-up and no limit on how many times you use it. It runs entirely in your browser, so there is nothing to install and no account to create.
Does ticking these boxes send any data anywhere?
No. The checklist runs entirely in your browser using ordinary checkboxes. Nothing you tick is sent to a server or stored, and it is cleared as soon as you leave or reload the page.
Can a WCAG 2.2 checklist replace an accessibility audit?
No. Ticking a box here records that your team looked at a criterion, not that a qualified assessor verified it. A full audit combines automated scans, manual testing and often assistive-technology users, and produces evidence a team can stand behind. Treat this checklist as the map of what to check, not the proof that you checked it.
How much of this checklist can a tool check automatically?
23 of the 55. axe-core 4.10.3, the accessibility engine behind most tooling, carries rules tagged to 23 of the 55 WCAG 2.2 Level A and AA success criteria. The other 32 ask whether something makes sense rather than whether it exists, so they need a person. The checklist above marks which is which as you go.
What's new in WCAG 2.2 compared to WCAG 2.1?
WCAG 2.2 adds nine new success criteria and removes one (4.1.1 Parsing, now obsolete). Six of the nine new criteria apply at Level A or AA, and are included in the 55 above: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). The other three are Level AAA.
ShipperAG is in a private pilot. Join the waitlist to become a product partner and get accessibility checks on every release, with an independent verifier and evidence you can sign.
Free 45-day trial, no card
Up to 20 release checks on your product
Direct line to the founders
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.
