Getting Started with WCAG 2.2: What Changed and What You Need to Do

What WCAG 2.2 actually changes for your team

Web Content Accessibility Guidelines (WCAG) 2.2 became the official W3C Recommendation in October 2023. It is the latest version of the international standard that defines how to make web content accessible to people with disabilities. If your organization targets WCAG compliance — whether for legal, ethical, or business reasons — version 2.2 is now the benchmark.

The update is not a revolution. It is an evolution: nine new success criteria, one removed criterion, and a sharper focus on cognitive accessibility and mobile interactions. But several of these criteria address gaps that have frustrated users for years, and regulators are already referencing 2.2 in enforcement guidance.

The nine new success criteria at a glance

WCAG 2.2 introduces criteria across three conformance levels. Here is what was added and why:

What was removed and why

WCAG 2.2 is the first version to remove a success criterion. Success Criterion 4.1.1 Parsing required that content could be reliably parsed — essentially, that HTML was well-formed with no duplicate IDs, proper nesting, and complete start/end tags.

The W3C's rationale: browser error handling has become so consistent that parsing issues no longer create real accessibility barriers. Assistive technologies rely on the browser's accessibility tree, not raw HTML parsing. Removing 4.1.1 acknowledges this reality.

The criteria that matter most in practice

Not all nine criteria carry equal weight for most teams. Here are the four that will require the most attention:

1. Focus Not Obscured (2.4.11) — Level AA

Sticky headers, cookie banners, and chat widgets routinely cover focused elements. A keyboard user tabs to a link, but it is hidden behind a fixed toolbar. They cannot see what they are interacting with.

WCAG 2.2 requires that the focused element is not entirely hidden by author-created content. The enhanced version (2.4.12, Level AAA) goes further and requires that no part of the focused element is obscured.

2. Target Size (2.5.8) — Level AA

Interactive elements must be at least 24×24 CSS pixels. There are exceptions for inline links within text, elements where the size is controlled by the user agent, and cases where a larger target is available elsewhere on the page.

3. Accessible Authentication (3.3.8) — Level AA

Login flows must not depend on cognitive function tests — meaning users should not be required to memorize, transcribe, or solve puzzles to authenticate. Alternatives like password managers (copy-paste support), passkeys, email/SMS codes, or biometrics satisfy this criterion.

4. Redundant Entry (3.3.7) — Level A

If a user has already provided information during a session (such as their shipping address), the site must not require them to enter it again. Auto-populate it, let them select from previously entered data, or remove the duplicate field.

This criterion addresses a long-standing frustration for users with motor or cognitive disabilities. Multi-step forms and checkout flows are the primary areas to audit.

How WCAG conformance levels work

If you are new to WCAG, the three conformance levels can be confusing. Here is how they work:

A practical implementation roadmap

Here is a straightforward approach to getting your site to WCAG 2.2 Level AA:

Common mistakes teams make with WCAG 2.2

  • Treating it as a one-time project. Your site changes constantly. Accessibility conformance must be monitored continuously, not audited once and forgotten.
  • Relying only on automated scans. Automated tools detect roughly 20–30% of WCAG non-conformities. The remaining 70–80% require manual evaluation and assistive technology testing.
  • Ignoring the new criteria. Teams that met WCAG 2.1 AA sometimes assume 2.2 requires no additional work. The six new AA criteria — especially Focus Not Obscured, Target Size, and Accessible Authentication — often require specific remediation.
  • Targeting AAA everywhere. Level AAA is aspirational. Some criteria (like 1.4.8 Visual Presentation) are impractical for certain content types. Focus on solid AA conformance first.
  • Skipping real-user testing. Automated tools and manual checklists are not substitutes for testing with people who use assistive technologies. If your budget allows it, include users with disabilities in your testing process.

Where WCAG 2.2 fits in the legal landscape

WCAG is a technical standard, not a law. But it is referenced by laws and regulations worldwide:

  • United States: The DOJ's April 2024 rule mandates WCAG 2.1 AA for state and local government websites under ADA Title II. Courts in ADA Title III cases routinely reference WCAG as the benchmark, and 2.2 is increasingly cited.
  • European Union: The European Accessibility Act (EAA), enforceable from June 2025, references the harmonized standard EN 301 549, which incorporates WCAG 2.1 and is expected to update to 2.2.
  • Procurement: Section 508 (US federal), EN 301 549 (EU), and similar standards in Canada, Australia, and Japan all reference WCAG-level requirements.

Next steps

If you are preparing for WCAG 2.2 Level AA conformance:

  • Run a baseline scan to understand your current conformance gap. Start a free scan with inspekter to identify machine-detectable non-conformities across your site.
  • Review the six new AA criteria against your existing interfaces, paying special attention to sticky elements, small touch targets, and authentication flows.
  • Build accessibility into your development workflow so that new features ship conformant rather than requiring retroactive fixes.

Accessibility is not a checkbox to clear once — it is a design practice that benefits every user and becomes more straightforward the earlier you integrate it.