Skip to contentAltstamp
Menu

WCAG 2.2 AA checklist

Every Level A and AA success criterion in WCAG 2.2, each with a test you can run without reading code. Mark each one Pass, Fail, Not applicable or Not checked as you go; the list remembers your answers in this browser and prints as a dated record.

Work through the 55 criteria

Pick a word for each criterion as you test. Your answers stay in this browser on this device and are never sent anywhere; print or copy the list to keep a record.

Progress

Show

Perceivable (20 criteria)

Can every visitor see or hear what is there?

1.1 Text Alternatives

1.1.1Non-text ContentA

Every photo, icon and image button has a text alternative that says what it shows or what it does. Pure decoration has empty alt (alt="") so screen readers skip it.

1.2 Time-based Media

1.2.1Audio-only and Video-only (Prerecorded)A

A recorded audio clip or podcast has a transcript. A recorded video with no soundtrack has a transcript or an audio track that tells the same story.

1.2.2Captions (Prerecorded)A

Every recorded video with speech or meaningful sound has captions, and the captions match what is said. Auto-captions left unchecked usually fail.

1.2.3Audio Description or Media Alternative (Prerecorded)A

When a recorded video shows something the soundtrack never says (on-screen text, a demo), there is audio description or a full text version.

1.2.4Captions (Live)AA

Live video streamed on the site, such as a webinar or a live event, has live captions.

1.2.5Audio Description (Prerecorded)AA

Recorded videos have audio description for what is only shown on screen. At AA a text version alone does not meet this one.

1.3 Adaptable

1.3.1Info and RelationshipsA

Things that look like headings, lists and data tables are built as headings, lists and tables, and every form field has a label tied to it.

1.3.2Meaningful SequenceA

Read the page with a screen reader or your browser's reader view: the content comes out in an order that still makes sense.

1.3.3Sensory CharacteristicsA

Instructions never rely only on shape, colour, size, position or sound, such as "press the round button" or "see the box on the right".

1.3.4OrientationAA

Turn your phone sideways and back: the site works in both portrait and landscape and never asks you to rotate.

1.3.5Identify Input PurposeAA

Fields asking for the visitor's own details (name, email, phone, address) can be filled by the browser's autofill. Your developer sets this with the autocomplete attribute.

1.4 Distinguishable

1.4.1Use of ColorA

Colour is never the only signal: links in a paragraph are underlined or otherwise marked, and errors and required fields say so in words.

1.4.2Audio ControlA

No sound plays by itself for more than 3 seconds unless there is a control to pause or stop it, or to set its volume apart from the system volume.

1.4.3Contrast (Minimum)AA

Text has a contrast ratio of at least 4.5:1 against its background, and large text at least 3:1. Logos are exempt. Measure it with the contrast check.

1.4.4Resize TextAA

Zoom the browser to 200%: all text grows and nothing is cut off, overlapping or missing.

1.4.5Images of TextAA

Words are real text, not pictures of words. A menu, price list or sale banner saved as one image fails; a logo is fine.

1.4.10ReflowAA

Set a 1280px-wide browser to 400% zoom (that is 320 CSS pixels wide): the page reads top to bottom with no sideways scrolling. Maps and data tables are exempt.

1.4.11Non-text ContrastAA

Input borders, button edges, icons that carry meaning and the focus ring have at least 3:1 contrast against the colours next to them.

1.4.12Text SpacingAA

With a text-spacing bookmarklet (line height 1.5, paragraph spacing 2, letter spacing 0.12 and word spacing 0.16 times the font size), no text is cut off or overlaps.

1.4.13Content on Hover or FocusAA

Tooltips and menus that open on hover or focus close with Escape without moving the mouse, stay open while you move the pointer onto them, and do not vanish on a timer.

Operable (20 criteria)

Can every visitor use it, without a mouse and without a rush?

2.1 Keyboard Accessible

2.1.1KeyboardA

