WCAG 2.2 is the current version of the W3C's Web Content Accessibility Guidelines, published as a W3C Recommendation in October 2023. It keeps nearly everything from WCAG 2.1 and adds nine new success criteria, six of them at levels A and AA, the levels that most audits and contracts ask for. Many websites were audited against 2.1 and have never been checked against the additions. This WCAG 2.2 checklist explains each new requirement in plain terms and how to test it. It is technical guidance, not legal advice.
Where WCAG 2.2 stands in 2026
For private businesses in the United States, the ADA does not name a technical standard for websites. The Department of Justice's guidance on web accessibility points to WCAG as helpful guidance, and demand letters and settlements commonly cite WCAG 2.0 or 2.1 Level AA. For state and local governments, the Department's 2024 Title II rule adopted WCAG 2.1 AA, and in April 2026 it extended the compliance dates to April 2027 for larger public entities and April 2028 for smaller ones. Content that meets WCAG 2.2 AA generally meets 2.1 AA as well, so building to 2.2 covers both. WCAG 3 is still a working draft, not a standard anyone can conform to yet. If you have received a demand letter or have a specific legal obligation, speak to an attorney.
The new WCAG 2.2 success criteria at levels A and AA
| Criterion | Level | In short |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | The element with keyboard focus is not completely hidden by other content |
| 2.5.7 Dragging Movements | AA | Anything done by dragging can also be done with single taps or clicks |
| 2.5.8 Target Size (Minimum) | AA | Click and tap targets are at least 24 by 24 CSS pixels, or have enough space around them |
| 3.2.6 Consistent Help | A | Help options repeated across pages appear in the same relative order |
| 3.3.7 Redundant Entry | A | Information already entered in a process is not requested again |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in does not depend on a memory or puzzle test without an alternative |
The other three new WCAG 2.2 success criteria (2.4.12, 2.4.13 and 3.3.9) are at level AAA. One older criterion, 4.1.1 Parsing, was removed as obsolete. The W3C's What's New in WCAG 2.2 page gives the official wording.
A WCAG 2.2 checklist: how to test each new criterion
Focus not obscured
Press Tab through every page template. Sticky headers, cookie banners, chat buttons and promotional bars are the usual culprits: when the focused link slides underneath them, a keyboard user loses their place. At level AA the focused item must not be entirely hidden; partly covered passes, though it is better avoided.
Target size minimum
The target size minimum is 24 by 24 CSS pixels, or smaller targets spaced so that a 24-pixel circle centered on each one does not overlap another target or its circle. Check icon buttons, pagination, close buttons on pop-ups, quantity steppers and star ratings, especially on mobile. Links inside a sentence of text are an exception.
Dragging movements
Price range sliders, drag-and-drop file uploads, sortable lists and maps all need a single-pointer alternative: arrow buttons, a field for typing the value, a "choose file" button. This criterion is about pointer users who cannot hold and drag; keyboard access is a separate requirement.
Consistent help
If a phone number, contact link, chat or FAQ link appears on several pages, keep it in the same relative order everywhere, for example always in the header, with the contact link after the phone number. The criterion does not require you to offer help, only to be consistent where you do.
Redundant entry
In a multi-step form or checkout, do not make people type the same information twice. Offer "billing address same as shipping", or carry the value over from the earlier step. Asking for a password again for security reasons is allowed.
Accessible authentication
Remembering a password counts as a cognitive test, so login forms must work with password managers and allow pasting; blocking paste in password or one-time code fields fails. Puzzles that ask users to transcribe distorted characters need an alternative. At level AA, challenges that ask users to recognize common objects or their own content are allowed exceptions. Passkeys, email links and sign-in through another account all help.
From audit to WCAG remediation
An audit report is only useful if it leads to fixes in the right order. For WCAG remediation, start with barriers in the tasks that matter most: finding a product or service, the contact or quote form, checkout and login. Fix problems in the theme or component that produces them rather than page by page, so a single change repairs every page that uses it. Re-test with the keyboard and a screen reader after each round. Overlay widgets that promise one-line fixes do not change the underlying code that assistive technology reads, which is why they are no substitute for remediation.
Any claim of WCAG 2.2 compliance should rest on evidence: which pages and templates were tested, when, against which level, and which known issues remain. Our ADA compliance and accessibility remediation service works this way: we audit against WCAG 2.1 AA, list the additional 2.2 criteria separately and fix the code in your theme.
Writing an accessibility statement
An accessibility statement tells visitors which standard you aim for, what you know is not yet accessible and how to reach you if something blocks them. Keep it honest: name the target, for example WCAG 2.2 Level AA, give the date of the last review, list known problems with a plan to fix them, and provide an email address or form that someone actually reads. A statement claiming full conformance that a visitor can disprove in a minute does more harm than good.
Frequently asked questions: wcag 2.2
Should we aim for WCAG 2.1 or 2.2?
Build and test to 2.2 AA. It contains nearly everything in 2.1, the extra checks are modest, and the references most commonly cited today are covered along the way.
Can an accessible website stop ADA lawsuits?
No one can promise that. Fixing real barriers, documenting the work and responding to complaints lowers the risk; questions about a specific claim belong with an attorney.
Are automated scanners enough to test WCAG 2.2?
No. Scanners catch many contrast, label and markup issues, but most of the new 2.2 criteria, such as focus hidden behind a sticky header or a slider that only works by dragging, need a person to test them.
Does this matter for stores selling to Europe?
The European Accessibility Act has applied since June 28, 2025 to many e-commerce services offered to consumers in the EU, with its own rules and an exemption for the smallest businesses. If you sell to EU consumers, ask counsel how it applies to you.
Want to know where your site stands against WCAG 2.2? Our WCAG audit and accessibility remediation page explains what we test, from screen readers and keyboard access to contrast and forms, and how the fixes are delivered. Planning a redesign? E-commerce UX and UI design is the point to build accessible patterns in from the start. Contact us with your site address and the main tasks visitors complete on it, and we can scope an audit.
