WCAG 2.2 AA checklist: all 55 criteria explained
Jonathan Bell
Co-founder, Sprout ·
Quick answer
To meet WCAG 2.2 AA, a website must satisfy every Level A and Level AA success criterion that applies to it: 55 in total, 31 at Level A and 24 at Level AA. The criteria marked AA aren’t enough on their own. Below are all 55 in tables, with what each one requires, how to test it and how much an automated scan can catch.
What’s new in WCAG 2.2
WCAG 2.2 became a W3C Recommendation on 5 October 2023. It adds nine success criteria to WCAG 2.1 and removes 4.1.1 Parsing as obsolete. Six of the new criteria are Level A or AA, so they’re part of this checklist:
- 2.4.11 Focus Not Obscured (Minimum), AA
- 2.5.7 Dragging Movements, AA
- 2.5.8 Target Size (Minimum), AA
- 3.2.6 Consistent Help, A
- 3.3.7 Redundant Entry, A
- 3.3.8 Accessible Authentication (Minimum), AA
The other three (2.4.12, 2.4.13 and 3.3.9) are AAA. If your site already met WCAG 2.1 AA, check these six first.
WCAG 2.2 and the European Accessibility Act
The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025, through each member state’s national law. For technical conformity, the European reference is the standard EN 301 549. Version 3.2.1 points to WCAG 2.1 AA. ETSI published version 4.1.1 on 2 September 2026, which updates that reference to WCAG 2.2. It takes full legal effect once it’s cited in the Official Journal of the EU.
In practice: if you’re starting accessibility work today, aim for WCAG 2.2 AA. Whether the EAA applies to you depends on the products and services you offer, and on the national law where you operate.
How to use this checklist
- Scan first, to find the failures a tool can detect on its own.
- Group by component and template. A failure in the menu repeats on every page.
- Test complete journeys: checkout, sign-up, search, log-in.
- For each criterion, record how you tested it and what you found.
- Repeat after every significant change.
The “Auto” column is Sprout’s own rating, not the W3C’s. High: software can check almost all of it. Partial: a tool finds signals, but a person has to judge. Low: it depends on interaction or meaning.
Principle 1. Perceivable: 20 criteria
| Criterion | Level | What it requires | How to test it | Auto |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | An equivalent text alternative for images, icons and charts that carry information | Use a screen reader: does the alt text describe the purpose or content? | Partial |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | A transcript or equivalent alternative | Review each media file | Low |
| 1.2.2 Captions (Prerecorded) | A | Synchronised captions | Play the video with the sound off | Low |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | An alternative for information that’s only visual | Listen to the video without watching | Low |
| 1.2.4 Captions (Live) | AA | Captions for live broadcasts | Watch live streams and webinars without sound | Low |
| 1.2.5 Audio Description (Prerecorded) | AA | Audio description of the relevant visual information | Listen without watching: are actions or on-screen text missing? | Low |
| 1.3.1 Info and Relationships | A | Headings, lists, tables and labels marked up in the code, not just styled | Inspect the semantics and test with a screen reader | Partial |
| 1.3.2 Meaningful Sequence | A | The code order keeps the meaning | Compare the visual order with the DOM order | Partial |
| 1.3.3 Sensory Characteristics | A | Instructions don’t rely only on shape, size, position or sound | Look for text like “press the round button on the right” | Partial |
| 1.3.4 Orientation | AA | Don’t lock the view to portrait or landscape | Rotate the device | Partial |
| 1.3.5 Identify Input Purpose | AA | Correct autocomplete attribute on personal-data fields | Check name, email, address and phone fields | High |
| 1.4.1 Use of Color | A | Colour isn’t the only way information is shown | View the page in greyscale: errors, links, charts | Partial |
| 1.4.2 Audio Control | A | Audio that plays for more than 3 seconds can be paused or muted | Load the page with sound on | Partial |
| 1.4.3 Contrast (Minimum) | AA | 4.5:1 for normal text and 3:1 for large text | Measure text, links and states | High |
| 1.4.4 Resize Text | AA | Text at 200% without losing content or functions | Zoom the browser to 200% | Partial |
| 1.4.5 Images of Text | AA | Real text instead of images of text | Check banners and buttons | Partial |
| 1.4.10 Reflow | AA | No horizontal scrolling at 320 CSS pixels wide | Test at 320 px, or zoom to 400% at 1280 px | Partial |
| 1.4.11 Non-text Contrast | AA | 3:1 for controls, field borders, icons and essential graphics | Measure borders, icons and selected states | Partial |
| 1.4.12 Text Spacing | AA | Nothing breaks with line height 1.5, paragraph spacing 2 em, letter spacing 0.12 em and word spacing 0.16 em | Apply those values with CSS | Partial |
| 1.4.13 Content on Hover or Focus | AA | It can be dismissed, hovered over, and doesn’t disappear on its own | Test tooltips and menus with mouse and keyboard | Partial |
Principle 2. Operable: 20 criteria
| Criterion | Level | What it requires | How to test it | Auto |
|---|---|---|---|---|
| 2.1.1 Keyboard | A | Everything works with a keyboard | Complete the key tasks without a mouse | Partial |
| 2.1.2 No Keyboard Trap | A | You can always move away with the keyboard | Tab and Shift+Tab through modals, widgets and iframes | Partial |
| 2.1.4 Character Key Shortcuts | A | Single-key shortcuts can be turned off, remapped or only work on focus | Try shortcuts while typing or dictating | Low |
| 2.2.1 Timing Adjustable | A | Time limits can be turned off, extended or adjusted | Let sessions and bookings time out | Low |
| 2.2.2 Pause, Stop, Hide | A | Automatic movement lasting more than 5 seconds can be paused | Check carousels and tickers | Partial |
| 2.3.1 Three Flashes or Below Threshold | A | Nothing flashes more than three times a second above the threshold | Check videos and animations | Partial |
| 2.4.1 Bypass Blocks | A | A way to skip to the main content | First Tab: is there a skip link, or landmarks? | Partial |
| 2.4.2 Page Titled | A | Every page has a descriptive title | Check the browser tabs | High |
| 2.4.3 Focus Order | A | Focus follows a logical order | Tab through and compare with the visual order | Partial |
| 2.4.4 Link Purpose (In Context) | A | The link text or its context explains where it goes | Look for “here”, “more”, “read” | Partial |
| 2.4.5 Multiple Ways | AA | More than one way to reach each page | Menu, search, sitemap | Low |
| 2.4.6 Headings and Labels | AA | They describe the topic or purpose | Read only the headings and labels | Low |
| 2.4.7 Focus Visible | AA | You can always see which element has focus | Tab through the page | Partial |
| 2.4.11 Focus Not Obscured (Minimum), new | AA | The focused element isn’t completely hidden | Sticky headers, cookie banners, chat widgets | Partial |
| 2.5.1 Pointer Gestures | A | A single-pointer alternative to multipoint or path-based gestures | Maps, zoom, sliders | Low |
| 2.5.2 Pointer Cancellation | A | The action fires on release, or can be undone | Press, then drag away before releasing | Low |
| 2.5.3 Label in Name | A | The accessible name contains the visible text | Compare visible text with the accessible name | Partial |
| 2.5.4 Motion Actuation | A | An alternative to shaking or tilting, and a way to turn it off | Look for features that respond to motion | Low |
| 2.5.7 Dragging Movements, new | AA | An alternative that doesn’t need dragging | Kanban boards, sliders, sorting, file uploads | Low |
| 2.5.8 Target Size (Minimum), new | AA | At least 24×24 CSS pixels or enough spacing, with exceptions | Icons, chips, carousel dots | Partial |
Test your site with these criteria in front of you. Sprout’s free scan shows the automated failures on any page in seconds. No sign-up. Scan my website
Principle 3. Understandable: 13 criteria
| Criterion | Level | What it requires | How to test it | Auto |
|---|---|---|---|---|
| 3.1.1 Language of Page | A | Correct lang attribute | Check the lang on the html element | High |
| 3.1.2 Language of Parts | AA | lang on passages in another language | Quotes or buttons in another language | Partial |
| 3.2.1 On Focus | A | Focus doesn’t trigger a change of context | Tab through the page | Low |
| 3.2.2 On Input | A | Changing a value doesn’t cause unexpected changes | Selects, filters, radio buttons | Low |
| 3.2.3 Consistent Navigation | AA | Repeated navigation keeps the same order | Compare templates | Low |
| 3.2.4 Consistent Identification | AA | Same function, same name and icon | Compare buttons across pages | Low |
| 3.2.6 Consistent Help, new | A | Repeated help appears in the same relative order | Contact details, chat and FAQ on each template | Low |
| 3.3.1 Error Identification | A | The error is identified and described in text | Submit forms with errors | Partial |
| 3.3.2 Labels or Instructions | A | Every field has a label or instructions | Review the forms | Partial |
| 3.3.3 Error Suggestion | AA | The message says how to fix the error | Trigger common errors | Low |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Review, correct, confirm or reverse for legal, financial or data transactions | Checkout, account deletion | Low |
| 3.3.7 Redundant Entry, new | A | Don’t ask again for information already given in the same process | Checkout and multi-step forms | Low |
| 3.3.8 Accessible Authentication (Minimum), new | AA | No cognitive tests without an alternative; pasting and password managers work | Log-in and 2FA | Low |
Principle 4. Robust: 2 criteria
| Criterion | Level | What it requires | How to test it | Auto |
|---|---|---|---|---|
| 4.1.2 Name, Role, Value | A | Components expose their name, role, state and value | The browser’s accessibility tree | Partial |
| 4.1.3 Status Messages | AA | Messages are announced without moving focus | Add to basket, filter, submit a form | Low |
4.1.1 Parsing isn’t listed because WCAG 2.2 removed it. If a contract requires reporting against WCAG 2.1, you may still need to include it.
The 55 criteria aren’t enough: conformance requirements
WCAG 2.2 adds five requirements on top of the criteria:
- Level: every applicable A and AA criterion.
- Full pages: you can’t exclude the part that fails.
- Complete processes: if a page is part of a process, the whole process must conform.
- Accessibility-supported technologies only.
- Non-interference: anything that isn’t accessible can’t block the rest of the page.
That’s why “the home page passes the scan” doesn’t work for an online shop. If the checkout fails at payment, the whole process fails.
What an automated scan catches, and what it misses
A scan is good at repeatable technical failures: missing attributes, a missing language or title, most contrast problems, empty accessible names. It’s poor at anything that needs context: whether alt text describes the image well, whether the focus order makes sense, or whether an error message helps.
So a scan doesn’t prove conformance, and neither does a Lighthouse score of 100. It covers a lot of ground quickly and leaves people’s time for the criteria rated “Low”.
How to prioritise
- Blockers: any barrier that stops someone buying, signing up, getting in touch or logging in.
- Shared components: menus, modals and form fields. One fix corrects hundreds of pages.
- Templates and CMS: if the CMS lets editors publish images without alt text, the failure will come back.
- Ongoing checks: a site that conforms today can stop conforming in the next release. Sprout Observability reruns the automated checks every month and shows what got worse.
FAQ
Do I need to meet the AAA criteria? Not to claim AA. The W3C also doesn’t recommend requiring AAA for entire sites, because some content can’t meet it.
Can this checklist be used as an official audit? No. It’s a working guide. A conformance evaluation needs a methodology, a sample of pages and processes, and evidence for each test.
Does meeting WCAG 2.2 AA mean I comply with the EAA? Not automatically. WCAG is a technical standard; the EAA and national laws define who’s covered and what’s required. Meeting WCAG 2.2 AA helps you comply, but the legal answer depends on your service.
Start with what a machine can find. Scan your site for free with Sprout and use this checklist for the rest. No sign-up. Scan my website
The scan is an automated check. It isn’t an audit or a conformance statement.
Sources
Posted by
Jonathan Bell
Co-founder, Sprout ·