Skip to main content

WCAG 2.2 Checklist: How to Test Every AA Criterion

Benjamin Morton

This is a test list rather than an overview. It covers every Level A and Level AA success criterion in WCAG 2.2, grouped by the four principles. Each row gives the requirement in plain words, the axe-core rule IDs that check part of it (if there are any), the manual step that covers the rest, and the condition that counts as a pass. The six A and AA criteria added in 2.2 are marked New in 2.2.

The criteria and their levels come from the WCAG 2.2 Recommendation, and the rule mappings come from the axe-core 4.14 rule list. If you first need to know which law asks for which WCAG version, start with our map of accessibility laws.

TL;DR: WCAG 2.2 has 31 Level A and 24 Level AA success criteria, so AA conformance means 55 checks. Six of them are new in 2.2: 2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8. 4.1.1 Parsing is obsolete and removed. axe-core has a rule that runs by default for 20 of the 55, or 21 once target-size is on, and none of those rules proves a criterion on its own. The other 34 criteria need a person.

How to Use This Checklist

Do the automated column first. Run axe-core with the tags wcag2a, wcag2aa, wcag21a, wcag21aa and wcag22aa in CI so a violation blocks the merge; our GitHub Actions walkthrough has the setup. Then work down the manual column with a keyboard, a screen reader, browser zoom and a contrast checker.

Read a clean axe result as "nothing axe can detect is wrong", not as a pass. That is why every row has a manual step, including the rows with rules. Our automated versus manual results show how big that gap is.

What 2.2 Added and Removed

WCAG 2.2 added nine success criteria. Six sit at Level A or AA and are in the tables below. The other three (2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance and 3.3.9 Accessible Authentication (Enhanced)) are Level AAA, so they are not part of AA conformance.

4.1.1 Parsing is now labeled "Obsolete and removed". W3C's reasoning is that assistive technology no longer parses HTML directly, so the problems it addressed "either no longer exist or are addressed by other criteria" (W3C, 2024). There is a catch for older policies: W3C adds that anyone whose policy still names WCAG 2.0 or 2.1 might have to keep checking 4.1.1 and including it in reports. axe-core's two Parsing rules, duplicate-id and duplicate-id-active, are deprecated and off by default.

Perceivable: 20 Criteria

Text alternatives, captions, structure and visual presentation. For contrast fixes in CSS, see our contrast ratio guide; for alt text and labels, see the top ten violations, with code.

Criterion

Level

Requirement

axe-core rules

Manual test

Pass when

1.1.1 Non-text Content

A

Images, icons and other non-text content have a text alternative that serves the same purpose

image-alt, input-image-alt, object-alt, role-img-alt, svg-img-alt, aria-meter-name, aria-progressbar-name

Read each alt text in context; check decorative images are skipped by a screen reader

Every informative image has an accurate alternative; decorative ones have alt="" or are hidden

1.2.1 Audio-only and Video-only (Prerecorded)

A

Recorded audio has a transcript; silent video has a text or audio alternative

None (audio-caption is deprecated)

Find each audio file and silent video, then look for the alternative beside it

Each has an equivalent alternative

1.2.2 Captions (Prerecorded)

A

Recorded video with sound has captions

video-caption (review only)

Watch with captions on: check accuracy, timing, speaker changes and meaningful sounds

Captions exist and match the audio

1.2.3 Audio Description or Media Alternative (Prerecorded)

A

Recorded video has audio description or a full text alternative

None

Listen without watching: is visual-only information described? If not, find a text alternative

Visual information is available as audio or text

1.2.4 Captions (Live)

AA

Live audio in video has captions

None

Join a live stream or webinar and turn captions on

Live captions are provided

1.2.5 Audio Description (Prerecorded)

AA

Recorded video has audio description

None

As 1.2.3, but a text alternative alone no longer passes

Important visual content is described in audio

1.3.1 Info and Relationships

A

Structure shown visually (headings, lists, tables, groups) is in the markup

list, listitem, definition-list, dlitem, td-headers-attr, th-has-data-cells, aria-required-children, aria-required-parent, aria-hidden-body

Use a screen reader's headings and landmarks lists; check data tables have header cells and related fields are grouped

Markup carries the structure the page shows

1.3.2 Meaningful Sequence

A

