WCAG 2.1 vs 2.2

Why This Comparison Comes Up

Organizations planning accessibility work frequently have to answer a version question. A regulation names WCAG 2.1. A vendor advertises WCAG 2.2. A consultant recommends targeting the newest version. A procurement document has to say something specific.

The two versions are closer than the numbering suggests. WCAG 2.2 keeps the entire structure of WCAG 2.1, adds nine success criteria, and removes one. Understanding what changed, and what did not, makes the version question much easier to answer.

Status of Each Version

WCAG 2.1 became a W3C Recommendation in June 2018. It remains a current, published, citable standard, and it is the version incorporated by the Department of Justice rule for state and local government web content and mobile applications.

WCAG 2.2 became a W3C Recommendation in October 2023 and was updated in December 2024. It is the most recently published version of WCAG 2.

Neither version is retired. A newer W3C Recommendation does not withdraw an earlier one, and it does not automatically change what any law requires.

The Shared Framework

Everything structural in WCAG 2.1 carries forward into WCAG 2.2.

Both versions organize requirements under the same four principles: perceivable, operable, understandable, and robust. Both use the same guideline and success criterion structure. Both use the same conformance levels of A, AA, and AAA, and the same cumulative relationship between them. Both use the same conformance requirements, including the concept of conformance applying to full pages and to complete processes.

This means that work done against WCAG 2.1 is not discarded when an organization moves to WCAG 2.2. The move is an addition rather than a rebuild.

Backward Compatibility

The WCAG 2 versions are designed so that meeting a later version also means meeting the earlier ones. Content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0.

The practical consequence is significant. An organization legally required to meet WCAG 2.1 Level AA can design and procure to WCAG 2.2 Level AA and still satisfy its obligation, because the WCAG 2.1 criteria are contained within it.

One detail is worth carrying forward. Because WCAG 2.2 removes 4.1.1 Parsing, an organization that must formally report against WCAG 2.0 or WCAG 2.1 may still need to test and report that criterion even while working to WCAG 2.2 for everything else.

The Nine New Success Criteria

WCAG 2.2 adds nine success criteria. Three are Level A or AA additions in the focus and input area, three address forms and authentication, and three sit at Level AAA.

2.4.11 Focus Not Obscured (Minimum), Level AA. When a component receives keyboard focus, it must not be entirely hidden by author-created content such as a sticky header or a cookie banner.

2.4.12 Focus Not Obscured (Enhanced), Level AAA. A stricter version of the same idea, requiring that no part of the focused component be hidden.

2.4.13 Focus Appearance, Level AAA. Sets minimum size and contrast expectations for the visible focus indicator.

2.5.7 Dragging Movements, Level AA. Functionality that uses a dragging movement must have an alternative that does not require dragging, unless dragging is essential.

2.5.8 Target Size (Minimum), Level AA. Interactive targets must meet a minimum size, with defined exceptions such as targets placed inline within a sentence.

3.2.6 Consistent Help, Level A. If help mechanisms such as contact details or a help link are repeated across pages, they must appear in a consistent relative order.

3.3.7 Redundant Entry, Level A. Information the user has already entered in a process must not be required again, unless re-entry is essential, with the information either auto-populated or available to select.

3.3.8 Accessible Authentication (Minimum), Level AA. A cognitive function test such as remembering a password or solving a puzzle must not be the only way to authenticate, unless an alternative method, a mechanism to assist, or object recognition is available.

3.3.9 Accessible Authentication (Enhanced), Level AAA. A stricter version that narrows the available exceptions.

For an organization targeting Level AA, the practical additions are 2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, and 3.3.8.

The Removal of 4.1.1 Parsing

WCAG 2.2 removes success criterion 4.1.1 Parsing, which addressed duplicate identifiers and correctly nested markup. The W3C describes the criterion as obsolete.

The reasoning is that browsers and assistive technologies now handle the markup conditions this criterion targeted, so the problems it was written to catch are generally addressed by other criteria that deal with names, roles, and values directly.

Removing a criterion is unusual, and it is the reason WCAG 2.2 cannot be described as purely additive. It also explains why conformance reports sometimes list 4.1.1 with a note rather than omitting it, since organizations reporting against WCAG 2.0 or 2.1 are still measured against it.

What the New Criteria Have in Common

The additions in WCAG 2.2 cluster around a few practical themes.

Keyboard focus visibility. Two of the new criteria address the situation where a keyboard user tabs to a control that is then covered by overlapping content. This is a common side effect of sticky headers, floating chat widgets, and persistent banners.

Pointer and motor access. Dragging alternatives and minimum target sizes address users who have difficulty with precise pointer movement, including many people using touch screens, and people using head pointers, switches, or tremor-affected input.

