WCAG 2.2 is the latest version of the Web Content Accessibility Guidelines from the W3C. It builds on WCAG 2.1 and the POUR principles (Perceivable, Operable, Understandable, Robust), adding nine new success criteria focused on users with cognitive, low-vision, and motor disabilities.

Understanding WCAG 2.2: The Complete Practical Guide (2026)

Q: How many new success criteria does WCAG 2.2 add?

WCAG 2.2 adds nine new success criteria covering focus visibility and appearance, dragging movements, target size, consistent help, redundant entry, and accessible authentication.

Q: What was removed in WCAG 2.2?

Success criterion 4.1.1 Parsing was removed. Modern browsers and assistive technologies now handle imperfect HTML reliably, so strict parsing is no longer a formal requirement - though clean, semantic HTML remains a best practice.

Q: Is WCAG 2.2 a legal requirement?

WCAG itself is a technical standard, not a law, but it is the standard most accessibility laws reference, including the ADA, Section 508, the European Accessibility Act, and AODA. WCAG 2.2 AA is quickly becoming the expected benchmark and is being incorporated into regulations such as the EU's EN 301 549.

Q: What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 keeps everything in 2.1 and adds nine new success criteria, while removing 4.1.1 Parsing. The new criteria emphasize keyboard focus visibility, easier interactions, larger targets, and more accessible authentication and help.

Q: How do I test my website for WCAG 2.2 compliance?

Combine automated scanning tools with manual testing using a keyboard and screen reader. Automated tools catch code-level issues like contrast and missing alt text quickly, while manual testing confirms judgment-based criteria such as focus order, target size, and accessible authentication.

Jan 16, 2026

Understanding WCAG 2.2: The Complete Practical Guide (2026)

WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, and in 2026 it has become the benchmark for accessible, legally defensible websites. This pillar guide is your single starting point: it explains what WCAG 2.2 is, breaks down all nine new success criteria, shows exactly what changed from WCAG 2.1, maps the standard to the laws that apply to you, and gives you a practical path to implement and test it. Throughout, you'll find links to deeper guides on each topic so you can go as deep as you need.

TL;DR: WCAG 2.2 keeps everything from WCAG 2.1, adds nine new success criteria (focused on keyboard focus visibility, easier interactions, larger targets, and accessible authentication), and removes the old 4.1.1 Parsing requirement. Aim for Level AA, prioritize the new criteria, run an accessibility audit with the right testing tools, and bake testing into your workflow.

What Are WCAG 2.2 Accessibility Standards?

WCAG is developed by the World Wide Web Consortium (W3C) to make digital content accessible to people with disabilities. It is organized around four principles - POUR:

Perceivable - users must be able to perceive the information, through alternative text for images, sufficient color contrast, and content that works with a screen reader.
Operable - navigation and controls must be usable by keyboard and assistive devices, with no keyboard traps and helpful skip links.
Understandable - content and interactions must be predictable and easy to comprehend.
Robust - content must work with current and future assistive technologies.

WCAG 2.2 is backward-compatible with 2.1: meeting 2.2 means you also meet 2.1. Its new criteria were identified through extensive user research and litigation analysis, with a strong emphasis on cognitive, low-vision, and motor accessibility.

WCAG Conformance Levels: A, AA, and AAA

Every success criterion is assigned a conformance level. Level A is the minimum baseline; Level AA is the standard most laws require and the practical target for nearly every website; Level AAA is the highest bar, reserved for specialized or high-stakes content. Unless you have a specific reason to go further, target WCAG 2.2 Level AA.

The 9 New WCAG 2.2 Success Criteria Explained

These nine criteria are the heart of WCAG 2.2. Several relate to keyboard focus management and pointer interactions:

2.4.11 Focus Not Obscured (Minimum) - AA: a keyboard-focused element must not be entirely hidden by author content like sticky headers or modals. Fix with z-index adjustments, repositioning, or scrolling the focused element into view.
2.4.12 Focus Not Obscured (Enhanced) - AAA: extends the above so the focused element is not obscured at all.
2.4.13 Focus Appearance - AAA: focus indicators must be large enough and high-contrast enough to be clearly visible.
2.5.7 Dragging Movements - AA: any drag interaction must also be achievable with a single pointer (a simple click or tap).
2.5.8 Target Size (Minimum) - AA: interactive targets must be at least 24 by 24 CSS pixels, or have adequate spacing.
3.2.6 Consistent Help - A: if help mechanisms (contact links, support) are provided, they must appear in the same relative location across pages, supporting users with cognitive disabilities.
3.3.7 Redundant Entry - A: information a user already entered in a process must not be required again - auto-populate it or let them select it.
3.3.8 Accessible Authentication (Minimum) - AA: logins must not rely on a cognitive function test (like memorizing or transcribing) without an accessible alternative.
3.3.9 Accessible Authentication (Enhanced) - AAA: a stricter version removing cognitive-test exceptions.

