Category: Standards and Guidelines

WCAG 2.2

Also known as: WCAG, Web Content Accessibility Guidelines 2.2, WCAG 2.2

Simply put

WCAG 2.2 is the latest version of the Web Content Accessibility Guidelines, a set of technical guidelines that explain how to make websites and other digital content more usable for people with disabilities. Published by the World Wide Web Consortium (W3C), it builds on earlier versions by adding new criteria focused on helping people navigate, find content, and operate functionality more easily. It is a technical standard rather than a law, though it is often cited as a benchmark for accessibility.

Formal definition

WCAG 2.2 is a technical standard published by the W3C through the Web Accessibility Initiative (WAI) that defines how to make web content more accessible to people with disabilities. It was published as a W3C Recommendation on 5 October 2023 and adds 9 additional success criteria beyond those in WCAG 2.1; the new requirements address helping users navigate and find content, and operate functionality more easily through various inputs. Like prior versions, WCAG 2.2 organizes success criteria under conformance levels (A, AA, and AAA), with AA commonly cited as a target. WCAG 2.2 is a technical guideline and not itself a law; while it is frequently referenced as a benchmark in regulatory and legal contexts, its applicability depends on the specific jurisdiction, regulation, or agency guidance involved, and readers should consult qualified legal counsel and current rulemaking for compliance questions.

Why it matters

WCAG 2.2 represents the most current iteration of the Web Content Accessibility Guidelines, published by the W3C as a formal Recommendation on 5 October 2023. Because it builds on the widely referenced WCAG 2.0 and 2.1, organizations tracking accessibility benchmarks look to WCAG 2.2 for the newest guidance on making digital content usable by people with disabilities. Understanding the version matters because success criteria differ across versions, and the nine additional criteria in WCAG 2.2 introduce requirements not present in earlier releases.

While WCAG 2.2 is a technical standard rather than a law, it is frequently cited as a benchmark in regulatory, contractual, and legal contexts. It does not by itself impose legal obligations; whether and how it applies depends on the specific jurisdiction, regulation, or agency guidance involved. In the United States, for example, the applicable authority (such as Title II or Title III of the ADA, Section 508, or Section 504) shapes what accessibility expectations attach to a given organization, and courts and settlements have historically referenced WCAG as a benchmark rather than a codified rule.

Because requirements evolve through regulation and case law, teams should treat WCAG 2.2 conformance as one component of a broader accessibility effort rather than a guarantee of an accessible experience or legal immunity. Meeting success criteria does not by itself ensure usability for all users, and this entry is not legal advice. Organizations with compliance questions should consult qualified legal counsel and monitor current rulemaking from relevant agencies such as the Department of Justice and the U.S. Access Board.

Who it's relevant to

Accessibility engineers and developers

Technical practitioners use WCAG 2.2 to guide how they build and remediate digital content, paying particular attention to the 9 success criteria added since WCAG 2.1. They rely on the W3C's Understanding documents and Quick Reference to interpret criteria and select techniques, and should combine automated checks with manual and assistive technology testing since automated tools detect only a portion of issues.

UX and content designers

Designers benefit from WCAG 2.2's focus on helping users navigate and find content and operate functionality more easily through various inputs. Incorporating these considerations early in the design process can reduce downstream remediation, though conformance to success criteria does not by itself guarantee an accessible experience for all users.

Compliance officers and business leaders

Those responsible for accessibility programs often adopt a WCAG version and conformance level (AA is commonly cited) as an internal benchmark. Because WCAG 2.2 is a technical standard and not a law, its applicability in any given context depends on the relevant jurisdiction, regulation, or agency guidance, and adopting it does not guarantee legal immunity.

Legal counsel

Attorneys evaluating accessibility obligations may encounter WCAG 2.2 referenced as a benchmark in regulatory or legal contexts. Whether WCAG applies, and which version or level is expected, depends on the specific authority involved (for example, Title II or Title III of the ADA, Section 508, or Section 504). This entry is not legal advice; counsel should consult current rulemaking and case law for compliance questions.

Inside WCAG

Version and Publication

WCAG 2.2 is a version of the Web Content Accessibility Guidelines published by the W3C through the Web Accessibility Initiative (WAI). It builds on WCAG 2.0 and 2.1, remaining backward-compatible so that content conforming to 2.2 generally also conforms to earlier 2.x versions.

Conformance Levels (A, AA, AAA)

Like earlier versions, WCAG 2.2 organizes success criteria into three conformance levels: A, AA, and AAA. Level AA is the level most commonly cited as a target in policy, procurement, and settlement contexts.

New Success Criteria

WCAG 2.2 introduces additional success criteria beyond those in WCAG 2.1, addressing areas such as focus visibility and appearance, accessible authentication, dragging movements, target size, consistent help, and redundant entry. Practitioners should consult the current W3C recommendation for the authoritative list and each criterion's assigned level.

Relationship to Prior Versions

WCAG 2.2 extends rather than replaces WCAG 2.0 and 2.1. Criteria added in later versions should be attributed to the version in which they were introduced rather than conflated with earlier criteria.

