WCAG 2.2 Success Criteria Explorer

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

Provide alternatives for prerecorded audio-only and video-only media.

Captions are provided for prerecorded audio content in synchronized media.

Alternative for prerecorded video content in synchronized media.

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

Audio description is provided for all prerecorded video content.

Sign language interpretation is provided for prerecorded audio content.

Extended audio description for prerecorded video.

Alternative for time-based media for prerecorded synchronized media.

Alternative for time-based media that presents equivalent information for live audio-only.

Structure and relationships conveyed through presentation can be programmatically determined.

The reading sequence can be programmatically determined.

Instructions don't rely solely on shape, color, size, location, or sound.

Content is not restricted to a single display orientation.

The purpose of common input fields can be programmatically determined via autocomplete.

Purpose of UI components, icons, and regions can be programmatically determined.

Color is not the only means of conveying information.

Audio that plays for more than 3 seconds can be paused.

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

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

Use text instead of images of text where possible.

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

Background audio is quiet or absent in prerecorded audio-only content.

Blocks of text meet visual presentation requirements.

Images of text are only used for pure decoration or where essential.

Content reflows to a single column at 320 CSS pixels without loss.

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

No loss of content when users override text spacing.

Additional content triggered on hover/focus is dismissible, hoverable, and persistent.

All functionality is available from a keyboard.

Keyboard focus can move away from any component.

All functionality is available from a keyboard with no timing requirements.

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

Users can turn off, adjust, or extend time limits.

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

Timing is not an essential part of the activity.

Interruptions can be postponed or suppressed.

Users can continue activity without data loss after re-authentication.

Users are warned about session timeouts causing data loss.

No content flashes more than 3 times per second.

No content flashes more than 3 times per second (stricter).

Motion animation triggered by interaction can be disabled.

A mechanism (skip link, landmarks) bypasses repeated content.

Pages have titles that describe topic or purpose.

Focus order preserves meaning and operability.

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

More than one way is available to locate a page.

Headings and labels describe topic or purpose.

Keyboard focus indicator is visible.

User's location within a set of pages is available.

The purpose of each link can be identified from the link text alone.

Section headings are used to organize content.

Focused element is not entirely hidden by author-created content.

No part of the focused element is hidden.

Focus indicator meets minimum size and contrast requirements.

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

Users can abort or undo pointer activations.

Accessible name contains the visible label text.

Motion-triggered functions have UI alternatives and can be disabled.

Touch targets are at least 44 by 44 CSS pixels.

Users can switch between input modalities.

Dragging functions have single-pointer alternatives.

Touch targets are at least 24 by 24 CSS pixels.

Default language of the page can be programmatically determined.

Language of each passage can be programmatically determined.

Mechanism available to identify unusual words.

Mechanism to identify the expanded form of abbreviations.

Text does not require more than lower secondary education reading ability.

Mechanism to identify specific pronunciation.

Receiving focus does not trigger a change of context.

Changing a setting does not automatically change context.

Navigation repeated on multiple pages is in the same order.

Components with the same function are identified consistently.

Changes of context are initiated only by user request.

Help mechanisms are provided in the same relative order across pages.

Input errors are identified and described to the user.

Labels or instructions are provided when content requires user input.

If input errors are detected, suggestions for correction are provided.

For sensitive submissions, users can review, correct, or reverse.

Context-sensitive help is available.

Reversal, verification, or confirmation is available for all submissions.

Information previously entered is auto-populated or available.

No cognitive function test is required for authentication.

No cognitive function test at all for authentication.

Historically required valid nesting; now removed from WCAG 2.2.

Name, role, and state of UI components are programmatically determinable.

Status messages can be programmatically determined via role/aria-live.