WCAG 2.2 vs WCAG 2.1: What Changed

The headline change is the nine added criteria above. The other notable change is a removal:

4.1.1 Parsing was removed. It previously required clean, valid HTML so assistive technologies could interpret content. Modern browsers and screen readers now handle malformed HTML reliably, so the focus has shifted to actual user experience rather than code validity. Clean, semantic HTML remains a best practice - it's simply no longer a formal success criterion.

Who Requires WCAG 2.2 (and When)?

WCAG itself is a technical standard, not a law - but it's the standard nearly every accessibility regulation references. WCAG 2.2 AA is quickly becoming the expected benchmark worldwide. Here's how it maps to the major frameworks:

United States - the ADA: courts increasingly treat WCAG AA as the yardstick for the Americans with Disabilities Act. See our beginner's guide to WCAG and ADA compliance.
US federal - Section 508: federal agencies and their vendors must meet WCAG-based requirements. Learn more in our Section 508 compliance software guide and Section 508 hub.
European Union - the EAA: the European Accessibility Act references WCAG via EN 301 549. See our EAA compliance hub.
Canada (Ontario) - AODA: the Accessibility for Ontarians with Disabilities Act points to WCAG. Explore our AODA compliance hub.

How to Implement WCAG 2.2: A Step-by-Step Process

Audit against WCAG 2.2 AA. Combine automated scanning with manual testing using our website accessibility audit checklist and the best accessibility testing tools - paying special attention to the nine new criteria.
Fix the foundations first. Address color contrast (check pairs with the WCAG contrast checker), alt text, keyboard operability and skip links, and choose accessible fonts for readability.
Prioritize the new 2.2 criteria most likely to affect your interface: focus visibility, target size, dragging alternatives, and accessible authentication.
Test with assistive technology and real users to validate judgment-based criteria automation can't confirm. Run a quick scan with the WCAG checker as a baseline.
Publish an accessibility statement documenting your conformance - use our accessibility statement generator (see what an accessibility statement is).
Monitor continuously so new pages and features don't reintroduce issues. An accessibility widget plus ongoing scanning keeps you compliant between audits.

Frequently Asked Questions

What is WCAG 2.2?

The latest version of the Web Content Accessibility Guidelines from the W3C. It builds on WCAG 2.1 and the POUR principles, adding nine new success criteria for users with cognitive, low-vision, and motor disabilities.

How many new success criteria does WCAG 2.2 add?

Nine - covering focus visibility and appearance, dragging movements, target size, consistent help, redundant entry, and accessible authentication.

What was removed in WCAG 2.2?

Success criterion 4.1.1 Parsing, because modern browsers and assistive tech 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, but it's the standard most laws reference - including the ADA, Section 508, the EAA, and AODA. WCAG 2.2 AA is becoming the expected benchmark and is being incorporated into regulations like EN 301 549.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 keeps everything in 2.1, adds nine new criteria, and removes 4.1.1 Parsing. The additions emphasize focus visibility, easier interactions, larger targets, and accessible authentication and help.

What are the WCAG conformance levels A, AA, and AAA?

Level A is the minimum baseline, Level AA is the standard most laws require and the practical target for most sites, and Level AAA is the highest level for specialized content. Most organizations target WCAG 2.2 Level AA.

How do I test my website for WCAG 2.2 compliance?

Combine automated scanning tools with manual keyboard and screen reader testing. Automation catches code-level issues like contrast and missing alt text quickly; manual testing confirms judgment-based criteria such as focus order, target size, and accessible authentication.

This pillar links to focused resources across the WebAbility library:

Standards & criteria: Color Contrast for Accessibility · Contrast Ratio (glossary) · Target Size (glossary) · Focus Management (glossary)
Build & test: Website Accessibility Audit Checklist · Web Accessibility Testing Tools · WCAG Checker · WCAG Contrast Checker · Skip to Main Content Links · What Is Alt Text · Most Accessible Fonts
Laws & regions: WCAG & ADA Compliance Guide · Section 508 Hub · EAA Compliance Hub · AODA Compliance Hub
Get compliant: Accessibility Statement Generator · Accessibility Widget

