WCAG 2.2 Compliance: What the New Success Criteria Require

WCAG 2.2, the Web Content Accessibility Guidelines version 2.2, is the current version of the web accessibility standard published by the World Wide Web Consortium (W3C). W3C released it in October 2023, five years after WCAG 2.1. It adds nine success criteria focused on keyboard focus, touch input, and login and form design.

WCAG 2.2 matters even though U.S. laws still name earlier versions. ADA Title II and the HHS Section 504 rule require WCAG 2.1 AA, and Section 508 names WCAG 2.0 AA. But WCAG 2.2 became an ISO standard in October 2025, and it also meets 2.1 AA. This article covers what WCAG 2.2 adds, how it compares to earlier versions, and whether it is worth building to now.

What Is WCAG 2.2?

WCAG 2.2 keeps the same four principles and three conformance levels as earlier versions. What changed is the list of success criteria.

A Brief History: From WCAG 2.1 to ISO Standard

W3C published WCAG 2.2 as a Recommendation on October 5, 2023. On October 21, 2025, it was approved as ISO/IEC 40500:2025, which makes it easier for countries and public bodies to adopt it formally in their own regulations.

Conformance Levels and Success Criteria

WCAG 2.2 contains 86 success criteria: 31 at Level A, 24 at Level AA, and 31 at Level AAA. WCAG 2.2 level AA means meeting every Level A and Level AA criterion, 55 in total. Because the standard builds on 2.1, content that meets 2.2 AA also meets 2.1 AA, apart from the removed criterion 4.1.1.

What Changed: Nine Added, One Removed

WCAG 2.2 adds nine success criteria: two at Level A, four at Level AA, and three at Level AAA. It also removes 4.1.1 Parsing, which W3C retired because browsers and assistive technology now handle markup errors on their own. Every other WCAG 2.0 and 2.1 criterion carries over unchanged.

What WCAG 2.2 Adds for Websites

The new WCAG 2.2 success criteria address three groups of barriers: keyboard focus, touch and pointer input, and forms and login.

Focus and Keyboard Navigation

Focus Not Obscured (Minimum) (2.4.11, Level AA) requires that a component receiving keyboard focus is not entirely hidden by other content. Sticky headers, chat widgets, and cookie banners often cover the element a keyboard user has just tabbed to, leaving that user unable to see where they are. WCAG 2.2 also adds two Level AAA criteria, Focus Not Obscured (Enhanced) and Focus Appearance, for sites that want to go further.

Touch and Pointer Input

Dragging Movements (2.5.7, Level AA) requires a single-pointer alternative to any drag-and-drop action, such as buttons that move an item up or down a list. Target Size (Minimum) (2.5.8, Level AA) requires interactive targets to be at least 24 by 24 CSS pixels, with limited exceptions. Both help users with tremors, limited dexterity, and touch devices, as covered in our article on website accessibility for motor disabilities.

Forms, Login, and Help

• Redundant Entry (3.3.7, Level A): information a user has already entered in a process, such as a shipping address reused for billing, should not have to be typed again.
• Accessible Authentication (Minimum) (3.3.8, Level AA): logging in cannot depend on a cognitive test, such as remembering a password or solving a puzzle, unless an alternative exists, such as support for password managers and paste.
• Consistent Help (3.2.6, Level A): help options such as a contact link or chat widget must appear in the same place across pages.

These changes mainly support users with cognitive disabilities, but they reduce friction for everyone. Our forms accessibility article covers how form design affects screen reader and keyboard users.

Is WCAG 2.2 Required by Law?

The major U.S. frameworks covered in this series still name earlier versions of WCAG, though the direction is toward newer ones.

U.S. Laws That Still Name Earlier Versions

ADA Title II requires WCAG 2.1 AA for state and local governments, and the HHS Section 504 rule requires WCAG 2.1 Levels A and AA. Section 508 incorporates WCAG 2.0 Level A and AA. Title III has no codified standard for private businesses, though 2.1 AA is the benchmark most often cited in settlements. None of these frameworks currently names WCAG 2.2.

Where WCAG 2.2 Is Gaining Ground

ISO recognition allows more countries and public bodies to adopt WCAG 2.2 formally. Some buyers are also starting to ask for 2.2 conformance in contracts and RFPs, so vendors may be held to the newer standard before any law requires it. Organizations that build to 2.2 now avoid a second round of remediation later.

WCAG 2.2 vs. WCAG 2.1 and 2.0

WCAG 2.0 has 61 success criteria, WCAG 2.1 has 78, and WCAG 2.2 has 86. Each version adds to the last. WCAG 2.1 brought criteria for mobile, low vision, and cognitive accessibility, and WCAG 2.2 adds focus, target size, dragging, and authentication criteria. Our WCAG 2.0 and WCAG 2.1 articles cover the details of each version.

Should You Build to WCAG 2.2 AA?

For most organizations, yes. A site that already meets 2.1 AA needs to address only six new Level A and AA criteria to reach WCAG 2.2 compliance, so the added effort is small. Building to 2.2 AA satisfies every requirement named in this series today, and it prepares the site for the next round of legal updates. It also removes the guesswork about which version a contract, settlement, or deadline will point to.

How to Test for WCAG 2.2 Compliance

Automated scans catch only part of the new criteria. A manual website accessibility audit is the reliable way to check the areas that changed most:

• Sticky elements: tab through every page and confirm that headers, banners, and chat widgets never fully cover the focused element.
• Target sizes: measure small buttons, icons, and close controls.
• Drag and drop: confirm that every drag action has a click or tap alternative.
• Login flows: test sign-in with a password manager and with paste enabled.
• Forms: check that previously entered data is reused within multi-step processes.

FAQ

What is WCAG 2.2?

WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, published by W3C in October 2023. It contains 86 success criteria and adds nine to WCAG 2.1, covering keyboard focus, target size, dragging, and accessible authentication.

Is WCAG 2.2 required by law?

Not by name in the major U.S. frameworks covered here. ADA Title II and the HHS Section 504 rule require WCAG 2.1 AA, and Section 508 requires WCAG 2.0 AA. Meeting WCAG 2.2 AA satisfies all of them.

What is the difference between WCAG 2.1 and 2.2?

WCAG 2.2 adds nine success criteria to WCAG 2.1 and removes 4.1.1 Parsing. Six of the new criteria are at Level A or AA, so they apply to the compliance levels most laws and contracts use.

How many success criteria are in WCAG 2.2 AA?

WCAG 2.2 Level AA includes 55 success criteria: 31 at Level A and 24 at Level AA.

Does WCAG 2.2 replace WCAG 2.1?

W3C encourages use of the most current version, and WCAG 2.2 includes every 2.1 criterion except the obsolete 4.1.1. Laws still name earlier versions, though, so 2.1 AA remains the legal benchmark in many cases until those rules change. Meeting 2.2 AA covers both.

Check Your Site Against WCAG 2.2 AA

Whether you are targeting 2.1 AA for a legal deadline or building to 2.2 AA to stay ahead, a manual accessibility audit shows exactly where your site stands. Get a free accessibility audit quote to find out what it will take to close the gaps.