Accessibility Home / Policy

WCAG 2.2 Highlights

Understanding the new success criteria in WCAG 2.2 and preparing for adoption.

Status: WCAG 2.2 became a W3C Recommendation on October 5, 2023.

Note: ADA Title II currently references WCAG 2.1 AA, but institutions should prepare for eventual adoption of 2.2.

What's New in WCAG 2.2

WCAG 2.2 extends WCAG 2.1 with 9 new success criteria focused on:

  • Cognitive accessibility: Helping users with cognitive and learning disabilities
  • Mobile accessibility: Better support for touch interfaces
  • Low vision: Improved focus and target visibility
  • Authentication: Reducing barriers in login processes

Version Comparison

Version Year Total Criteria New in Version
WCAG 2.0 2008 61 61
WCAG 2.1 2018 78 17
WCAG 2.2 2023 86 9 new, 1 removed

New Success Criteria

2.4.11 Focus Not Obscured (Minimum) — Level AA

Requirement: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

What This Means

When users tab through a page, they must be able to see what's focused. Sticky headers, cookie banners, and chat widgets shouldn't completely cover focused elements.

How to Comply

  • Ensure sticky elements don't cover focused content
  • Use scroll-padding or scroll-margin in CSS
  • Test by tabbing through pages with sticky elements

2.4.12 Focus Not Obscured (Enhanced) — Level AAA

Requirement: No part of the focused component is hidden by author-created content.

What This Means

The stricter version requires the entire focused element to be visible, not just part of it.

2.4.13 Focus Appearance — Level AAA

Requirement: Focus indicators must have sufficient size and contrast.

What This Means

Focus indicators should have an area at least the size of a 2px thick perimeter and a 3:1 contrast ratio against adjacent colors.

How to Comply

  • Use visible, high-contrast focus indicators
  • Avoid thin, subtle focus outlines
  • Test with keyboard navigation

2.5.7 Dragging Movements — Level AA

Requirement: Functionality that uses dragging can be operated with single pointer without dragging.

What This Means

If users can drag items (like reordering a list or moving a slider), they must also be able to do so with clicks/taps alone.

How to Comply

  • Provide click/tap alternatives for drag operations
  • Add up/down buttons for reorderable lists
  • Allow clicking to set slider values

Example

A sortable list should have "Move Up" and "Move Down" buttons in addition to drag-and-drop.

2.5.8 Target Size (Minimum) — Level AA

Requirement: Targets for pointer inputs are at least 24×24 CSS pixels, with some exceptions.

What This Means

Buttons, links, and interactive controls should be large enough to tap or click without difficulty.

Exceptions

  • Spacing: Smaller targets are okay if there's enough space between them
  • Equivalent: Same function available via larger target
  • Inline: Links within text paragraphs
  • User agent: Size determined by browser, not author
  • Essential: Specific size is legally required or essential

How to Comply

  • Make buttons at least 44×44 pixels (recommended)
  • Add padding to small interactive elements
  • Ensure adequate spacing between targets

3.2.6 Consistent Help — Level A

Requirement: Help mechanisms appear in the same relative order across pages.

What This Means

If a website has help features (contact info, chat, FAQ links), they should appear in consistent locations throughout the site.

Help Mechanisms Include

  • Human contact details
  • Human contact mechanisms (chat, forms)
  • Self-help options (FAQ, help pages)
  • Automated contact mechanisms (chatbots)

How to Comply

  • Place help links in consistent locations (e.g., always in footer)
  • Keep help navigation order consistent
  • Use consistent visual presentation

3.3.7 Redundant Entry — Level A

Requirement: Information previously entered doesn't have to be re-entered in the same process.

What This Means

In multi-step forms, if a user enters information like their name or address, they shouldn't have to enter it again on a later step.

Exceptions

  • Re-entering is essential (security)
  • Information is no longer valid

How to Comply

  • Auto-populate fields with previously entered data
  • Allow users to select from previous entries
  • Store form progress across steps

3.3.8 Accessible Authentication (Minimum) — Level AA

Requirement: Cognitive function tests aren't required for authentication unless alternatives exist.

What This Means

Login processes shouldn't require users to solve puzzles, remember passwords, or transcribe CAPTCHAs unless there's an alternative method.

Cognitive Function Tests Include

  • Remembering passwords (without password manager support)
  • Solving puzzles
  • Performing calculations
  • Recognizing images (CAPTCHAs)

Acceptable Alternatives

  • Allow password managers to work
  • Provide copy/paste for verification codes
  • Support email/SMS links
  • Enable passkeys or biometric authentication
  • Offer object recognition CAPTCHA alternative

3.3.9 Accessible Authentication (Enhanced) — Level AAA

Requirement: No cognitive function tests for authentication, even object recognition.

What This Means

The stricter version eliminates even object recognition (like "click all the traffic lights") as a required step.

Removed Criterion

4.1.1 Parsing — Removed

Previous requirement: Markup must be well-formed with complete start/end tags, nested according to specification, no duplicate attributes, and unique IDs.

Why Removed

Modern browsers and assistive technologies handle parsing errors gracefully. The issues this criterion addressed are now covered by:

  • 1.3.1 Info and Relationships
  • 4.1.2 Name, Role, Value

Note: Valid HTML is still a best practice, but minor parsing errors won't fail WCAG 2.2 audits.

Impact Assessment

Most Impactful Changes

Criterion Level Effort Impact
Target Size (Minimum) AA Medium High (mobile users)
Focus Not Obscured AA Low High (keyboard users)
Accessible Authentication AA Medium High (cognitive)
Dragging Movements AA Medium Medium
Redundant Entry A Low-Medium Medium (forms)
Consistent Help A Low Low-Medium

Actions to Take Now

  1. Audit sticky elements: Check if they obscure focused content
  2. Review target sizes: Ensure interactive elements are large enough
  3. Test authentication: Ensure login works with password managers
  4. Check drag functionality: Add click/tap alternatives
  5. Audit multi-step forms: Avoid redundant data entry

Adoption Timeline

Current Status

  • ADA Title II: References WCAG 2.1 AA (as of 2024 rule)
  • Section 508: References WCAG 2.0 AA (refresh expected)
  • Our standard: WCAG 2.1 AA with 2.2 recommended

Recommended Approach

  1. Meet WCAG 2.1 AA (required for Title II compliance)
  2. Implement WCAG 2.2 AA for new projects
  3. Prioritize 2.2 criteria that provide highest user benefit
  4. Plan full 2.2 adoption when regulations update

Resources