WCAG 2.2 Checklist

All 86 success criteria of WCAG 2.2 with plain-language summaries and links to the official Understanding docs.

Principle:
Level:

Showing 86 of 86 criteria.

1.1.1

Non-text Content

All non-text content (images, icons, charts) needs a text alternative that serves the equivalent purpose.

1.2.1

Audio-only and Video-only (Prerecorded)

Provide transcripts for prerecorded audio, and transcripts or audio description for prerecorded video.

1.2.2

Captions (Prerecorded)

Provide captions for all prerecorded audio content in synchronized media.

1.2.3

Audio Description or Media Alternative (Prerecorded)

Provide audio description or a full text alternative for prerecorded video content.

1.2.4

Captions (Live)

Provide captions for all live audio content in synchronized media.

1.2.5

Audio Description (Prerecorded)

Provide audio description for all prerecorded video content.

1.2.6

Sign Language (Prerecorded)

Provide sign language interpretation for all prerecorded audio content.

1.2.7

Extended Audio Description (Prerecorded)

Provide extended audio description where standard description cannot convey all video information.

1.2.8

Media Alternative (Prerecorded)

Provide a full text alternative for all prerecorded synchronized media.

1.2.9

Audio-only (Live)

Provide text alternatives that convey equivalent information for live audio-only content.

1.3.1

Info and Relationships

Structure (headings, lists, tables) and relationships in content must be programmatically determinable.

1.3.2

Meaningful Sequence

The reading order of content must be programmatically determinable when it affects meaning.

1.3.3

Sensory Characteristics

Instructions must not rely solely on shape, size, position, orientation, or sound to identify controls.

1.3.4

Orientation

Content does not restrict its use to a single display orientation, such as portrait only.

1.3.5

Identify Input Purpose

The purpose of common input fields is programmatically determinable, e.g. via HTML autocomplete.

1.3.6

Identify Purpose

The purpose of user interface components, icons, and regions is programmatically determinable.

1.4.1

Use of Color

Color is never the only visual means of conveying information, indicating an action, or distinguishing an element.

1.4.2

Audio Control

Auto-playing audio longer than 3 seconds can be paused, stopped, or have its volume controlled.

1.4.3

Contrast (Minimum)

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

1.4.4

Resize Text

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

1.4.5

Images of Text

Real text is used rather than images of text, except where essential, such as logos.

1.4.6

Contrast (Enhanced)

Text has a contrast ratio of at least 7:1 against its background (4.5:1 for large text).

1.4.7

Low or No Background Audio

Speech audio has minimal or no background noise, or the background audio can be turned off.

1.4.8

Visual Presentation

Blocks of text offer user control over width, line spacing, justification, and colors.

1.4.9

Images of Text (No Exception)

Images of text are used only for decoration or where no other way of presenting the content exists.

1.4.10

Reflow

Content reflows to a single 320 CSS pixel wide column without two-dimensional scrolling.

1.4.11

Non-text Contrast

UI components, focus indicators, and graphical objects have at least 3:1 contrast against adjacent colors.

1.4.12

Text Spacing

No loss of content or functionality when users adjust line height, paragraph, letter, and word spacing.

1.4.13

Content on Hover or Focus

Hover- or focus-triggered extra content is dismissible, hoverable, and persistent.

2.1.1

Keyboard

All functionality is operable through a keyboard interface.

2.1.2

No Keyboard Trap

Keyboard focus can always be moved away from any component using the keyboard alone.

2.1.3

Keyboard (No Exception)

All functionality is operable via keyboard with no timing-dependent exceptions.

2.1.4

Character Key Shortcuts

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

2.2.1

Timing Adjustable

Time limits can be turned off, adjusted, or extended by the user.

2.2.2

Pause, Stop, Hide

Moving, blinking, or auto-updating content can be paused, stopped, or hidden.

2.2.3

No Timing

Timing is not an essential part of any activity, except real-time events.

2.2.4

Interruptions

Interruptions can be postponed or suppressed by the user, except for emergencies.

2.2.5

Re-authenticating

Re-authenticating does not cause loss of user data or activity.

2.2.6

Timeouts

Users are warned of the duration of inactivity that could cause data loss.

2.3.1

Three Flashes or Below Threshold

No content flashes more than three times per second, or only below the general flash threshold.

2.3.2

Three Flashes

No content flashes more than three times in any one-second period.

2.3.3

Animation from Interactions

Motion animation triggered by interaction can be disabled, and its absence does not break functionality.

2.4.1

Bypass Blocks

