WCAG 2.2 vs WCAG 2.1: What Changed and Why It Matters

What Is the Relationship Between WCAG 2.1 and 2.2?

WCAG 2.2 is a superset of WCAG 2.1. Every WCAG 2.1 criterion (except one that was removed) is included in WCAG 2.2, with 9 new criteria added. This means a website that meets WCAG 2.2 automatically meets WCAG 2.1 as well.

The versions build on each other:

• WCAG 2.0 (2008): The original standard with 61 success criteria.
• WCAG 2.1 (2018): Added 17 criteria, focused on mobile, low vision, and cognitive accessibility.
• WCAG 2.2 (2023): Added 9 more criteria, focused on cognitive accessibility, mobile interactions, and authentication.

New Success Criteria in WCAG 2.2

2.4.11 Focus Not Obscured (Minimum) — Level AA

When an element receives keyboard focus, it must not be entirely hidden by other content. Sticky headers, cookie banners, chat widgets, and fixed navigation bars commonly obscure focused elements. The focused element must be at least partially visible.

2.4.12 Focus Not Obscured (Enhanced) — Level AAA

The enhanced version requires the focused element to be fully visible, not just partially. This is a Level AAA criterion, so it is not required for baseline compliance but represents best practice.

2.4.13 Focus Appearance — Level AAA

Focus indicators must meet specific size and contrast requirements. The focus indicator area must be at least as large as a 2px thick perimeter of the element, and the contrast between focused and unfocused states must be at least 3:1. This is Level AAA.

2.5.7 Dragging Movements — Level AA

Any functionality that uses dragging (drag and drop, slider controls, sortable lists) must have a single-pointer alternative that does not require dragging. Users with motor impairments may not be able to perform drag operations. For example, a sortable list must also support reordering via buttons, and a slider must accept direct value input.

2.5.8 Target Size (Minimum) — Level AA

Interactive targets must be at least 24x24 CSS pixels, or have sufficient spacing between targets. This is a practical minimum that prevents users from accidentally activating the wrong control. The spacing exception means that smaller targets are acceptable if there is at least 24px of space between them and adjacent targets.

3.2.6 Consistent Help — Level A

If a website provides help mechanisms (contact information, chat, FAQ links), they must be in a consistent location across pages. This helps users with cognitive disabilities reliably find help when they need it.

3.3.7 Redundant Entry — Level A

Information previously entered by the user in a process must be auto-populated or available for selection in subsequent steps. Users should not have to re-enter data they already provided. Common example: if a billing address was entered, offering a checkbox to reuse it as the shipping address.

3.3.8 Accessible Authentication (Minimum) — Level AA

Authentication processes must not require cognitive function tests (such as remembering a password or solving a puzzle) unless an alternative method is available. Acceptable alternatives include password managers (inputs must support paste and autofill), passkeys, biometric authentication, and email/SMS verification codes.

3.3.9 Accessible Authentication (Enhanced) — Level AAA

The enhanced version is stricter: no cognitive test may be required even with alternatives, except for object recognition and personal content recognition. This is Level AAA.

What Was Removed: 4.1.1 Parsing

WCAG 2.2 removed Success Criterion 4.1.1 Parsing, which required valid HTML markup. Modern browsers and assistive technologies have become robust enough to handle parsing errors, making this criterion obsolete. Note that valid HTML is still good practice for accessibility; it is just no longer a formal WCAG requirement.

Which Version Should You Target?

For legal compliance in the United States, the current requirement is WCAG 2.1 Level AA (as specified in the ADA Title II rule). Meeting WCAG 2.1 AA satisfies both ADA Title II and Section 508 requirements.

However, targeting WCAG 2.2 provides several advantages:

• Future-proofing: Regulations will likely reference WCAG 2.2 in future updates. Building to 2.2 now avoids rework later.
• Better user experience: The new 2.2 criteria address real usability problems, particularly for mobile users and people with cognitive disabilities.
• European compliance: The European Accessibility Act and EN 301 549 are expected to reference WCAG 2.2 in future revisions.
• Stronger legal defense: Exceeding the minimum standard demonstrates good faith compliance and reduces lawsuit risk.

Getting Started

Start by meeting WCAG 2.1 AA — the current legal baseline. Run a free WCAG 2.1 AA scan to identify your current violations. Once you have addressed 2.1 issues, review the new 2.2 criteria and assess which ones require additional work on your site.

For ongoing compliance with both standards, set up continuous monitoring to catch regressions as your site evolves.