Put the mouse away and use Tab, Shift+Tab, Enter, Space and the arrow keys: every link, menu, button, form and pop-up works.

2.1.2No Keyboard TrapA

Tab into every widget (a chat box, video player, map or booking frame) and Tab back out of it. You never get stuck.

2.1.4Character Key ShortcutsA

Single-key shortcuts (a letter or number pressed without Ctrl or Alt) can be turned off or changed, or work only while their part has focus. Most small sites have none: mark it Not applicable.

2.2 Enough Time

2.2.1Timing AdjustableA

A time limit (a booking hold, a session timeout) can be turned off or lengthened, or it warns you and gives at least 20 seconds to extend it with one simple action.

2.2.2Pause, Stop, HideA

A slider, carousel, ticker or animation that starts by itself and runs longer than 5 seconds has a pause or stop control.

2.3 Seizures and Physical Reactions

2.3.1Three Flashes or Below ThresholdA

Nothing on the page flashes more than three times in any one second.

2.4 Navigable

2.4.1Bypass BlocksA

Press Tab once on a fresh page: a "Skip to content" link (or proper landmarks) lets a keyboard user jump past the menu.

2.4.2Page TitledA

Each page's title, the text on the browser tab, says what the page is, such as "Book a table | Rosa's Kitchen".

2.4.3Focus OrderA

As you Tab, focus moves in an order that matches the page: menu, content, footer. A pop-up takes focus when it opens and gives it back when it closes.

2.4.4Link Purpose (In Context)A

Each link says where it goes, alone or with its sentence. A row of bare "Read more" links with no context fails.

2.4.5Multiple WaysAA

Visitors can reach a page in more than one way: the menu plus a search box, a site map or links between related pages.

2.4.6Headings and LabelsAA

Headings and form labels describe what comes after them. "Field 1" or a heading that just says "Welcome" on every page says nothing.

2.4.7Focus VisibleAA

As you Tab, you can always see where you are: a clear outline or ring on the focused link, button or field.

2.4.11Focus Not Obscured (Minimum)AANew in 2.2

As you Tab, the focused item is never completely hidden behind a sticky header, a cookie banner or a chat bubble.

2.5 Input Modalities

2.5.1Pointer GesturesA

Anything that needs a pinch, a two-finger move or a drawn path (a map, a gallery) can also be done with single taps, such as + and - buttons or arrows.

2.5.2Pointer CancellationA

Buttons act when you let go, not the moment you press, so sliding your finger off before releasing cancels, or the action can be undone.

2.5.3Label in NameA

A control's hidden name contains the words shown on it: a button labelled "Send" is not called "Submit form" to screen readers and voice control.

2.5.4Motion ActuationA

Anything done by shaking or tilting the device also has a button, and the motion can be switched off. Most sites: Not applicable.

2.5.7Dragging MovementsAANew in 2.2

Anything done by dragging (a price slider, a map, a before-and-after image, reordering a list) can also be done with taps or clicks.

2.5.8Target Size (Minimum)AANew in 2.2

Buttons, icons and links you tap are at least 24 by 24 CSS pixels, or have enough space around them. Links inside a sentence are exempt.

Understandable (13 criteria)

Is it predictable, and do forms help people get it right?

3.1 Readable

3.1.1Language of PageA

The page's code names its language (lang="en" on the html element) so screen readers pronounce it right. View the page source, or ask your developer.

3.1.2Language of PartsAA

A passage in another language, such as your opening hours in Spanish, is marked with its own language.

3.2 Predictable

3.2.1On FocusA

Tabbing onto a field or button never opens a new page or window, or submits anything, by itself.

3.2.2On InputA

Picking an option or ticking a box does not jump to a new page or send the form, unless the page said beforehand that it would.

3.2.3Consistent NavigationAA

The main menu and other repeated links appear in the same order on every page.

3.2.4Consistent IdentificationAA

