WCAG 2.1 vs 2.2 Difference
The WCAG 2.1 vs 2.2 difference is that WCAG 2.2 builds on 2.1 by adding success criteria focused on mobile interaction, cognitive accessibility, and authentication. WCAG 2.2 is backwards compatible, meaning content that conforms to 2.2 also conforms to 2.1. Most organizations referencing the Web Content Accessibility Guidelines today work toward either 2.1 AA or 2.2 AA, depending on the legal or contractual standard they follow.
| Key Point | What It Means |
|---|---|
| Relationship | WCAG 2.2 is backwards compatible with 2.1. Conforming to 2.2 means conforming to 2.1. |
| New criteria | WCAG 2.2 adds success criteria focused on focus appearance, dragging movements, target size, accessible authentication, and consistent help. |
| Removed criterion | 4.1.1 Parsing was removed in WCAG 2.2 because modern assistive technology no longer relies on it. |
| Legal references | ADA Title II references WCAG 2.1 AA. Other agencies and contracts may reference 2.2 AA. |
| Conformance level | Level AA remains the standard target for both versions. |
How WCAG Versions Build on Each Other
The Web Content Accessibility Guidelines follow an additive model. WCAG 2.0 was the original baseline, 2.1 added criteria primarily focused on mobile and cognitive accessibility, and 2.2 continued that pattern with additional criteria addressing newer interaction issues.
Because each version is backwards compatible, an organization meeting 2.2 AA automatically meets 2.1 AA and 2.0 AA. This matters when contracts reference different versions across customers or jurisdictions.
What WCAG 2.2 Added
WCAG 2.2 introduced success criteria covering interaction patterns that became more common after 2.1 was published. The additions focus on people with motor disabilities, cognitive disabilities, and low vision interacting with modern interfaces.
Topics covered by the new criteria include the visibility of keyboard focus, alternatives to dragging motions, minimum size of interactive targets, accessible authentication methods that do not rely on memory or puzzles, redundant entry of information, and consistent placement of help mechanisms across pages.
The criterion 4.1.1 Parsing was removed in 2.2. It addressed a category of HTML errors that modern browsers and assistive technologies manage without issue, so it no longer reflected real accessibility problems.
Which Version to Use
The version an organization works toward depends on legal references, contractual obligations, and risk posture. Under ADA Title II, the U.S. Department of Justice rule references WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. Title III of the ADA does not specify a technical standard, but courts and settlements have widely referenced WCAG 2.1 AA.
Procurement contracts, particularly those tied to federal purchases or international sales, may reference 2.2 AA or specific WCAG editions of accessibility conformance reporting. Organizations that adopt 2.2 AA cover both standards in one effort.
What Changes for Evaluation and Remediation
An evaluation against 2.2 AA includes everything in a 2.1 AA evaluation plus the new criteria. The additional criteria are evaluated through the same approach: screen reader testing, keyboard testing, visual inspection, code inspection, and an automated scan as a review component.
Scans only flag approximately 25% of accessibility issues, which is true for both versions. Most of the criteria added in 2.2, particularly those involving cognitive load and interaction design, require human evaluation to assess accurately. For organizations preparing to meet ADA website requirements, deciding between 2.1 AA and 2.2 AA early in the process keeps the audit, remediation, and documentation aligned.
How to Document Conformance
Conformance claims specify the version (2.1 or 2.2) and the level (A, AA, or AAA). An accessibility conformance report or accessibility statement should state the version and level being claimed, the date of evaluation, and any portions of the product covered.
Updating from a 2.1 AA claim to a 2.2 AA claim requires evaluating the additional criteria and remediating any issues identified. Because of backwards compatibility, the existing 2.1 AA work carries forward.
For organizations choosing between versions, the practical question is which standard their legal, procurement, and risk requirements reference, and whether covering both in a single audit makes sense for their roadmap.