When order matters, code order matches the meaning

None

Read the page with a screen reader or with CSS off and compare with the visual order

Content reads in a sensible order

1.3.3 Sensory Characteristics

A

Instructions don't rely only on shape, color, size, position or sound

None

Search the copy for "the round button", "on the right" and similar

Each instruction also names the thing in text

1.3.4 Orientation

AA

Content works in portrait and landscape unless one is essential

None by default (css-orientation-lock is experimental)

Rotate a phone and a tablet on key pages

Nothing is locked to one orientation

1.3.5 Identify Input Purpose

AA

Fields that collect the user's own data declare their purpose

autocomplete-valid (checks only fields that already have autocomplete)

Check name, email, phone, address and payment fields

Each has the correct autocomplete token

1.4.1 Use of Color

A

Color is not the only way information is shown

link-in-text-block

View pages in grayscale: links in text, required fields, errors, chart series, status badges

Everything still reads correctly without color

1.4.2 Audio Control

A

Audio that autoplays for more than 3 seconds can be paused, stopped or turned down

no-autoplay-audio (review only)

Load each page with sound on

No such audio, or a control stops it or sets its volume

1.4.3 Contrast (Minimum)

AA

Text has at least 4.5:1 contrast, or 3:1 for large text

color-contrast

Check what axe flags for review (text on images, gradients, overlaps) plus hover, focus and error states

All text meets its ratio

1.4.4 Resize Text

AA

Text zooms to 200% without loss of content or function

meta-viewport (only catches zoom blocked in the viewport tag)

Zoom the browser to 200% and use every feature

Nothing is cut off, overlapping or unusable

1.4.5 Images of Text

AA

Real text is used instead of pictures of text

None

Look for banners, buttons and headings that are images

Only logos, or cases where the look is essential, are images of text

1.4.10 Reflow

AA

Content fits 320 CSS px wide without scrolling both ways

None

Set a 1280 px window to 400% zoom, or a 320 px wide viewport

No two-way scrolling except maps, data tables and similar

1.4.11 Non-text Contrast

AA

Control boundaries, states and meaningful graphics have 3:1 contrast

None

Measure input borders, icon buttons, focus indicators, checkbox states and chart lines

Each reaches 3:1 against adjacent colors

1.4.12 Text Spacing

AA

Content survives users increasing text spacing

avoid-inline-spacing (inline styles only)

Apply line height 1.5, paragraph spacing 2, letter spacing 0.12 and word spacing 0.16 times the font size with a user stylesheet

No text is clipped or overlapping

1.4.13 Content on Hover or Focus

AA

Tooltips and popovers can be dismissed, hovered and stay visible

None

Hover and tab to each one; press Esc; move the pointer onto it

Esc closes it without moving focus, it stays while hovered, and it stays until the trigger is removed or it is dismissed

Operable: 20 Criteria

Keyboard access, timing, navigation and pointer input. Focus order, visible focus and 2.4.11 are covered in depth in our SPA focus guide, and link text for 2.4.4 in our "read more" link post.

Criterion

Level

Requirement

axe-core rules

Manual test

Pass when

2.1.1 Keyboard

A

Everything works from a keyboard

scrollable-region-focusable, frame-focusable-content, server-side-image-map

Put the mouse away; use Tab, Shift+Tab, Enter, Space and arrows through every flow

Every function can be reached and used

2.1.2 No Keyboard Trap

A

Keyboard focus can always leave a component

None

Tab into embeds, modals, editors and date pickers, then try to leave

Focus never gets stuck, or the way out is explained

2.1.4 Character Key Shortcuts

A

Single-key shortcuts can be turned off, remapped, or work only on focus

None

List the app's shortcuts; press letter keys with focus on the page

No single-key shortcut fires unless one of those three holds

2.2.1 Timing Adjustable

A

Time limits can be turned off, adjusted or extended

meta-refresh

Let session and form timeouts run

A warning leaves 20 seconds or more to extend with a simple action, or an exception applies

2.2.2 Pause, Stop, Hide

A

Moving or auto-updating content can be paused, stopped or hidden

blink, marquee

Find carousels, animations and live feeds that start on their own

Anything that moves for more than 5 seconds, or auto-updates, has a control

2.3.1 Three Flashes or Below Threshold

A

Nothing flashes more than three times a second

