Understanding WCAG 2.2: The Complete Practical Guide (2027)
Last updated: October 20, 2026
Short answer: WCAG 2.2 is the current version of the Web Content Accessibility Guidelines. The W3C published it on 5 October 2023. It keeps all of WCAG 2.1 except 4.1.1 Parsing and adds nine new success criteria, six of them at Level A or AA. No major law requires WCAG 2.2 by name yet, but a site that meets WCAG 2.2 AA also meets the WCAG 2.1 AA and 2.0 AA versions that the ADA, the European Accessibility Act, Section 508 and AODA use.
This guide covers the four principles, the nine new criteria and how to test each one, what changed from WCAG 2.1, which law uses which version, and a step-by-step plan. If you need the wider picture first, read WCAG guidelines explained or what WCAG stands for.
What Are the WCAG 2.2 Accessibility Standards?
WCAG is developed by the World Wide Web Consortium (W3C) to make digital content usable by people with disabilities. It is organised around four principles, known as POUR:
- Perceivable: users can perceive the information, through alternative text for images, enough color contrast, and content that works with a screen reader.
- Operable: every control works with a keyboard and assistive devices, with no keyboard traps and with useful skip links.
- Understandable: content and interactions are predictable and easy to follow.
- Robust: content works with current and future browsers and assistive technologies.
WCAG 2.2 is backward compatible with 2.1 and 2.0, with one exception: 4.1.1 Parsing no longer exists in 2.2. A page that meets 2.2 AA meets 2.1 AA and 2.0 AA.
WCAG Conformance Levels: A, AA, and AAA
Every success criterion has a level. Level A is the minimum; failing it often blocks some users completely. Level AA is the level laws, procurement rules and contracts require. Level AAA is the highest level; the W3C does not recommend it as a whole-site target because some content cannot meet it. WCAG 2.2 Level A and AA together hold 55 success criteria. Target WCAG 2.2 Level AA unless a contract says otherwise.
The 9 New WCAG 2.2 Success Criteria Explained
Six of the nine new criteria are Level A or AA, so they count for compliance. Three are Level AAA.
| Criterion | Level | What it requires | How to test it |
|---|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A keyboard-focused element is not entirely hidden by sticky headers, cookie banners or chat bubbles. | Tab through the page with a sticky header and a cookie banner open. Every focused item must stay at least partly visible. |
| 2.5.7 Dragging Movements | AA | Anything done by dragging also works with a single click or tap. | Find every slider, sortable list and drag-and-drop. Check that a button or tap alternative exists. |
| 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. | Inspect small icon buttons, close buttons and inline links in menus. Measure the box or the spacing. |
| 3.2.6 Consistent Help | A | Help links, contact details or chat appear in the same place on every page. | Compare the header and footer on five page types. Help must be in the same relative order. |
| 3.3.7 Redundant Entry | A | Users are not asked to type the same information twice in one process. | Walk through checkout or sign-up. Shipping and billing details must be auto-filled or selectable. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login does not depend on a memory test or puzzle without an alternative. Password managers and paste must work. | Try logging in with a password manager and with paste in the password field. Check for CAPTCHA with no alternative. |
The three Level AAA criteria are 2.4.12 Focus Not Obscured (Enhanced) (the focused element is not obscured at all), 2.4.13 Focus Appearance (the focus indicator is large and contrasting enough), and 3.3.9 Accessible Authentication (Enhanced) (no cognitive test at all). Most laws do not require them.
Work through every criterion with our interactive WCAG 2.2 checklist. For keyboard focus, see focus management; for target sizes, see target size. Run a free WCAG 2.2 scan to see which of these your site fails today.
WCAG 2.2 vs WCAG 2.1: What Changed
The headline change is the nine added criteria. The only removal is 4.1.1 Parsing. It required valid HTML so assistive technology could read the page. Browsers and screen readers now repair broken markup reliably, so the W3C dropped the criterion. Clean, semantic HTML is still best practice; it is just no longer a pass/fail test.
Is WCAG 2.2 Required by Law? Which Version Each Law Uses
WCAG is a technical standard, not a law. It becomes mandatory when a law, regulation or contract adopts it. Each framework names its own version:
| Law | Who it covers | WCAG version |
|---|---|---|
| ADA Title II (US) | State and local governments, including public schools, colleges and transit | WCAG 2.1 AA. Compliance dates: April 26, 2027 for entities with 50,000 or more people, and April 26, 2028 for smaller entities and special districts. |
| ADA Title III (US) | Businesses open to the public | No technical standard in the regulation. Demand letters, settlements and DOJ guidance use WCAG AA as the benchmark. |
| Section 508 (US) | Federal agencies and the technology they buy | WCAG 2.0 AA |
| European Accessibility Act (EU) | E-commerce, banking, e-books and other products and services, since June 28, 2025 | WCAG 2.1 AA through EN 301 549 |
| AODA (Ontario, Canada) | Public sector and organisations with 50 or more employees | WCAG 2.0 AA |
The ADA Title II dates come from the Department of Justice interim final rule published on April 20, 2026 (ada.gov). Federal rules are at section508.gov. For the ADA in detail, see our ADA compliance guide, and for the EU, the European Accessibility Act guide.
Why build to 2.2 if the law says 2.1? Because 2.2 AA covers every older version, new contracts and procurement checklists increasingly ask for it, and fixing focus, target size and login problems once is cheaper than a second audit later. If you sell software to government or enterprise buyers, they will usually ask for a VPAT or Accessibility Conformance Report; see how we prepare a VPAT/ACR.
How to Implement WCAG 2.2: A Step-by-Step Process
- Audit against WCAG 2.2 AA. Combine automated scanning with manual testing. Use our website accessibility audit checklist and the best accessibility testing tools, and pay special attention to the six new A and AA criteria. If you need a report to hand to a buyer or lawyer, our manual WCAG audit covers every Level A and AA criterion.
- Fix the foundations first. Address color contrast (check pairs with the WCAG contrast checker), alt text, keyboard operability and skip links. Choose accessible fonts for readability.
- Fix the new 2.2 criteria that hit your interface: sticky elements covering focus, small tap targets, drag-only controls, and logins that block password managers.
- Test with assistive technology. Automated tools reliably catch about 30 to 40% of issues. A keyboard and a screen reader such as NVDA or VoiceOver confirm the rest. Run the WCAG checker as a baseline.
- Publish an accessibility statement. Use our accessibility statement generator (see what an accessibility statement is).
- Monitor continuously. New pages, plugins and content bring issues back. Scan on a schedule. The WebAbility Accessibility Enhancer adds ongoing scanning and fixes between audits.
Common Mistakes with WCAG 2.2
- Treating a clean automated scan as proof of compliance.
- Letting a sticky header or cookie banner cover the focused element (2.4.11).
- Shipping 16-pixel icon buttons packed together on mobile (2.5.8).
- Blocking paste in password fields, or adding a puzzle CAPTCHA with no alternative (3.3.8).
- Building to WCAG 2.2 once and never retesting after new content ships.
Frequently Asked Questions
What is WCAG 2.2?
The current version of the Web Content Accessibility Guidelines, a W3C Recommendation published on 5 October 2023. It builds on WCAG 2.1 and the POUR principles, adds nine success criteria and removes 4.1.1 Parsing.
How many new success criteria does WCAG 2.2 add?
Nine. Six are Level A or AA (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) and three are Level AAA (2.4.12, 2.4.13, 3.3.9). Level A and AA together contain 55 criteria.
What was removed in WCAG 2.2?
Success criterion 4.1.1 Parsing. Browsers and assistive technologies now handle imperfect HTML reliably. Clean, semantic HTML is still best practice.
Is WCAG 2.2 a legal requirement?
WCAG is a standard, not a law. No major accessibility law names WCAG 2.2 as its only required version yet. ADA Title II requires WCAG 2.1 AA, the European Accessibility Act uses EN 301 549 (WCAG 2.1 AA), and Section 508 and AODA use WCAG 2.0 AA. A site that meets WCAG 2.2 AA also meets all of those.
What is the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 keeps every 2.1 criterion except 4.1.1 Parsing and adds nine new ones about focus visibility, dragging, target size, consistent help, redundant entry and accessible authentication.
What are the WCAG conformance levels A, AA, and AAA?
Level A is the minimum, Level AA is the level that laws and contracts require, and Level AAA is the highest level and is not recommended as a whole-site target. Most organisations target WCAG 2.2 Level AA.
How do I test my website for WCAG 2.2 compliance?
Run an automated scan first, then test by hand with a keyboard and a screen reader. Automation finds contrast and missing alt text. Manual testing confirms focus order, target size, dragging alternatives and accessible authentication.
Related Guides and Tools
- Standards and criteria: WCAG Guidelines Explained · Color Contrast for Accessibility · Contrast Ratio · Target Size · Focus Management
- Build and test: Website Accessibility Audit Checklist · Web Accessibility Testing Tools · WCAG Checker · WCAG Contrast Checker · What Is Alt Text · Most Accessible Fonts
- Laws and regions: ADA · Section 508 · EAA · AODA
- Get compliant: Manual WCAG Audit · Accessibility Enhancer · Accessibility Statement Generator
Conclusion
WCAG 2.2 is an evolution of 2.1, not a rewrite. Fix the six new A and AA criteria, drop any reliance on 4.1.1 Parsing, and target Level AA. That one target also meets the older versions every current law names. Audit, fix by severity, document your conformance and keep monitoring.
Quick Questions
Tap to ask AI about this article