Cognitive load. Consistent help, redundant entry, and accessible authentication address memory, attention, and processing demands. Accessible authentication in particular changes how many login and verification flows need to be designed, because it limits reliance on remembering or transcribing information.

Together these reflect the areas where research and practice identified gaps in WCAG 2.1 rather than a change in the standard's philosophy.

Why an Organization May Target WCAG 2.2

Several reasons come up consistently.

It is the most current published version, so designing to it reduces the likelihood of rework if a future regulation references a newer version.

It satisfies earlier versions through backward compatibility, so a single design target can cover multiple obligations at once.

Its additions address barriers that are common in current interface patterns, particularly authentication flows, sticky interface elements, and touch targets.

Procurement and contract language written to a newer version tends to age better than language written to a version that is already several years old.

Why the Title II Rule Still Specifies WCAG 2.1

The Department of Justice rule for state and local government web content and mobile applications incorporates WCAG 2.1 Level A and Level AA. That remains the regulatory requirement for covered public entities, with compliance dates of April 26, 2027 and April 26, 2028 depending on the entity's total population as the rule defines it.

Regulations incorporate a fixed version of a standard by reference so that the legal requirement does not shift each time the standard is revised. Changing the incorporated version requires a rulemaking process. The publication of WCAG 2.2 therefore did not alter what the Title II rule requires.

For a covered public entity this means WCAG 2.1 Level AA is the obligation and WCAG 2.2 Level AA is an optional, compatible target that exceeds it. Treating a WCAG 2.2 gap as a Title II violation in itself would misstate the rule.

Why Section 508 Still Points to WCAG 2.0

The Revised Section 508 Standards, maintained by the U.S. Access Board, incorporate WCAG 2.0 at Level A and Level AA for electronic content. That is the standard federal agencies and their suppliers are measured against for covered technology.

The same logic applies. The incorporated version changes only through the process that updates the standards, not through W3C publication. A product assessed against Section 508 has therefore been assessed against WCAG 2.0 criteria, which is worth knowing when that product is being bought by an organization whose own obligation is WCAG 2.1 or higher.

A Practical Way to Decide

Two questions usually resolve the version choice.

What am I required to meet? This is determined by the law, regulation, contract, or policy that applies. A state or local government entity subject to the Title II rule is required to meet WCAG 2.1 Level A and AA. A federal agency or federal supplier works to the Revised Section 508 Standards and therefore WCAG 2.0 Level A and AA. Other organizations should check their contracts, funding conditions, and internal policies.

What should I build and buy to? Many organizations answer WCAG 2.2 Level AA, because it satisfies the requirement above while addressing current interface barriers and reducing future rework.

Writing both answers down, rather than using a general phrase such as WCAG compliant, prevents most of the confusion that arises later in audits, procurement, and accessibility statements.

Related AssistiveTechnology.org Resources

For what WCAG is and how conformance levels work, see WCAG Overview. For how WCAG relates to United States law, see WCAG vs ADA vs Section 508. For the Title II rule in detail, see ADA Title II Digital Accessibility for State and Local Governments, and for the K-12 context, see ADA Title II Digital Accessibility for Public Schools. For a general orientation, see Digital Accessibility, and for further reading across topics, see Resources.

Authoritative Sources

World Wide Web Consortium: Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, and Web Content Accessibility Guidelines (WCAG) 2.1, W3C Recommendation.

World Wide Web Consortium, Web Accessibility Initiative: What's New in WCAG 2.2, for the list of added success criteria and the status of 4.1.1 Parsing.

World Wide Web Consortium, Web Accessibility Initiative: WCAG 2 Overview, for version status and backward compatibility.

28 CFR part 35, subpart H, and U.S. Department of Justice, ADA.gov: Fact Sheet on the rule for web content and mobile applications of state and local government entities.

U.S. Access Board: Revised Section 508 Standards, including the incorporation of WCAG 2.0 Level A and Level AA for electronic content.

Last Standards Review

Last standards review: September 21, 2026. On that date the publication status of WCAG 2.1 and WCAG 2.2, the identity and conformance levels of the nine success criteria added in WCAG 2.2, the removal of 4.1.1 Parsing, backward compatibility between WCAG 2 versions, the WCAG version incorporated by the Department of Justice Title II rule and its compliance dates, and the WCAG version incorporated by the Revised Section 508 Standards were verified against current W3C, Department of Justice, and U.S. Access Board sources.

About This Page

This page provides general educational information comparing two published versions of the Web Content Accessibility Guidelines. It is prepared by The Accessibility Clinic Inc. as educational information only. It is not legal advice, it is not a conformance checklist, and it does not guarantee that any specific website, application, or product meets a particular standard or legal requirement. Organizations should evaluate their own obligations in light of their specific circumstances and consult qualified counsel when needed. Standards and regulations change; the last standards review date above indicates when the statements on this page were most recently verified against primary sources.