MyClawn WCAG Audit › WCAG 2.2
WCAG 2.2: what changed, and what it means for your website
WCAG 2.2 is the current version of the guidelines. It adds nine success criteria to WCAG 2.1 and removes one. Six of the new ones are at Level A or AA, so they matter to anyone aiming for AA. Here is each one with what it asks you to change.
The six new criteria at Level A and AA
| Criterion | Level | What to check on your site |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | When you Tab to a control, a sticky header, cookie banner or chat bubble must not cover it completely |
| 2.5.7 Dragging Movements | AA | Sliders, carousels, sortable lists and map panning need a way to work with single clicks or taps |
| 2.5.8 Target Size (Minimum) | AA | Buttons and links are at least 24 by 24 CSS pixels, or have that much space around them. Icon rows and footer links are the usual failures |
| 3.2.6 Consistent Help | A | If pages offer help (phone, chat, contact link), it sits in the same relative place on each |
| 3.3.7 Redundant Entry | A | A multi-step form does not make people retype what they already gave: offer it prefilled or selectable |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login does not depend on a memory or puzzle test alone. Allow paste and password managers, and offer an alternative to puzzle CAPTCHAs |
Three more were added at Level AAA: 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance and 3.3.9 Accessible Authentication (Enhanced).
What was removed
4.1.1 Parsing is gone. The W3C describes it as obsolete and removed from WCAG 2.2: browsers and assistive technology now handle the markup errors it was written for. Apart from that, the 2.0 and 2.1 criteria are, in the W3C's words, essentially the same in 2.2.
The count at Level A and AA goes from 50 in WCAG 2.1 to 55 in WCAG 2.2: six added, one removed.
Paste your address and see what fails WCAG 2.2 AA, where, and the code that fixes it. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Check my siteDo you have to meet 2.2 yet?
WCAG 2.2 became a W3C Recommendation on October 5, 2023. US rules have not moved to it: the ADA Title II web rule names 2.1 AA and Section 508 uses 2.0. Buyers increasingly do ask for it, though. Most of the audit requests in the job posts we read in November 2026 name WCAG 2.2 AA, and the current VPAT template's WCAG edition is built on 2.2.
Since 2.2 contains what 2.1 requires, testing against 2.2 costs you nothing extra and keeps the report current. The six additions are also among the cheaper ones to fix: most are CSS spacing, a sticky-header offset, or a form change.
How we test the new criteria
- Target size: measured in the rendered page for every link and button, at desktop and phone width.
- Focus not obscured: during the Tab-key walk we record whether each focused element is covered by something fixed or sticky.
- Dragging: draggable components are detected and checked for a click alternative; uncertain cases go on the human-check list.
- Consistent help, redundant entry, accessible authentication: reviewed across the audited pages and forms. Flows behind a login are outside the audit, and the report says so.
Check a page now: the free check reports target-size failures along with the classic ones.
Questions
When was WCAG 2.2 released?
It became a W3C Recommendation on October 5, 2023.
How many new success criteria does WCAG 2.2 add?
Nine: two at Level A, four at Level AA and three at Level AAA. One older criterion, 4.1.1 Parsing, was removed.
Is WCAG 2.2 backwards compatible with 2.1?
A page that meets WCAG 2.2 at a level also meets 2.1 at that level, because 2.2 keeps the 2.1 criteria. The only criterion dropped is 4.1.1 Parsing, which the W3C treats as obsolete.
What about WCAG 3.0?
WCAG 3.0 is still a W3C working draft with no release date. Nobody should plan a compliance project around it yet.
Paste your address and see what fails WCAG 2.2 AA, where, and the code that fixes it. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Check my siteMore about WCAG Audit
Sources (checked 2026-11-11): www.w3.org/WAI/standards-guidelines/wcag/new-in-22/ · www.w3.org/TR/WCAG22/ · www.itic.org/policy/accessibility/vpat · www.ada.gov/resources/2024-03-08-web-rule/