WCAG 2.2 AA Highlights

Understanding the Web Content Accessibility Guidelines and what's new in version 2.2.

Title II standard · Effective April 24, 2026

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards developed by the World Wide Web Consortium (W3C). They define how to make web content accessible to people with disabilities, including blindness, low vision, deafness, hearing loss, limited movement, speech disabilities, photosensitivity, and cognitive limitations.

Conformance levels

• Level A: Minimum accessibility requirements. Essential for basic access.
• Level AA: Addresses major barriers. Required by Title II and UA policy.
• Level AAA: Highest level. Not required but beneficial for specialized audiences.

Legal context

The U.S. Department of Justice's April 2024 Title II rule requires state and local governments (including public universities) to conform to WCAG 2.1 Level AA by April 24, 2026 for entities with 50,000+ population. UA must meet this deadline for all web content and mobile applications.

The POUR principles

WCAG is organized around four foundational principles. Content must be:

What's new in WCAG 2.2

WCAG 2.2 was published in October 2023 and adds 9 new success criteria. While Title II currently references WCAG 2.1, UA is aligning to 2.2 for best practice. Here are the new AA-level requirements:

2.4.11 Focus Not Obscured (Minimum) — Level AA

Requirement: When a component receives keyboard focus, it is not entirely hidden by other content (like sticky headers or modals).

Why it matters: Users navigating by keyboard need to see what's focused. Sticky navigation bars and cookie banners often cover focused elements.

How to comply:

• Ensure sticky headers don't completely cover focused elements
• Use CSS scroll-margin-top to offset anchored content
• Test by tabbing through all interactive elements

2.4.12 Focus Not Obscured (Enhanced) — Level AAA

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

2.4.13 Focus Appearance — Level AAA

Requirement: Focus indicators must have sufficient size and contrast.

2.5.7 Dragging Movements — Level AA

Requirement: Any functionality that uses dragging must have a single-pointer alternative.

Why it matters: Users with motor disabilities, tremors, or those using switch devices cannot perform drag operations.

How to comply:

• Provide click-based alternatives for drag-and-drop
• Allow selecting items and choosing a destination
• Offer keyboard shortcuts for reordering

2.5.8 Target Size (Minimum) — Level AA

Requirement: Touch targets must be at least 24×24 CSS pixels, or have sufficient spacing.

Why it matters: Small touch targets are difficult for users with motor impairments, tremors, or limited dexterity.

How to comply:

• Make buttons and links at least 24×24 pixels
• If smaller, ensure 24px spacing between targets
• Exception: Inline links within text blocks

3.2.6 Consistent Help — Level A

Requirement: If a page provides help mechanisms (contact info, chat, FAQ), they appear in the same relative order across pages.

Why it matters: Users with cognitive disabilities rely on consistent patterns to find help.

How to comply:

• Place help links in consistent footer/header locations
• Use consistent labeling ("Help," "Support," "Contact")
• Maintain the same order across all pages

3.3.7 Redundant Entry — Level A

Requirement: Don't require users to re-enter information they've already provided in the same process.

Why it matters: Redundant entry creates barriers for users with cognitive disabilities and motor impairments.

How to comply:

• Auto-populate previously entered information
• Allow users to select from previous entries
• Exception: Security verification or expired sessions

3.3.8 Accessible Authentication (Minimum) — Level AA

Requirement: Authentication processes must not rely on cognitive function tests (like remembering passwords or solving puzzles) unless alternatives are provided.

Why it matters: CAPTCHAs, password recall, and puzzle-based verification exclude users with cognitive disabilities.

How to comply:

• Support password managers (don't block paste)
• Offer authentication alternatives (WebAuthn, SSO)
• Provide copy/paste-friendly verification codes
• Allow object recognition alternatives to CAPTCHAs

3.3.9 Accessible Authentication (Enhanced) — Level AAA

Requirement: No cognitive function test for authentication, with no exceptions for object recognition.

Removed from WCAG 2.2

One success criterion was removed:

• 4.1.1 Parsing — Previously required well-formed HTML. Removed because modern browsers and assistive technologies handle parsing errors gracefully. Good coding practices still recommended.

High-priority checklist for UA

Based on WebAIM Million data and common issues at universities, focus on these first:

Most common failures

Data source: WebAIM Million 2024 annual report

Resources

• WCAG 2.2 Quick Reference — Filterable list of all criteria
• Understanding WCAG 2.2 — Detailed explanations and examples
• Techniques for WCAG 2.2 — How-to guides
• WCAG 2.2 Specification — Official W3C standard
• UA Title II Brief — Legal requirements for our institution