Things that do the same job are named the same way on every page: the search box is not "Search" on one page and "Find" on the next.

3.2.6Consistent HelpANew in 2.2

Help you offer on several pages (phone number, email, contact form, chat, FAQ link) sits in the same place in the page order on each of them.

3.3 Input Assistance

3.3.1Error IdentificationA

Send a form with a mistake in it: the field with the problem is pointed out and the error is described in words, not just outlined in red.

3.3.2Labels or InstructionsA

Every field has a visible label or instructions, including any format you need (such as a date as MM/DD/YYYY) and which fields are required.

3.3.3Error SuggestionAA

When the site knows how to fix an error it says so: "Enter an email address like name@example.com", not just "Invalid".

3.3.4Error Prevention (Legal, Financial, Data)AA

Before an order, payment, booking or account change is final, the visitor can check and correct it, or can undo it afterwards.

3.3.7Redundant EntryANew in 2.2

In a multi-step form, details already given (a delivery address, an email) are filled in or offered to pick, not typed a second time.

3.3.8Accessible Authentication (Minimum)AANew in 2.2

Signing in never demands remembering, retyping or solving something without another way: password managers and paste work, and a puzzle CAPTCHA (other than picking objects) has an alternative.

Robust (2 criteria)

Do screen readers and voice control get the right information?

4.1 Compatible

4.1.2Name, Role, ValueA

Custom controls (menus, tabs, toggles, accordions) tell a screen reader what they are, what they are called and whether they are open, on or selected.

4.1.3Status MessagesAA

Messages that appear without moving focus ("Added to cart", "3 results", "Message sent") are read out by a screen reader.

Line drawing of a checklist on a clipboard with one box ringed in orange

What WCAG asks

  • 2.4.11Focus Not Obscured (Minimum)AA
  • 2.5.7Dragging MovementsAA
  • 2.5.8Target Size (Minimum)AA
  • 3.2.6Consistent HelpA
  • 3.3.7Redundant EntryA
  • 3.3.8Accessible Authentication (Minimum)AA

What it checks

WCAG 2.2 has 86 success criteria: 31 at Level A, 24 at Level AA and 31 at Level AAA. Meeting Level AA means meeting 55 (A + AA), and those 55 are the list above, with the number, name and level of each copied from the W3C text. Six of them are new in WCAG 2.2 and carry that label; our guide to what changed in WCAG 2.2 explains each one.

The list is grouped by WCAG's four principles, in the spec's own order, for one practical reason: an auditor's report, a VPAT® and the W3C text all run in that order, so the record you print here lines up with whatever you are handed next. If you would rather walk the site by page part (menu, images, forms, video, PDFs), the ADA website checklist is built that way. For the basics behind the four principles, read what WCAG is.

Each line carries a plain test written for an owner, not a developer. The tests are a first pass: they find the problems you can see and hear, and they tell you which lines need someone who can read the code. Four words record the result: Pass, Fail, Not applicable (no video on the site, so no captions to check) and Not checked.

How to work through it

Going down the list in number order means switching tools every few lines. Testing goes faster in sittings: one way of using the site at a time, ticking off every criterion that sitting answers. The six below cover all 55 between them.