A mechanism exists to skip blocks of content repeated across pages, such as a skip link.

2.4.2

Page Titled

Pages have titles that describe their topic or purpose.

2.4.3

Focus Order

Focus order preserves meaning and operability as the user moves through content.

2.4.4

Link Purpose (In Context)

The purpose of each link is determinable from its link text or its surrounding context.

2.4.5

Multiple Ways

More than one way exists to locate a page within a set of pages (navigation, search, sitemap).

2.4.6

Headings and Labels

Headings and labels describe the topic or purpose of the content they name.

2.4.7

Focus Visible

The keyboard focus indicator is visible while an element has focus.

2.4.8

Location

Information about the user’s location within a set of pages is available.

2.4.9

Link Purpose (Link Only)

The purpose of each link is determinable from its link text alone.

2.4.10

Section Headings

Section headings are used to organize the content of a page.

2.4.11

Focus Not Obscured (Minimum)

The item receiving focus is not entirely hidden by author-created content. New in WCAG 2.2.

2.4.12

Focus Not Obscured (Enhanced)

The item receiving focus is not obscured at all by any content. New in WCAG 2.2.

2.4.13

Focus Appearance

The focus indicator has sufficient size, contrast, and change-of-appearance. New in WCAG 2.2.

2.5.1

Pointer Gestures

Multipoint or path-based pointer gestures have single-pointer alternatives.

2.5.2

Pointer Cancellation

Actions trigger on the up-event, or can be aborted or undone after down-event activation.

2.5.3

Label in Name

The visible label text is contained within the accessible name of the control.

2.5.4

Motion Actuation

Functions triggered by device motion have user-interface alternatives and can be disabled.

2.5.5

Target Size

Pointer input targets are at least 44 by 44 CSS pixels.

2.5.6

Concurrent Input Mechanisms

Content does not restrict its use to only one of the available input modalities.

2.5.7

Dragging Movements

Dragging operations have a clicking or tapping alternative. New in WCAG 2.2.

2.5.8

Target Size (Minimum)

Pointer targets are at least 24 by 24 CSS pixels, with limited exceptions. New in WCAG 2.2.

3.1.1

Language of Page

The default human language of the page is programmatically determinable.

3.1.2

Language of Parts

The language of passages that differ from the page language is identified.

3.1.3

Unusual Words

A mechanism is available for definitions of unusual words, idioms, and jargon.

3.1.4

Abbreviations

A mechanism is available for the expanded form or meaning of abbreviations.

3.1.5

Reading Level

Text requires no more than a lower secondary education reading level, or a supplemental version exists.

3.1.6

Pronunciation

A mechanism exists to identify pronunciation where meaning depends on it.

3.2.1

On Focus

Receiving focus does not trigger a change of context.

3.2.2

On Input

Changing a setting does not automatically change context without advance warning.

3.2.3

Consistent Navigation

Navigation mechanisms repeated across pages occur in the same relative order.

3.2.4

Consistent Identification

Components with the same functionality are identified consistently across the site.

3.2.5

Change on Request

Context changes are initiated only by user request, or a disable option exists.

3.2.6

Consistent Help

Help access is placed in the same relative order across pages. New in WCAG 2.2.

3.3.1

Error Identification

Input errors are automatically detected and described to the user in text.

3.3.2

Labels or Instructions

Labels or instructions are provided whenever content requires user input.

3.3.3

Error Suggestion

Error correction suggestions are provided when known and safe to do so.

3.3.4

Error Prevention (Legal, Financial, Data)

Legal, financial, or data-submission transactions are reversible, checked, or confirmed.

3.3.5

Help

Context-sensitive help is available.

3.3.6

Error Prevention (All)

All submissions are reversible, checked, or confirmed.

3.3.7

Redundant Entry

Previously entered information is auto-populated or selectable, not re-typed. New in WCAG 2.2.

3.3.8

Accessible Authentication (Minimum)

Logging in does not require a cognitive function test, or an alternative exists. New in WCAG 2.2.

3.3.9

Accessible Authentication (Enhanced)

No cognitive function test of any kind is required for authentication. New in WCAG 2.2.

4.1.2

Name, Role, Value

Custom UI components expose their name, role, states, and values to assistive technology.

4.1.3

Status Messages

Status messages can be programmatically determined without receiving focus.

Data from WCAG 2.2 — criteria new in 2.2 are noted in their summaries, and 4.1.1 Parsing was removed in 2.2. Conform to the official How to Meet WCAG (Quick Reference) , not this checklist.