WCAG 2.2 AA checklist: what changed and what to test
A plain-language WCAG 2.2 AA checklist: the six new Level A and AA criteria, the removal of 4.1.1 and the checks behind the most common failures.
Last updated . General information, not legal advice.
The Web Content Accessibility Guidelines (WCAG) 2.2 became a W3C Recommendation in October 2023. It is the current version of the standard behind most accessibility laws, contracts and audits. Level AA is the target that nearly everyone means when they say "accessible". This checklist covers what is new in 2.2 and the checks behind the failures that show up most often on real sites.
What is new in WCAG 2.2
WCAG 2.2 adds nine success criteria, six of them at Level A or AA. It also removes 4.1.1 Parsing, which no longer matters with modern browsers. Because 2.2 builds on 2.1, content that meets 2.2 AA also meets 2.1 AA, the standard named in the Title II and Section 504 rules.
| Criterion | Level | What to check |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused element is not completely hidden behind sticky headers, cookie banners or chat widgets. |
| 2.5.7 Dragging Movements | AA | Anything done by dragging, such as a slider or sortable list, can also be done with a single click or tap. |
| 2.5.8 Target Size (Minimum) | AA | Interactive targets are at least 24 by 24 CSS pixels, or have enough spacing, with a few exceptions. |
| 3.2.6 Consistent Help | A | If help (contact, chat, FAQ) appears on several pages, it is in the same place each time. |
| 3.3.7 Redundant Entry | A | Do not make people re-enter information they already gave in the same process. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in does not depend on solving a puzzle or transcribing a code from memory. Allow password managers and paste. |
The checks behind the most common failures
Large annual analyses of home pages, such as the WebAIM Million, keep finding the same few failures behind most detected errors. Start here.
- Color contrast (1.4.3, 1.4.11). Normal text needs a contrast ratio of at least 4.5:1, large text (18 point, or 14 point bold) needs 3:1, and meaningful interface parts such as input borders and icons need 3:1. Test pairs with the contrast checker.
- Text alternatives (1.1.1). Every meaningful image has alt text that says what it conveys. Decorative images have an empty alt attribute.
- Form labels (1.3.1, 3.3.2, 4.1.2). Every field has a visible label that is programmatically connected to it. A placeholder is not a label.
- Link and button names (2.4.4, 4.1.2). No empty links or buttons. "Click here" and "Read more" should say where they go.
- Page language (3.1.1). The page declares its language so screen readers pronounce it correctly.
- Keyboard access (2.1.1, 2.4.7). Everything works with the keyboard alone, and you can always see where focus is.
- Headings and landmarks (1.3.1, 2.4.1, 2.4.6). One clear heading structure, a way to skip repeated navigation, and the main regions marked up.
- Error handling (3.3.1, 3.3.3). Errors are identified in text and say how to fix them.
- Names and roles for custom widgets (4.1.2). Custom menus, tabs and dialogs expose the right roles and states. The ARIA inspector helps you see what a screen reader will announce.
- Time-based media (1.2.x). Captions for prerecorded video and a text alternative for audio.
What automation can and cannot check
An automated scan reliably catches things that have a clear right or wrong answer: missing alt attributes, contrast failures, missing labels, invalid ARIA and empty links. It cannot judge whether alt text is meaningful, whether focus order makes sense, whether captions are accurate or whether an error message is helpful. Plan for both. A scan is how you cover every page fast and keep watching; a human pass on your key journeys is how you find the rest.
Our free audit maps every finding to the exact success criterion and shows how widespread it is. The Monitor and Pro plans rescan on a schedule and track what you have fixed.
Frequently asked questions
What is new in WCAG 2.2?
WCAG 2.2 adds nine success criteria, six of them at Level A or AA: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). It also removes criterion 4.1.1 Parsing.
Does WCAG 2.2 replace WCAG 2.1?
WCAG 2.2 builds on 2.1 and is backward compatible in practice: content that meets 2.2 AA also meets 2.1 AA. The Title II and Section 504 rules name 2.1 AA, so many organizations test to 2.2 AA to be covered either way.
What is the minimum target size in WCAG 2.2?
Success criterion 2.5.8 requires interactive targets to be at least 24 by 24 CSS pixels, with exceptions for spacing, inline links, user agent controls and essential presentation.
Can an automated scan check all of WCAG 2.2 AA?
No. Automated tools reliably test only part of the criteria. Things such as meaningful alt text, logical focus order, caption accuracy and clear error messages need a person to judge, so a scan is the starting point, not the finish line.
See where your site stands
Request a free WCAG 2.2 AA audit of your website. The report names the exact success criterion for every finding and the deadline that applies to you.