WCAG 2.1 Criteria Reference

All non-text content has a text alternative.

Alternatives for time-based media.

Captions for prerecorded audio in synchronized media.

Audio description for video content.

Captions for live audio in synchronized media.

Audio description for prerecorded video.

Structure and relationships conveyed through presentation can be programmatically determined.

Correct reading sequence can be programmatically determined.

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

Content doesn't restrict view to a single display orientation.

Input fields collecting user info have autocomplete attributes.

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

Mechanism to pause/stop/control audio that auto-plays.

Text has contrast ratio of at least 4.5:1.

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

Text used to convey information, not images of text.

Content reflows to 320px width without horizontal scrolling.

UI components and graphical objects have 3:1 contrast ratio.

No loss of content when text spacing is adjusted.

Hover/focus content is dismissable, hoverable, and persistent.

All functionality available via keyboard.

Keyboard focus can be moved away from any component.

Single character key shortcuts can be turned off or remapped.

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

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

No content flashes more than three times per second.

Mechanism to skip repeated content blocks.

Pages have descriptive titles.

Focusable components receive focus in a meaningful sequence.

Purpose of each link can be determined from context.

Multiple ways to locate pages in a set of pages.

Headings and labels describe topic or purpose.

Keyboard focus indicator is visible.

Default human language of each page can be programmatically determined.

Human language of each passage or phrase can be determined.

Component doesn't change context on focus.

Changing a setting doesn't automatically change context.

Navigation in same relative order across pages.

Components with same function identified consistently.

Input errors are identified and described to user.

Labels or instructions provided when content requires user input.

Error suggestions provided when input error is detected.

Submissions are reversible, checked, or confirmed.

Markup is valid and well-formed.

Name, role, and value for all UI components are programmatically determinable.

Status messages can be programmatically determined.