None

Review videos, animations and GIFs for flashing

No flashing above the limit

2.4.1 Bypass Blocks

A

Users can skip blocks repeated on every page

bypass (review only)

Press Tab on load and use the skip link; check landmarks with a screen reader

Users can jump straight to the main content

2.4.2 Page Titled

A

Each page has a descriptive title

document-title

Read tab titles across pages, including after client-side route changes

Each title describes the page

2.4.3 Focus Order

A

Focus order preserves meaning and operation

None

Tab through pages, opening and closing dialogs and menus

Focus follows a logical order

2.4.4 Link Purpose (In Context)

A

Each link's purpose is clear from its text or context

link-name, area-alt

Read each link with its sentence, list item or cell; flag "click here" with no context

No link is empty or ambiguous

2.4.5 Multiple Ways

AA

There is more than one way to find a page

None

Look for navigation, search, a sitemap or related links

At least two ways exist (steps in a process are exempt)

2.4.6 Headings and Labels

AA

Headings and labels describe their topic or purpose

None

Read the headings list and the form labels on their own

Each says what its section or field is for

2.4.7 Focus Visible

AA

Keyboard focus always has a visible indicator

None

Tab through every control in each theme

You can always see where focus is

2.4.11 Focus Not Obscured (Minimum), New in 2.2

AA

A focused element is not completely hidden by content the site added

None

Tab with sticky headers, footers, cookie banners and chat widgets showing, at mobile and desktop widths

Part of the focused element is always visible

2.5.1 Pointer Gestures

A

Multi-finger or path-based gestures have a single-pointer alternative

None

Find pinch, two-finger and swipe-path gestures in maps, carousels and sliders

Each also works with simple taps or clicks

2.5.2 Pointer Cancellation

A

Single-pointer actions can be cancelled

None

Press on a control, slide off it, release

The action doesn't fire, or can be undone

2.5.3 Label in Name

A

A control's accessible name contains its visible label

label-content-name-mismatch

Compare visible text with the accessible name in dev tools; try a voice command using the visible words

The name contains the visible text

2.5.4 Motion Actuation

A

Shake or tilt features have a UI alternative and can be turned off

None

Look for shake-to-undo or tilt controls on mobile

A button alternative exists and motion can be disabled

2.5.7 Dragging Movements, New in 2.2

AA

Anything done by dragging also works with single clicks or taps

None

Use sliders, sortable lists, kanban boards and map panning without dragging

Each has a non-drag way, unless dragging is essential

2.5.8 Target Size (Minimum), New in 2.2

AA

Pointer targets measure 24 by 24 CSS px or more, or are spaced so 24 px circles around them don't touch other targets

target-size (off by default)

Measure small icon buttons, close buttons and pagination in dev tools, and anything axe flags for review

Size or spacing passes, or an exception applies: equivalent control, inline text, user agent control, essential

Understandable: 13 Criteria

Language, predictable behavior and form input. Most of this principle has no automated coverage, so it is where manual time goes.

Criterion

Level

Requirement

axe-core rules

Manual test

Pass when

3.1.1 Language of Page

A

The page's main language is set in code

html-has-lang, html-lang-valid, html-xml-lang-mismatch

Check the lang value matches the language the page is written in

<html lang> is present, valid and right

3.1.2 Language of Parts

AA

Passages in another language are marked up

valid-lang (checks values that exist)

Find quotes, foreign-language passages and language switchers

Each has a correct lang attribute

3.2.1 On Focus

A

Focusing a control doesn't change context

None

Tab through every control

Nothing navigates, submits or opens a window on focus alone

3.2.2 On Input

A

Changing a setting doesn't change context without warning

None

Change every select, radio button and checkbox

No surprise navigation or submission

3.2.3 Consistent Navigation

AA

Repeated navigation keeps the same relative order

None

Compare header, menu and footer across templates

The order is the same on every page

3.2.4 Consistent Identification

AA

Components with the same function are labeled the same way

None

Compare search, cart, download and icon-button names across pages

Same function, same name

3.2.6 Consistent Help, New in 2.2

A

Help (contact details, contact form, self-help, chatbot) repeated across pages keeps the same relative order

None

Open several pages and note where each help item sits in the page order

Help items keep the same order relative to other content

3.3.1 Error Identification

