WCAG 2.2 Compliance Checklist

All non-text content (images, icons, charts, CAPTCHAs) has a text alternative that serves the same purpose. Decorative images have empty alt attributes (alt="").

Audio-only content has a transcript. Video-only content has a text or audio description.

All prerecorded video with audio has synchronized captions. Auto-generated captions alone do not meet this criterion.

Video content has an audio description or a text transcript that describes all visual information.

Structure conveyed through visual formatting (headings, lists, tables) is also conveyed programmatically — e.g., using semantic HTML.

Reading order of content is logical and meaningful when CSS is removed or content is linearized.

Instructions do not rely solely on sensory characteristics like shape, color, size, or location ("click the green button").

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

Audio that plays automatically for more than 3 seconds can be paused, stopped, or the volume controlled independently.

All functionality is operable through a keyboard interface. No specific timing for individual keystrokes required.

If focus can be moved to a component using the keyboard, focus can also be moved away without requiring more than standard keys.

Single character key shortcuts can be turned off, remapped, or activated only when the component has focus.

Time limits can be turned off, adjusted, or extended. Exception: real-time events where time limits are essential.

Moving, blinking, or scrolling content that starts automatically and lasts more than 5 seconds can be paused, stopped, or hidden.

No content flashes more than three times per second, or the flash is below the general flash and red flash thresholds.

A mechanism exists to skip repetitive blocks of content (e.g., a "skip to main content" link).

Each web page has a title that describes its topic or purpose.

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

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

All functionality using multipoint or path-based gestures has a single-pointer alternative.

For single-pointer actions, the down-event is not used to execute the function, or there is a way to abort or undo.

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

Functionality triggered by device motion can also be operated by UI components, and motion response can be disabled.

The default human language of each web page can be programmatically determined (e.g., ).

Receiving focus on a component does not automatically trigger a change of context.

Changing the setting of a UI component does not automatically cause a change of context unless the user has been advised in advance.

If an input error is automatically detected, the item in error is identified and the error described to the user in text.

Labels or instructions are provided when content requires user input.

Information previously entered by the user is auto-populated or available for selection in the same session.

In WCAG 2.2 the W3C updated this criterion's Understanding document to note it is "always satisfied" for HTML content in modern browsers — modern browsers handle parsing errors in a consistent, interoperable way. This criterion is effectively obsolete for HTML. It remains in the spec for non-HTML content types and for backwards compatibility with WCAG 2.1.

For all UI components: name and role can be programmatically determined; state, properties, and values can be set and notified to user agents.

Live video with audio content provides real-time captions.

Audio description is provided for all prerecorded video content.

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

The purpose of input fields collecting user information (name, email, address) can be programmatically determined to allow autofill.

Text has a contrast ratio of at least 4.5:1. Large text (18pt+ or 14pt+ bold) requires 3:1.

Text can be resized up to 200% without loss of content or functionality (except for captions and images of text).

Images of text are not used to convey information except where: (1) Customizable — the image can be visually customized to the user's requirements; or (2) Essential — a specific visual presentation is essential (logos are the primary example). Purely decorative images of text should have empty alt text under 1.1.1 but are not a defined exception to this criterion.

Content can be presented without horizontal scrolling at a width of 320 CSS pixels (400% zoom on a 1280px-wide screen).

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

No loss of content when text spacing properties are modified (line height, letter spacing, word spacing, paragraph spacing).

Content triggered by hover or focus is dismissible, hoverable, and persistent.

More than one way to locate a web page within a set of pages (e.g., search + sitemap, or search + navigation).

Headings and labels describe topic or purpose.

Any keyboard-operable UI has a visible focus indicator.

The focus indicator area meets minimum size (perimeter of focused component) and contrast requirements.

All functionality using dragging can be accomplished with a single pointer without dragging.

The target size for pointer inputs is at least 24×24 CSS pixels, unless one of these exceptions applies: Inline (in a sentence/list), Spacing (a 24px circle centered on the target doesn't intersect another target or its spacing), Equivalent (another control on the same page performs the same action), User Agent (size determined by the browser, not the author), or Essential (a particular size is required by the specific presentation).

The human language of passages in a different language can be programmatically determined (e.g., lang="fr" on a French quote).

Navigation mechanisms that repeat across multiple pages appear in the same relative order each time.

Components with the same functionality across pages are identified consistently.

If an input error is detected, suggestions for correction are provided (unless it would jeopardize security).

Submissions that commit legal or financial transactions are reversible, checked for errors, or confirmed before final submission.

A cognitive function test (memorizing a password, solving a puzzle) is not the only means of authentication unless an alternative or help is available.

Status messages (success, error, progress) can be programmatically determined through role or properties so they can be announced by assistive technology without receiving focus.