Six sittings that cover all 55 Level A and AA criteria
SittingWhat you doCriteria it answers
KeyboardMouse away. Tab through the home page, one service or product page and the contact form.2.1.1, 2.1.2, 2.4.1, 2.4.3, 2.4.7, 2.4.11, 3.2.1, 1.4.13
Zoom and phoneZoom to 200% and 400%, try a text-spacing bookmarklet, then use the site on a phone both ways up.1.4.4, 1.4.10, 1.4.12, 1.3.4, 2.5.8
Eyes and earsLook at every image, colour cue, video, slider and sound with the questions in the list.1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.3, 1.4.1, 1.4.2, 1.4.3, 1.4.5, 1.4.11, 2.2.2, 2.3.1
FormsSend each form once with mistakes, then complete a booking, order or sign-in from start to finish.1.3.5, 2.2.1, 3.2.2, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8
Screen readerListen to the same pages with a screen reader: headings, links, buttons, messages.1.3.1, 1.3.2, 2.4.2, 2.4.4, 2.4.6, 2.5.3, 3.1.1, 3.1.2, 4.1.2, 4.1.3
Across pagesOpen three pages side by side and compare menus, help and names; then try every drag, swipe and shortcut.2.1.4, 2.4.5, 2.5.1, 2.5.2, 2.5.4, 2.5.7, 3.2.3, 3.2.4, 3.2.6
  1. Pick the pages you test: the home page, one page of each template (a service or product page, a blog post), the contact form and any booking, checkout or sign-in, from start to finish. WCAG judges a full page, and a process only conforms when every step of it does.
  2. Do the keyboard sitting first. It needs nothing but the Tab key, and the focus order checklist walks you through it stop by stop. What a good focus ring looks like is in focus indicators.
  3. Use the checks on this site for the lines that need a measurement: the contrast check for 1.4.3 and 1.4.11, the alt text check for 1.1.1.
  4. Mark a line Fail the moment you find one instance, and write where in the note. One instance fails that criterion on that page; the note is what tells the person fixing it where to look.
  5. Leave the screen reader sitting for last, or for someone who uses one daily. Our screen reader testing guide covers how an owner can start.

What WCAG asks

What WCAG asks: 5.2.1 Conformance Level

For Level AA conformance, the web page satisfies all the Level A and Level AA success criteria, or a Level AA conforming alternate version is provided.

It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content.

All of them, on the whole page: conformance is for full pages only, and it cannot be claimed if part of a page is excluded. A booking widget or chat bubble from another company is still part of your page. That is why the list has no score. Fifty-four Passes and one Fail is not Level AA.

What a fail usually looks like

The same few failures turn up year after year. WebAIM's 2026 scan of the top million home pages (results from February 2026) found detectable WCAG failures on 95.9% of them, and these six on the most:

The six most common failures in WebAIM's 2026 Million scan
FailureHome pagesCriterion
Low contrast text83.9%1.4.3
Missing alternative text for images53.1%1.1.1
Missing form input labels51%1.3.1, 3.3.2
Empty links46.3%2.4.4, 4.1.2
Empty buttons30.6%4.1.2
Missing document language13.5%3.1.1

A scanner can find those. The WCAG 2.2 lines usually fail in ways no scan sees: a cookie banner pinned to the bottom of the screen that hides the focused link (2.4.11), a row of small social icons in the footer packed tighter than 24 by 24 pixels (2.5.8), a sign-in that asks you to type characters from a distorted picture with no other way in (3.3.8). Forms break several lines at once; our guide to accessible forms takes them in order.

What this list leaves out

  • Level AAA. The 31 AAA criteria are not here, including 2.4.13 Focus Appearance, which is Level AAA, not AA, despite how often it is listed as a 2.2 requirement.
  • 4.1.1 Parsing. WCAG 2.2 removed it. If a contract binds you to WCAG 2.1, its 4.1.1 carries a note that it "should be considered as always satisfied for any content using HTML or XML".
  • WCAG 2.1 AA. The Title II rule for state and local governments names WCAG 2.1 Level AA. Use this list and skip the six lines marked New in 2.2; content that conforms to 2.2 also conforms to 2.1.
  • An audit. A first pass by an owner finds a lot, but a claim of conformance needs testing by someone who reads the code. The WCAG audit services comparison covers who does that.

When the list is done, the Fails are your fix list and the date at the top of the printout is your baseline. The order to fix them in, and the retest after, is the plan in how to make a website ADA compliant. The accessibility statement generator turns the known issues into a public statement. This is general information, not legal advice. For your own situation, ask a lawyer.

Related