WCAG 2.2 AA Checklist: All 55 Success Criteria in Plain English

Every meaningful image, icon and chart has alt text that says what it shows; decorative images use alt="".

Audio-only and video-only clips have a transcript or a text or audio description.

Prerecorded video with sound has accurate captions.

Prerecorded video has audio description or a full text alternative.

Live video with sound has live captions.

Prerecorded video has audio description of important visual information.

Headings, lists, tables and form labels are real markup, not just visual styling.

The reading order in the code matches the visual order when meaning depends on it.

Instructions do not rely only on shape, size, position or sound ("click the round button on the right").

Content works in both portrait and landscape unless one orientation is essential.

Fields that ask for the user’s own name, email, phone or address carry the right autocomplete attribute.

Color is never the only way information is shown, such as links in body text or form errors.

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

Body text has a contrast ratio of at least 4.5:1; large text at least 3:1.

Text can be zoomed to 200% without losing content or function; zoom is not disabled in the viewport tag.

Text is real text, not text baked into images, except logos.

At 320 CSS pixels wide (400% zoom) content reflows without horizontal scrolling.

Icons, input borders and focus indicators have at least 3:1 contrast against what is next to them.

Content still works when users increase line height, letter spacing and word spacing.

Tooltips and hover content can be dismissed, hovered over and do not vanish on their own.

Everything works with a keyboard alone: menus, forms, sliders, modals and custom widgets.

Keyboard focus never gets stuck inside a component.

Single-key shortcuts can be turned off or remapped, or only work when that component has focus.

Time limits can be turned off, adjusted or extended.

Anything that moves, blinks or auto-updates for more than 5 seconds can be paused, stopped or hidden.

Nothing flashes more than three times per second.

A skip link or landmarks let keyboard users bypass repeated navigation.

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

Tab order follows a logical sequence that preserves meaning.

Link text, alone or with its context, says where the link goes; no empty or "click here" links.

There is more than one way to find a page, such as navigation plus search or a sitemap.

Headings and labels describe their topic or purpose.

Keyboard focus is always visible.

The focused element is not completely hidden by sticky headers, banners or chat widgets.

Multipoint or path gestures (pinch, swipe) have a single-pointer alternative.

Actions fire on pointer up, or can be aborted or undone.

The accessible name of a control contains its visible label text.

Features triggered by shaking or tilting the device have a button alternative and can be disabled.

Anything done by dragging can also be done with single clicks or taps.

Click and tap targets are at least 24 by 24 CSS pixels, or have enough spacing around them.

The page declares its language with a lang attribute on the html element.

Passages in another language are marked with their own lang attribute.

Focusing an element does not trigger an unexpected change of page or context.

Changing a field value does not submit a form or change context without warning.

Navigation that repeats across pages stays in the same relative order.

Components with the same function are labelled the same way across pages.

Help options such as contact details or chat appear in the same place on every page that has them.

Form errors are identified in text and say which field is wrong.

Form fields have visible labels or instructions.

Error messages suggest how to fix the problem when a fix is known.

Legal, financial and data-changing submissions can be reviewed, corrected or reversed.

Information a user already entered in the same process is filled in again or selectable, not re-typed.

Login does not require solving a puzzle or remembering a password without allowing paste or password managers.

Custom controls expose a name, role and state to assistive technology; buttons and links are not empty.

Status messages such as "Added to cart" or "3 results" are announced without moving focus.