WCAG 2.2 Reference

WCAG 2.2 Checklist: All 50 Success Criteria Explained

A complete reference for every WCAG 2.2 Level A and AA success criterion. New 2.2 criteria are marked with a star. Use this checklist to audit your website or prepare your VPAT.

Audit My Website WCAG 2.2 Compliance Guide

WCAG 2.2 · Level A · Level AA · 9 New Criteria

About This Checklist

WCAG 2.2 was published by the W3C in October 2023. It adds nine new success criteria to WCAG 2.1, with a focus on mobile usability, cognitive accessibility, and focus visibility. This checklist covers all 50 Level A and AA success criteria. New 2.2 criteria are marked with a star (★).

This checklist covers all 50 Level A and AA success criteria. New 2.2 criteria are marked with a star.

Principle 1

Perceivable

Information and UI components must be presentable to users in ways they can perceive.

1.1.1

Non-text Content

All non-text content has a text alternative that serves the equivalent purpose.

1.2.1

Audio-only and Video-only (Prerecorded)

Prerecorded audio-only and video-only content has an alternative.

1.2.2

Captions (Prerecorded)

Captions are provided for all prerecorded audio content in synchronized media.

1.2.3

Audio Description or Media Alternative

An alternative for time-based media or audio description is provided.

1.2.4

Captions (Live)

Captions are provided for all live audio content in synchronized media.

1.2.5

Audio Description (Prerecorded)

Audio description is provided for all prerecorded video content.

1.3.1

Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined.

1.3.2

Meaningful Sequence

When the sequence of content affects its meaning, a correct reading sequence can be programmatically determined.

1.3.3

Sensory Characteristics

Instructions do not rely solely on sensory characteristics such as shape, color, size, or location.

1.3.4

Orientation

Content does not restrict its view and operation to a single display orientation.

1.3.5

Identify Input Purpose

The purpose of each input field collecting user information can be programmatically determined.

1.4.1

Use of Color

Color is not used as the only visual means of conveying information.

1.4.2

Audio Control

Audio that plays automatically for more than 3 seconds can be paused, stopped, or muted.

1.4.3

Contrast (Minimum)

Text has a contrast ratio of at least 4.5:1 (3:1 for large text).

1.4.4

Resize Text

Text can be resized up to 200% without loss of content or functionality.

1.4.5

Images of Text

Images of text are only used for decoration or where a particular presentation is essential.

1.4.10

Reflow

Content can be presented without loss of information at 320 CSS pixels wide without horizontal scrolling.

1.4.11

Non-text Contrast

UI components and graphical objects have a contrast ratio of at least 3:1.

1.4.12

Text Spacing

No loss of content when text spacing is adjusted (line height, letter spacing, word spacing).

1.4.13

Content on Hover or Focus

Content that appears on hover or focus is dismissible, hoverable, and persistent.

Principle 2

Operable

UI components and navigation must be operable by all users.

2.1.1

Keyboard

All functionality is available from a keyboard without requiring specific timings.

2.1.2

No Keyboard Trap

Keyboard focus can be moved away from any component using standard keys.

2.1.4

Character Key Shortcuts

Single-character key shortcuts can be turned off, remapped, or activated only on focus.

2.2.1

Timing Adjustable

Time limits can be turned off, adjusted, or extended.

2.2.2

Pause, Stop, Hide

Moving, blinking, or scrolling content can be paused, stopped, or hidden.

2.3.1

Three Flashes or Below Threshold

Content does not flash more than three times per second.

2.4.1

Bypass Blocks

A mechanism is available to bypass blocks of content repeated on multiple pages.

2.4.2

Page Titled

Web pages have titles that describe topic or purpose.

2.4.3

Focus Order

Focusable components receive focus in an order that preserves meaning and operability.

2.4.4

Link Purpose (In Context)

The purpose of each link can be determined from the link text or its context.

2.4.5

Multiple Ways

More than one way is available to locate a page within a set of pages.

2.4.6

Headings and Labels

Headings and labels describe topic or purpose.

2.4.7

Focus Visible

Any keyboard operable UI has a visible keyboard focus indicator.

2.4.11

Focus Not Obscured (Minimum) ★

New in WCAG 2.2. The focused component is not entirely hidden by author-created content.

2.4.12

Focus Not Obscured (Enhanced) ★

New in WCAG 2.2. The focused component is not hidden at all by author-created content.

2.5.1

Pointer Gestures

All functionality using multipoint or path-based gestures can be operated with a single pointer.

2.5.2

Pointer Cancellation

Functions triggered by a single pointer can be cancelled or reversed.

2.5.3

Label in Name

For UI components with visible text labels, the accessible name contains the visible text.

2.5.4

Motion Actuation

Functionality triggered by device motion can also be operated by UI components.

2.5.7

Dragging Movements ★

New in WCAG 2.2. All functionality using dragging can be achieved with a single pointer without dragging.

2.5.8

Target Size (Minimum) ★

New in WCAG 2.2. Target size for pointer inputs is at least 24x24 CSS pixels.

Principle 3

Understandable

Information and the operation of the UI must be understandable.

3.1.1

Language of Page

The default human language of each page can be programmatically determined.

3.1.2

Language of Parts

The human language of each passage or phrase can be programmatically determined.

3.2.1

On Focus

Receiving focus does not automatically trigger a change of context.

3.2.2

On Input

Changing a setting does not automatically cause a change of context.

3.2.3

Consistent Navigation

Navigation mechanisms repeated on multiple pages occur in the same relative order.

3.2.4

Consistent Identification

Components with the same functionality are identified consistently.

3.2.6

Consistent Help ★

New in WCAG 2.2. Help mechanisms appear in the same location across pages.

3.3.1

Error Identification

Input errors are identified and described to the user in text.

3.3.2

Labels or Instructions

Labels or instructions are provided when content requires user input.

3.3.3

Error Suggestion

If an input error is detected, suggestions for correction are provided.

3.3.4

Error Prevention (Legal, Financial, Data)

Submissions are reversible, checked, or confirmed.

3.3.7

Redundant Entry ★

New in WCAG 2.2. Information already entered is auto-populated or available for selection.

3.3.8

Accessible Authentication (Minimum) ★

New in WCAG 2.2. Authentication does not require a cognitive function test unless an alternative is provided.

Principle 4

Robust

Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

4.1.1

Parsing

In content implemented using markup languages, elements have complete start and end tags and are nested correctly.

4.1.2

Name, Role, Value

For all UI components, the name, role, and value can be programmatically determined.

4.1.3

Status Messages

Status messages can be programmatically determined through role or properties so they can be announced by assistive technologies.

Related Resources

WCAG 2.2 Compliance →

Full compliance guide

WCAG Audit Tool →

Automated WCAG testing

VPAT Generator →

Generate VPAT from audit

Accessibility Checklist →

Practical testing checklist

Check Your Site Against This List Automatically

ConformPilot scans your website against all WCAG 2.2 criteria and generates a detailed report with violations, severity levels, and remediation guidance.

Start Free Trial See the Audit Tool