Scope as a Technical Standard

WCAG 2.2 is a set of technical guidelines, not a law. It is often referenced as a benchmark in legal, regulatory, and procurement settings, but it does not itself carry legal force absent adoption through a specific law, regulation, agency guidance, or settlement.

Common questions

Answers to the questions practitioners most commonly ask about WCAG.

Does the ADA legally require conformance to WCAG 2.2?

Not directly. The ADA is a US civil rights law and does not itself contain detailed web technical specifications naming a particular WCAG version. WCAG 2.2, like earlier versions, is a technical guideline published by the W3C through the Web Accessibility Initiative. Courts, settlements, and some agency guidance have often referenced WCAG as a benchmark, but a specific version becomes an enforceable requirement only where a particular regulation, settlement, or agency rule adopts it, and that should be attributed to that specific source. Because these requirements evolve through regulation and case law and vary by jurisdiction, consult qualified legal counsel for your situation.

If we meet all WCAG 2.2 success criteria, are we guaranteed to be accessible and legally safe?

No. Meeting WCAG 2.2 success criteria, including at Level AA, does not guarantee an accessible experience for all users, nor does it guarantee immunity from legal claims. Conformance, usability, and legal compliance are distinct. Automated testing detects only a portion of accessibility issues, so manual review and testing with assistive technology are generally needed. Conformance is best understood as evidence of good-faith effort against a recognized standard rather than a promise of legal safety.

What is the difference between WCAG 2.2 and WCAG 2.1, and do we need to re-audit?

WCAG 2.2 builds on 2.1 and adds new success criteria while retaining the earlier ones, so material that conforms to 2.2 generally also addresses 2.1. Because 2.2 introduces criteria not present in 2.1, teams that previously targeted 2.1 will typically want to review their work against the added criteria rather than assume prior conformance carries over automatically. The specific criteria added and their assigned levels should be confirmed against the current W3C recommendation.

Which conformance level of WCAG 2.2 should we target?

Level AA is the level most commonly cited as a target in policies, settlements, and agency guidance, and it is a common practical goal for most organizations. Level A represents a baseline, and Level AAA includes criteria that may not be achievable or appropriate across all content. The appropriate target for a given organization can depend on applicable regulations and internal policy, so confirm any specific obligation against the relevant authority or legal counsel.

How should we test for WCAG 2.2 conformance?

A combination of methods is generally recommended. Automated tools can efficiently flag certain issues but detect only a portion of them, so they should be paired with manual evaluation and testing using assistive technologies such as screen readers and keyboard-only navigation. Reviewing against each applicable success criterion, rather than relying solely on an automated score, gives a more accurate picture of conformance.

We currently conform to WCAG 2.0 or 2.1. How do we approach migrating toward 2.2?

Because WCAG 2.2 retains the earlier success criteria and adds new ones, a practical approach is to treat existing conformance as a starting point and evaluate content against the criteria introduced in 2.2. Prioritizing the newly added criteria and confirming their assigned conformance levels against the current W3C recommendation helps focus remediation effort. Keep in mind that any legal or contractual obligation to a specific version should be verified against the applicable regulation, settlement, or counsel's advice.

Common misconceptions

The ADA legally requires conformance with WCAG 2.2.

The ADA is a US civil rights law and does not itself contain detailed web technical specifications naming a WCAG version. WCAG has commonly been referenced as a benchmark in settlements, regulations, and agency guidance rather than codified as a general ADA rule. Any specific requirement should be attributed to the particular regulation, guidance, or settlement that establishes it, and readers should consult qualified legal counsel and current rulemaking.

Meeting WCAG 2.2 guarantees an accessible experience and legal immunity.

Satisfying WCAG success criteria does not guarantee an accessible experience for all users, nor does it guarantee immunity from legal claims. Conformance, usability, and legal compliance are distinct. Automated testing detects only a portion of issues, so manual testing and testing with assistive technologies are generally required.

WCAG 2.2 replaces WCAG 2.0 and 2.1, so older criteria no longer apply.

WCAG 2.2 is backward-compatible and extends the earlier 2.x versions rather than superseding their requirements. New criteria were added in 2.1 and 2.2, and criteria should be attributed to the version that introduced them rather than treated as interchangeable across versions.

Best practices

Target Level AA as a commonly cited benchmark, while confirming the specific version and level required by any applicable policy, procurement requirement, regulation, or settlement rather than assuming a single universal mandate.

Consult the current W3C recommendation for the authoritative list of WCAG 2.2 success criteria and their assigned conformance levels, and attribute newly added criteria to the version that introduced them.

Combine automated testing with manual review and testing using assistive technologies, since automated tools detect only a portion of accessibility issues.

Evaluate real user experience and usability alongside technical conformance, recognizing that passing success criteria does not by itself ensure an accessible experience for all users.

Distinguish the technical standard from the legal framework in documentation and communications, and consult qualified legal counsel and current agency rulemaking for compliance questions.

Track evolving requirements over time, since accessibility obligations develop through regulation and case law and WCAG itself is updated across versions.