Web Content Accessibility Guidelines (WCAG) 2.2

Plain English Summary

WCAG 2.2 is the most recent completed version of the internationally recognized web accessibility standard, published by the W3C on October 5, 2023. It builds upon WCAG 2.1 by adding nine new success criteria that primarily focus on making the web more usable for people with cognitive and learning disabilities, people with low vision, and people with motor disabilities.

One of the most notable changes in WCAG 2.2 is the addition of criteria addressing authentication (logging in), consistent help mechanisms, and minimum target sizes for interactive elements. These additions reflect a growing recognition that accessibility is not just about screen reader compatibility -- it is also about making interfaces cognitively manageable and physically usable for everyone.

WCAG 2.2 also made history by removing a success criterion for the first time: 4.1.1 Parsing was removed because modern browsers and assistive technologies are now robust enough that the specific markup issues it addressed are no longer barriers.

While no U.S. law currently mandates WCAG 2.2 specifically (the 2024 Title II rule references WCAG 2.1), WCAG 2.2 represents the current state of the art and is likely to be adopted in future rulemaking and referenced in litigation.

Who This Applies To

Currently Legally Required:

• No U.S. law specifically mandates WCAG 2.2 as of early 2026
• The European Accessibility Act timeline references EN 301 549, which may be updated to incorporate WCAG 2.2

Practically Recommended For:

• Organizations building new websites or undertaking major redesigns
• Organizations seeking to exceed minimum legal requirements
• Organizations that want to reduce cognitive barriers for users
• E-commerce businesses (authentication and target size criteria are highly relevant)
• Government entities planning ahead for potential future standards updates
• Any organization that wants to be at the forefront of accessibility best practices

Who Should Be Aware:

• All web developers and designers
• UX researchers and designers
• Quality assurance and testing teams
• Accessibility professionals and consultants
• Legal and compliance teams monitoring regulatory trends

Key Requirements

New Success Criteria in WCAG 2.2

New Level A Criteria (2):

• 3.2.6 Consistent Help: If a web page contains help mechanisms (such as contact information, a chatbot, or a FAQ link), those mechanisms appear in the same relative order on every page. This helps people with cognitive disabilities who rely on consistent placement to find help.
• 3.3.7 Redundant Entry: Information previously entered by or provided to the user that is required again in the same process is either auto-populated or available for selection. Users should not have to re-enter data they already provided.

New Level AA Criteria (4):

• 2.4.11 Focus Not Obscured (Minimum): When a UI component receives keyboard focus, it is not entirely hidden by author-created content. The focused element must be at least partially visible.
• 2.5.7 Dragging Movements: Any functionality that uses dragging must also be achievable with a single pointer without dragging. This helps users who cannot perform drag operations.
• 2.5.8 Target Size (Minimum): Interactive targets are at least 24x24 CSS pixels, or there is sufficient spacing between undersized targets. This is a more practical version of the AAA target size criterion from WCAG 2.1.
• 3.3.8 Accessible Authentication (Minimum): Cognitive function tests (such as remembering a password or solving a puzzle) are not required for any step in authentication unless an alternative method is available, or a mechanism assists the user (such as password managers and passkeys).

New Level AAA Criteria (3):

• 2.4.12 Focus Not Obscured (Enhanced): When a component receives focus, no part of the component is hidden by author-created content.
• 2.4.13 Focus Appearance: When a component has keyboard focus, the focus indicator meets minimum area, contrast, and visibility requirements.
• 3.3.9 Accessible Authentication (Enhanced): No cognitive function test is required for authentication, with narrower exceptions than the AA criterion.

Removed Criterion

• 4.1.1 Parsing (removed): This criterion required valid HTML markup. It was removed because modern browsers and assistive technologies handle parsing errors gracefully, and the specific issues it addressed are now covered by other criteria.

Enforcement and Penalties

Current Legal Status in the U.S.

As of early 2026, no U.S. federal law or regulation specifically mandates WCAG 2.2:

• Section 508 references WCAG 2.0 AA
• Title II (2024 rule) references WCAG 2.1 AA
• Title III has no specific WCAG version mandate

Expected Trajectory

The pattern is clear -- each new regulatory action references a more recent version of WCAG:

• Section 508 refresh (2017) adopted WCAG 2.0
• Title II rule (2024) adopted WCAG 2.1
• Future rulemaking is likely to adopt WCAG 2.2

Litigation Relevance

Plaintiffs' attorneys and accessibility experts are beginning to test against WCAG 2.2 criteria. While courts currently reference WCAG 2.1 AA as the standard, WCAG 2.2 criteria may be cited as evidence of best practices or as additional barriers in accessibility lawsuits.

International Adoption

The EU's EN 301 549 is expected to be updated to reference WCAG 2.2. When this happens, organizations doing business in the EU will need to comply with WCAG 2.2 requirements.

Practical Implications

For Organizations Already at WCAG 2.1 AA

The upgrade from WCAG 2.1 AA to WCAG 2.2 AA requires meeting six additional success criteria (2 at Level A and 4 at Level AA). Key focus areas:

• Authentication flows: Audit your login process. Can users log in without memorizing a password or solving a CAPTCHA? Support password managers, passkeys, and biometric authentication (3.3.8).
• Drag-and-drop interactions: Any drag-and-drop functionality must have a non-dragging alternative, such as arrow buttons or a menu option (2.5.7).
• Target sizes: Ensure interactive elements are at least 24x24 CSS pixels, or provide adequate spacing. This is especially important on mobile (2.5.8).
• Focus visibility: Ensure focused elements are not hidden behind sticky headers, modals, or other overlapping content (2.4.11).
• Consistent help placement: If you have help mechanisms (chat widget, contact info, FAQ link), ensure they appear in the same location on every page (3.2.6).
• Form data persistence: Multi-step forms should remember previously entered data and not require users to re-enter information (3.3.7).

For New Projects

• Build to WCAG 2.2 AA. Since WCAG 2.2 is backward compatible with 2.1 and 2.0, building to 2.2 automatically satisfies all earlier versions.
• Prioritize authentication accessibility. Passwordless login methods (passkeys, magic links, biometric) are not just more accessible -- they are also better for security and user experience.
• Design touch targets generously. The 24x24 minimum is a baseline. The AAA target of 44x44 remains the best practice, especially for primary actions.

For Accessibility Testers

• Update your testing checklist to include the new WCAG 2.2 criteria.
• Remove 4.1.1 Parsing from your audit checklist. While valid HTML remains a best practice, it is no longer a WCAG conformance requirement.
• Test authentication flows with password managers and without cognitive function tests.
• Test drag-and-drop alternatives and verify they provide equivalent functionality.

Key Dates and Deadlines

| Date | Event | |------|-------| | October 5, 2023 | WCAG 2.2 published as a W3C Recommendation | | April 24, 2024 | DOJ Title II rule adopts WCAG 2.1 (not 2.2) as the standard | | TBD | Expected update of EN 301 549 to reference WCAG 2.2 | | TBD | Potential future Section 508 refresh to incorporate WCAG 2.1 or 2.2 |

Organizations should plan to adopt WCAG 2.2 AA as their target standard even before it is legally mandated. The additional criteria address real usability barriers, and early adoption positions organizations ahead of inevitable regulatory updates.

---

This content is provided for educational and informational purposes only and does not constitute legal advice. For guidance on your specific situation, consult a qualified attorney. Laws and regulations are subject to change, and this information may not reflect the most current legal developments.