Free tool · WCAG 2.2 accessibility

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.

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 →

1 Perceivable — 20 criteria
1.1.1 Non-text Content A

Images, icons and controls have accurate text alternatives

1.2.1 Audio-only and Video-only (Prerecorded) A

Prerecorded audio-only or video-only media has an alternative

1.2.2 Captions (Prerecorded) A

Prerecorded video with sound has accurate captions

1.2.3 Audio Description or Media Alternative (Prerecorded) A

Prerecorded video has audio description or a full text alternative

1.2.4 Captions (Live) AA

Live video with sound has accurate live captions

1.2.5 Audio Description (Prerecorded) AA

Prerecorded video has audio description covering what matters visually

1.3.1 Info and Relationships A

Headings, lists and form labels are marked up, not just styled

1.3.2 Meaningful Sequence A

The reading order still makes sense with styles removed

1.3.3 Sensory Characteristics A

Instructions never rely on shape, position, sound or colour alone

1.3.4 Orientation AA

Content works in both portrait and landscape

1.3.5 Identify Input Purpose AA

Common inputs use the correct autocomplete value

1.4.1 Use of Color A

Colour is never the only way information is conveyed

1.4.2 Audio Control A

Auto-playing audio over three seconds can be paused, stopped or muted

1.4.3 Contrast (Minimum) AA

Text meets a 4.5:1 contrast ratio (3:1 for large text)

1.4.4 Resize Text AA

Text can be resized to 200% without losing content or function

1.4.5 Images of Text AA

Text is real text, not an image, except logos

1.4.10 Reflow AA

Content reflows at 320 CSS pixels wide with no two-dimensional scrolling

1.4.11 Non-text Contrast AA

Borders, icons and focus rings that carry meaning meet 3:1 contrast

1.4.12 Text Spacing AA

Content still works if line height and letter spacing are overridden

1.4.13 Content on Hover or Focus AA

Tooltips and popovers can be hovered, dismissed and stay visible

2 Operable — 20 criteria
2.1.1 Keyboard A

Every function works from a keyboard alone

2.1.2 No Keyboard Trap A

You can always tab out of every widget and modal

2.1.4 Character Key Shortcuts A

Single-character shortcuts can be turned off, remapped or need focus

2.2.1 Timing Adjustable A

Time limits can be turned off, adjusted or extended

2.2.2 Pause, Stop, Hide A

Moving, blinking or auto-updating content can be paused or stopped

2.3.1 Three Flashes or Below Threshold A

Nothing flashes more than three times per second

2.4.1 Bypass Blocks A

A skip link or landmark lets users bypass repeated content

2.4.2 Page Titled A

Every page has a clear, descriptive title

2.4.3 Focus Order A

Tab order follows the meaning and operation of the page

2.4.4 Link Purpose (In Context) A

Link text, with its context, makes the destination clear

2.4.5 Multiple Ways AA

There is more than one way to find a page: nav, search, sitemap

2.4.6 Headings and Labels AA

Headings and labels describe what follows accurately

2.4.7 Focus Visible AA

A visible focus indicator appears on every control

2.4.11 Focus Not Obscured (Minimum) AA

Sticky headers or chat widgets never fully hide the focused control

2.5.1 Pointer Gestures A

Multi-point or path-based gestures have a single-pointer alternative

2.5.2 Pointer Cancellation A

Pointer actions fire on release and can be cancelled

2.5.3 Label in Name A

The visible label text is included in the accessible name

2.5.4 Motion Actuation A

Motion-triggered actions have a conventional alternative and can be disabled

2.5.7 Dragging Movements AA

Every drag interaction has a single-tap or click alternative

2.5.8 Target Size (Minimum) AA

Pointer targets are at least 24 by 24 CSS pixels, with exceptions

3 Understandable — 13 criteria
3.1.1 Language of Page A

The page's language is set in code

3.1.2 Language of Parts AA

Passages in a different language are marked up as such

3.2.1 On Focus A

Nothing changes context just because an element receives focus

3.2.2 On Input A

Nothing submits, navigates or reorders the page from an input alone

3.2.3 Consistent Navigation AA

Repeated navigation stays in the same relative order across pages

3.2.4 Consistent Identification AA

Components with the same function are labelled the same way

3.2.6 Consistent Help A

Help appears in the same place on every page that has it

3.3.1 Error Identification A

Errors are described in text and identify the field

3.3.2 Labels or Instructions A

Form fields have visible labels or instructions

3.3.3 Error Suggestion AA

Error messages suggest how to fix the problem, where known

3.3.4 Error Prevention (Legal, Financial, Data) AA

Legal, financial or data-deleting actions are reversible, checked or confirmed

3.3.7 Redundant Entry A

Multi-step processes don't ask again for information already given

3.3.8 Accessible Authentication (Minimum) AA

Sign-in doesn't require a cognitive test with no alternative

4 Robust — 2 criteria
4.1.2 Name, Role, Value A

Custom controls expose a correct name, role and state

4.1.3 Status Messages AA

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.

WCAG 2.2 success criteria at Level A and AA, by principle
PrincipleLevel ALevel AATotal
1. Perceivable91120
2. Operable14620
3. Understandable7613
4. Robust112
Total312455

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

FAQ

WCAG 2.2 checklists, answered

What is a WCAG 2.2 checklist?

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.

Free 45-day trial · waitlist open

Get WCAG 2.2 checked on every release

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.