Conclusion

WCAG 2.2 is an evolution, not a reinvention: master the nine new criteria, retire your reliance on 4.1.1 Parsing, and target Level AA. Audit your site, prioritize the new requirements, remediate by severity, document your conformance, and monitor continuously. Use the linked guides and tools above to go deeper on any piece - together they give you everything you need to meet the standard that defines accessible, compliant digital experiences in 2026.

Quick Questions

Tap to ask AI about this article

Ask Questions

AI assistant for this article

Ready to help!

Ask me anything about this article

Understanding WCAG 2.2: The Complete Practical Guide (2026)

Jan 16, 2026

Understanding WCAG 2.2: The Complete Practical Guide (2026)

What Are WCAG 2.2 Accessibility Standards?

WCAG is developed by the World Wide Web Consortium (W3C) to make digital content accessible to people with disabilities. It is organized around four principles - POUR:

Perceivable - users must be able to perceive the information, through alternative text for images, sufficient color contrast, and content that works with a screen reader.
Operable - navigation and controls must be usable by keyboard and assistive devices, with no keyboard traps and helpful skip links.
Understandable - content and interactions must be predictable and easy to comprehend.
Robust - content must work with current and future assistive technologies.

WCAG Conformance Levels: A, AA, and AAA

The 9 New WCAG 2.2 Success Criteria Explained

These nine criteria are the heart of WCAG 2.2. Several relate to keyboard focus management and pointer interactions:

2.4.11 Focus Not Obscured (Minimum) - AA: a keyboard-focused element must not be entirely hidden by author content like sticky headers or modals. Fix with z-index adjustments, repositioning, or scrolling the focused element into view.
2.4.12 Focus Not Obscured (Enhanced) - AAA: extends the above so the focused element is not obscured at all.
2.4.13 Focus Appearance - AAA: focus indicators must be large enough and high-contrast enough to be clearly visible.
2.5.7 Dragging Movements - AA: any drag interaction must also be achievable with a single pointer (a simple click or tap).
2.5.8 Target Size (Minimum) - AA: interactive targets must be at least 24 by 24 CSS pixels, or have adequate spacing.
3.2.6 Consistent Help - A: if help mechanisms (contact links, support) are provided, they must appear in the same relative location across pages, supporting users with cognitive disabilities.
3.3.7 Redundant Entry - A: information a user already entered in a process must not be required again - auto-populate it or let them select it.
3.3.8 Accessible Authentication (Minimum) - AA: logins must not rely on a cognitive function test (like memorizing or transcribing) without an accessible alternative.
3.3.9 Accessible Authentication (Enhanced) - AAA: a stricter version removing cognitive-test exceptions.

WCAG 2.2 vs WCAG 2.1: What Changed

The headline change is the nine added criteria above. The other notable change is a removal:

Who Requires WCAG 2.2 (and When)?

United States - the ADA: courts increasingly treat WCAG AA as the yardstick for the Americans with Disabilities Act. See our beginner's guide to WCAG and ADA compliance.
US federal - Section 508: federal agencies and their vendors must meet WCAG-based requirements. Learn more in our Section 508 compliance software guide and Section 508 hub.
European Union - the EAA: the European Accessibility Act references WCAG via EN 301 549. See our EAA compliance hub.
Canada (Ontario) - AODA: the Accessibility for Ontarians with Disabilities Act points to WCAG. Explore our AODA compliance hub.

How to Implement WCAG 2.2: A Step-by-Step Process

Audit against WCAG 2.2 AA. Combine automated scanning with manual testing using our website accessibility audit checklist and the best accessibility testing tools - paying special attention to the nine new criteria.
Fix the foundations first. Address color contrast (check pairs with the WCAG contrast checker), alt text, keyboard operability and skip links, and choose accessible fonts for readability.
Prioritize the new 2.2 criteria most likely to affect your interface: focus visibility, target size, dragging alternatives, and accessible authentication.
Test with assistive technology and real users to validate judgment-based criteria automation can't confirm. Run a quick scan with the WCAG checker as a baseline.
Publish an accessibility statement documenting your conformance - use our accessibility statement generator (see what an accessibility statement is).
Monitor continuously so new pages and features don't reintroduce issues. An accessibility widget plus ongoing scanning keeps you compliant between audits.