WCAG 2.2 added nine success criteria to WCAG 2.1 and removed one, 4.1.1 Parsing. Six of the nine are Level A or AA, so they count toward an AA target. Most touch parts of a CMS site that older audits skipped: sticky headers, small icons, forms and logins.
Our plain guide to web accessibility lists the nine in one table. This post takes each one in turn. You get the level, the plain meaning, a typical WordPress or Drupal failure, a test and a fix.
The short version: three criteria cause most of the work. Focus Not Obscured fails when a sticky header or cookie banner covers the focused item. Target Size fails on tiny icons and close buttons. Accessible Authentication fails when a login blocks paste or password managers. The Level A items are quick fixes, and the AAA items are optional.
WCAG 2.2 at a glance: the nine new criteria
As of October 2026, WCAG 2.2 is the current W3C Recommendation. It was first published on October 5, 2023, and the current version is dated December 12, 2024. The W3C’s What’s New in WCAG 2.2 page sums up each criterion. The WCAG 2.2 Recommendation holds the exact wording.
| Criterion | Level | Plain meaning |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | The focused item is never fully hidden by the page’s own content |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused item is hidden |
| 2.4.13 Focus Appearance | AAA | The focus indicator is big enough and changes enough to see |
| 2.5.7 Dragging Movements | AA | Anything done by dragging also works with clicks or taps |
| 2.5.8 Target Size (Minimum) | AA | Targets are at least 24 by 24 CSS pixels, or spaced apart |
| 3.2.6 Consistent Help | A | Repeated help links stay in the same order on every page |
| 3.3.7 Redundant Entry | A | No asking for the same thing twice in one process |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in does not depend on memory, puzzles or retyping |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Same, without the object and personal image exceptions |
Focus Not Obscured (2.4.11 and 2.4.12): sticky headers and banners
Meaning. When an item gets keyboard focus, the AA rule says it must not be "entirely hidden due to author-created content." Partly hidden passes. The AAA version says no part of it may be hidden.
CMS failure. A theme with a sticky header, or a cookie banner pinned to the bottom of the screen. A keyboard user tabs down, and the focused link slides under the bar. The W3C lists this as failure F110.
Test. Put the mouse away. Tab through a long page with the cookie banner still open, then tab back up. Watch for the focused item disappearing.
Fix. The Understanding document for 2.4.11 names CSS scroll-padding (technique C43). It keeps focused items clear of sticky bars. A banner can also be made modal, so it holds focus until dismissed.
Focus Appearance (2.4.13): a focus ring people can see
Meaning. This one is AAA. The focus indicator must cover at least the area of a 2 CSS pixel outline around the item. Its pixels must also change by a contrast ratio of at least 3:1 between focused and unfocused states.
CMS failure. A theme or page builder swaps the browser outline for a faint 1-pixel line. Removing the outline entirely is failure F78, which already fails 2.4.7 Focus Visible at AA.
Test. Tab through the header, a form and the footer. Compare each control focused and unfocused. A contrast checker settles close calls.
Fix. Use a solid outline at least 2 pixels thick. The W3C’s technique C40 uses a two-color indicator, such as a dark ring inside a light one. That shows on any background. Set it once in the theme’s base styles. It is AAA, but it is also one of the cheapest fixes here.
Dragging Movements (2.5.7): a click for every drag
Meaning. At AA, anything done by dragging must also work with single clicks or taps, unless dragging is essential. Scrolling and other dragging the browser provides are out of scope.
CMS failure. A sortable list, slider or kanban board from a plugin or module that only works by dragging. Donation amount sliders are a common case. The W3C lists this as failure F108.
Test. For each drag interaction, try to finish the task with single clicks only. Test with a mouse or a finger, not just the keyboard.
Fix. Add buttons or a click target. The Understanding document for 2.5.7 gives examples. Click a point on a slider track to move the thumb there. Or select an item and use up and down controls. The core editors already do this. The WordPress block toolbar has Move up and Move down buttons, per the WordPress documentation. Drupal’s admin tables have a "Show row weights" link that replaces dragging with numbers.
Target Size (Minimum) (2.5.8): 24 pixels or enough space
Meaning. At AA, pointer targets must be "at least 24 by 24 CSS pixels," with five exceptions. The main one is spacing. A smaller target passes if a 24-pixel circle centered on it overlaps no other target. Links inside a sentence are exempt. So are browser-sized controls, essential sizes, and targets with an equivalent control on the page.
CMS failure. Footer social icons at 16 pixels, side by side. Carousel dots. The small "x" on a modal or cookie banner.
Test. Open the browser’s developer tools. Inspect the clickable element, not the icon inside it. If it is under 24 by 24, measure the space to its neighbors.
Fix. Grow the clickable area, not the icon. Padding or a minimum width and height on the link does this (technique C42). The Understanding document for 2.5.8 suggests the stricter AAA size for important controls.
Consistent Help (3.2.6): help stays in the same place
Meaning. At Level A, help that repeats across pages must keep the same order relative to other page content. That covers contact details, a contact form or chat, a self-help page, and a chatbot. You do not have to offer help at all.
CMS failure. A site with several templates. The contact link sits in the header on the main site and in a sidebar in the member portal.
Test. Open five page types side by side. Note where each help item falls among the shared content.
Fix. Put help in a shared header or footer, a synced pattern or a Drupal block. Use it the same way on every template. The W3C’s technique G220 is a contact link in a consistent location.
Redundant Entry (3.3.7): do not ask twice
Meaning. At Level A, anything the user already gave in the same process must be filled in for them or offered to select. Exceptions cover essential re-entry, security and expired information. Nothing has to be stored between sessions.
CMS failure. A membership or event form asks for a billing address after the mailing address. There is no "same as" option. A form that clears every field after one error is another.
Test. Complete each multi-step form from start to finish. Note any repeated question. Then trigger an error and see what survives.
Fix. Add a "same as" checkbox or carry values forward. The Understanding document for 3.3.7 says browser autocomplete is "not considered sufficient," so the site must supply the data. Confirming a new password is allowed.
Accessible Authentication in WCAG 2.2 (3.3.8 and 3.3.9)
Meaning. At AA, no login step may require a cognitive function test, such as remembering a password or solving a puzzle. The exception is when the step offers an alternative or a helping mechanism. A password field passes when password managers can fill it and paste works. Object recognition and picking your own uploaded image are allowed at AA. The AAA version drops those two exceptions.
CMS failure. A security plugin or member login that blocks paste. A six-box code field that rejects a pasted code. A text CAPTCHA with no alternative. Blocking paste of a password or code is failure F109.
Test. Log in with a password manager. Paste a password and a two-factor code. Check every login path, including any AMS single sign-on page.
Fix. Mark up username and password fields properly (technique H100). Never block paste. Offer an email login link (technique G218) or a passkey, which our passkeys explainer covers. The Understanding document for 3.3.8 notes that an audio CAPTCHA the user must transcribe is not a valid alternative.
Why 4.1.1 Parsing was removed
4.1.1 Parsing was a Level A rule about well-formed markup, such as no duplicate IDs. The W3C’s Understanding page for Parsing says assistive technology "no longer has any need to directly parse HTML." It relies on the browser instead.
Broken markup is still a problem. The same page says many issues that failed Parsing will now fail 1.3.1 Info and Relationships or 4.1.2 Name, Role, Value. A duplicate ID that breaks a form label still fails.
Teams bound to WCAG 2.0 or 2.1 may still need to test and report 4.1.1. Check which version a contract names before dropping it from an audit template.
Testing WCAG 2.2 on WordPress and Drupal sites
Most of these failures live in shared parts: the theme, header, footer, form components and login page. Fix them there once. Start with logins and forms, then focus, then targets and dragging, then help placement. Most checks need a person with a keyboard, a mouse and a password manager.
WordPress’s accessibility coding standards expect its code to meet WCAG 2.2 AA. Drupal’s accessibility page says core targets WCAG 2.2 AA for public and admin pages. Themes, plugins and contributed modules are where sites fall short. Test them after every major update.
See what Drupal 10 end of life means for your site and our guide to the Drupal Webform advisories. Documents need their own checks, covered in our accessible PDF checklist. For what may follow 2.2, see the September WCAG 3 draft.
Frequently Asked Questions
How many new success criteria are in WCAG 2.2?
Nine. Two are Level A, four are Level AA and three are Level AAA. WCAG 2.2 also removed 4.1.1 Parsing.
Which new WCAG 2.2 criteria count toward Level AA?
Six: 2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8. An AA target includes every Level A criterion.
Does WCAG 2.2 AA require 44-pixel touch targets?
No. The AA rule, 2.5.8, sets 24 by 24 CSS pixels, with a spacing exception. The stricter 2.5.5 Target Size (Enhanced) is Level AAA.
Do CAPTCHAs fail WCAG 2.2?
A puzzle or text CAPTCHA on login fails 3.3.8 unless an alternative is offered. Object recognition CAPTCHAs pass at AA but not at AAA.
Does browser autofill satisfy Redundant Entry?
No. The W3C says browser autocomplete is not sufficient. The site must fill in the earlier answer or offer it to select.
Do we still need to test 4.1.1 Parsing?
Only if a contract or rule names WCAG 2.0 or 2.1. Many markup errors it caught still fail 1.3.1 or 4.1.2.
Does Consistent Help mean we must add a chat or phone number?
No. It only says that help repeated across pages stays in the same relative order.
Is Focus Appearance required for WCAG 2.2 AA?
No. 2.4.13 is Level AAA. A visible focus indicator is still required at AA under 2.4.7 Focus Visible.