A

Detected input errors are identified and described in text

None

Submit each form empty and with bad data

The field in error is identified and the error described in text

3.3.2 Labels or Instructions

A

Inputs have labels or instructions

form-field-multiple-labels (review only); see label under 4.1.2

Check every field has a visible label and formats are explained before entry

Each input has a visible label or instruction

3.3.3 Error Suggestion

AA

When a fix for an error is known, it is suggested

None

Enter a malformed email, date and ZIP code

The message says how to fix it, unless that would weaken security

3.3.4 Error Prevention (Legal, Financial, Data)

AA

Binding, financial and data-changing submissions can be checked, confirmed or reversed

None

Walk checkout, account deletion and any binding submission

The user can review and correct first, or undo afterwards

3.3.7 Redundant Entry, New in 2.2

A

Information already given in the same process is filled in or selectable

None

Run multi-step flows such as checkout and sign-up; note anything asked twice

Repeats are auto-filled or selectable, unless re-entry is essential, needed for security, or the old value is no longer valid

3.3.8 Accessible Authentication (Minimum), New in 2.2

AA

No login step requires a cognitive function test such as recalling or transcribing, unless help or an alternative exists

None

Sign in with a password manager, paste the password and any one-time code, and try each CAPTCHA route

Every step allows paste or autofill, offers another method, or only asks the user to recognize objects or their own content

Robust: 2 Criteria

How components expose themselves to assistive technology. Most failures here come from custom widgets and misused ARIA; the ARIA mistakes post covers the usual ones.

Criterion

Level

Requirement

axe-core rules

Manual test

Pass when

4.1.2 Name, Role, Value

A

Every control exposes its name, role, state and value

button-name, link-name, label, select-name, input-button-name, input-image-alt, summary-name, frame-title, frame-title-unique, nested-interactive, duplicate-id-aria, area-alt, plus 16 aria-* rules such as aria-roles and aria-hidden-focus

Use menus, tabs, toggles, comboboxes and accordions with a screen reader

Each announces its name, role and state, and updates when the state changes

4.1.3 Status Messages

AA

Status messages are announced without moving focus

None

With a screen reader on, add to cart, search and submit a form

The message is announced (for example through role="status") while focus stays put

4.1.1 Parsing has no row because it no longer exists in 2.2. Test it only if you report against WCAG 2.0 or 2.1.

Reading the axe-core Column

Counting the rows: 20 of the 55 criteria have at least one axe-core rule that runs by default, and target-size makes it 21. For four of those (1.2.2, 1.4.2, 2.4.1 and 3.3.2), the only rule marks items for review and never reports a failure on its own. That leaves 34 criteria with no default rule at all.

A few version details matter when you set up a pipeline:

  • target-size is disabled by default. axe-core runs it when you filter by the wcag22aa tag or enable the rule by name. a11yFlow's WCAG 2.2 AA scans switch it on.
  • label-content-name-mismatch changed status. It was experimental, and off by default, in axe-core 4.11; the 4.14 rule list includes it with the WCAG 2.1 rules. Check the version your tools ship.
  • Experimental and deprecated rules don't run unless you ask for them. That is why 1.3.4 and 1.2.1 count as manual-only above.

Frequently Asked Questions

How many success criteria are in WCAG 2.2 Level AA?

55: 31 at Level A and 24 at Level AA. Claiming AA conformance means meeting all of them. Level AAA adds another 31.

Can axe-core test WCAG 2.2 AA on its own?

No. Its default rules touch 20 of the 55 criteria, or 21 with target-size, and each rule checks only part of its criterion. The other 34 criteria need manual testing.

Do I still need to test 4.1.1 Parsing?

Not for WCAG 2.2. If a contract or law holds you to WCAG 2.0 or 2.1 (Section 508 uses 2.0), W3C says you might still have to check it and report on it.

Which WCAG 2.2 criteria are new?

Nine. Six are Level A or AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum). Three are AAA: 2.4.12, 2.4.13 and 3.3.9.

The Bottom Line

Treat WCAG 2.2 AA as 55 separate tests. Automate the 20 or so that axe-core can partly check, gate them in CI, and schedule a manual pass for everything else, starting with the six criteria new in 2.2, since older audits will not have covered them. Then use the law map to confirm which version your obligations cite.