WCAG 2.2 Success Criteria Checklist

Every WCAG 2.2 success criterion in one interactive checklist. Filter by level, principle or what is new in 2.2, mark each one pass, fail or not applicable with notes, and export the audit to CSV or Markdown. Progress is saved in your browser.

100% free · No sign-up · No watermarks

Level AA progress

0 of 55 criteria reviewed · saved in this browser

Pass 0Fail 0N/A 0To do 55

Target level

Showing 55 of 86 success criteria

  1. 1.1.1 Non-text ContentA

    Every image, icon and control has a text alternative that serves the same purpose; decorative images are hidden from assistive tech.

    Understanding 1.1.1
  2. 1.2.1 Audio-only and Video-only (Prerecorded)A

    Prerecorded audio-only content has a transcript; prerecorded video-only content has a transcript or audio track.

    Understanding 1.2.1
  3. 1.2.2 Captions (Prerecorded)A

    Prerecorded video with audio has synchronised captions.

    Understanding 1.2.2
  4. 1.2.3 Audio Description or Media Alternative (Prerecorded)A

    Prerecorded video has audio description or a full text alternative.

    Understanding 1.2.3
  5. 1.2.4 Captions (Live)AA

    Live video with audio has real-time captions.

    Understanding 1.2.4
  6. 1.2.5 Audio Description (Prerecorded)AA

    Prerecorded video has audio description of important visual information.

    Understanding 1.2.5
  7. 1.3.1 Info and RelationshipsA

    Structure conveyed visually — headings, lists, tables, labels — is also in the markup.

    Understanding 1.3.1
  8. 1.3.2 Meaningful SequenceA

    The DOM order matches the reading order when order affects meaning.

    Understanding 1.3.2
  9. 1.3.3 Sensory CharacteristicsA

    Instructions do not rely only on shape, size, location, orientation or sound.

    Understanding 1.3.3
  10. 1.3.4 OrientationAA

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

    Understanding 1.3.4
  11. 1.3.5 Identify Input PurposeAA

    Inputs collecting user data declare their purpose, e.g. with the autocomplete attribute.

    Understanding 1.3.5
  12. 1.4.1 Use of ColorA

    Colour is never the only way information, an action or a state is conveyed.

    Understanding 1.4.1
  13. 1.4.2 Audio ControlA

    Audio that plays automatically for more than 3 seconds can be paused, stopped or turned down.

    Understanding 1.4.2
  14. 1.4.3 Contrast (Minimum)AA

    Text has at least 4.5:1 contrast, or 3:1 for large text (24px, or 18.66px bold).

    Understanding 1.4.3
  15. 1.4.4 Resize TextAA

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

    Understanding 1.4.4
  16. 1.4.5 Images of TextAA

    Real text is used instead of images of text, except for logos or where customisable.

    Understanding 1.4.5
  17. 1.4.10 ReflowAA

    Content reflows at 320 CSS px wide (400% zoom) without two-dimensional scrolling.

    Understanding 1.4.10
  18. 1.4.11 Non-text ContrastAA

    UI component boundaries, states and meaningful graphics have at least 3:1 contrast against adjacent colours.

    Understanding 1.4.11
  19. 1.4.12 Text SpacingAA

    Nothing is lost when users increase line height, paragraph, letter and word spacing.

    Understanding 1.4.12
  20. 1.4.13 Content on Hover or FocusAA

    Tooltips and popovers shown on hover or focus are dismissible, hoverable and persistent.

    Understanding 1.4.13
  21. 2.1.1 KeyboardA

    All functionality works from a keyboard without specific timings.

    Understanding 2.1.1
  22. 2.1.2 No Keyboard TrapA

    Keyboard focus can always move away from any component.

    Understanding 2.1.2
  23. 2.1.4 Character Key ShortcutsA

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

    Understanding 2.1.4
  24. 2.2.1 Timing AdjustableA

    Users can turn off, adjust or extend time limits.

    Understanding 2.2.1
  25. 2.2.2 Pause, Stop, HideA

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

    Understanding 2.2.2
  26. 2.3.1 Three Flashes or Below ThresholdA

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

    Understanding 2.3.1
  27. 2.4.1 Bypass BlocksA

    A skip link or landmarks let users bypass blocks repeated across pages.

    Understanding 2.4.1
  28. 2.4.2 Page TitledA

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

    Understanding 2.4.2
  29. 2.4.3 Focus OrderA

    Focus moves through the page in an order that preserves meaning and operability.

    Understanding 2.4.3
  30. 2.4.4 Link Purpose (In Context)A

    The purpose of each link is clear from its text, or its text plus surrounding context.

    Understanding 2.4.4
  31. 2.4.5 Multiple WaysAA

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

    Understanding 2.4.5
  32. 2.4.6 Headings and LabelsAA

    Headings and labels describe their topic or purpose.

    Understanding 2.4.6
  33. 2.4.7 Focus VisibleAA

    Every keyboard-focusable element has a visible focus indicator.

    Understanding 2.4.7
  34. 2.4.11 Focus Not Obscured (Minimum)AANew in 2.2

    A focused component is never entirely hidden by author content such as sticky headers, footers or cookie banners.

    Understanding 2.4.11
  35. 2.5.1 Pointer GesturesA

    Multipoint or path-based gestures have a single-pointer alternative.

    Understanding 2.5.1
  36. 2.5.2 Pointer CancellationA

    Actions fire on the up-event, or can be aborted or undone.

    Understanding 2.5.2
  37. 2.5.3 Label in NameA

    A control's accessible name contains the text of its visible label.

    Understanding 2.5.3
  38. 2.5.4 Motion ActuationA

    Functions triggered by device motion also have a UI control and can be disabled.

    Understanding 2.5.4
  39. 2.5.7 Dragging MovementsAANew in 2.2

    Anything done by dragging can also be done with a single pointer without dragging.

    Understanding 2.5.7
  40. 2.5.8 Target Size (Minimum)AANew in 2.2

    Pointer targets are at least 24 by 24 CSS px, or spaced so a 24 px circle around each does not touch another target.

    Understanding 2.5.8
  41. 3.1.1 Language of PageA

    The page's default human language is set, e.g. <html lang>.

    Understanding 3.1.1
  42. 3.1.2 Language of PartsAA

    Passages in a different language are marked with their own lang attribute.

    Understanding 3.1.2
  43. 3.2.1 On FocusA

    Receiving focus never triggers a change of context.

    Understanding 3.2.1
  44. 3.2.2 On InputA

    Changing a setting does not change context unless users were told beforehand.

    Understanding 3.2.2
  45. 3.2.3 Consistent NavigationAA

    Repeated navigation appears in the same relative order on every page.

    Understanding 3.2.3
  46. 3.2.4 Consistent IdentificationAA

    Components with the same function are labelled consistently across pages.

    Understanding 3.2.4
  47. 3.2.6 Consistent HelpANew in 2.2

    Help mechanisms repeated across pages — contact details, chat, FAQ links — appear in the same relative order.

    Understanding 3.2.6
  48. 3.3.1 Error IdentificationA

    Input errors are detected, the field is identified and the error is described in text.

    Understanding 3.3.1
  49. 3.3.2 Labels or InstructionsA

    Inputs have labels or instructions.

    Understanding 3.3.2
  50. 3.3.3 Error SuggestionAA

    When an input error is detected and a fix is known, the fix is suggested.

    Understanding 3.3.3
  51. 3.3.4 Error Prevention (Legal, Financial, Data)AA

    Legal, financial and data-changing submissions are reversible, checked, or confirmed.

    Understanding 3.3.4
  52. 3.3.7 Redundant EntryANew in 2.2

    Information already entered in the same process is auto-filled or selectable instead of re-typed.

    Understanding 3.3.7
  53. 3.3.8 Accessible Authentication (Minimum)AANew in 2.2

    Login does not require a cognitive function test — remembering, transcribing, solving — unless an alternative or assistance (paste, password managers) is allowed.

    Understanding 3.3.8
  54. 4.1.2 Name, Role, ValueA

    Every UI component exposes its name, role, states and values to assistive technology.

    Understanding 4.1.2
  55. 4.1.3 Status MessagesAA

    Status messages are announced by assistive tech without receiving focus, e.g. via role=status.

    Understanding 4.1.3

Why use the WCAG 2.2 Checklist

Private by design

No account needed. What you type stays in your browser unless you ask for an AI suggestion or name a URL to fetch.

Exact WCAG 2.2 thresholds

Each check uses the success criterion's own numbers, such as 4.5:1, 24×24 CSS px or a 2 px perimeter, with no rounding up into a pass.

Named criteria

Verdicts cite the success criterion they test, so a result can go straight into an audit report.

Frequently asked questions

How many success criteria are in WCAG 2.2?

86. WCAG 2.2 added 9 new criteria to WCAG 2.1 and removed one, 4.1.1 Parsing, which had become obsolete. Of the 86, 31 are level A, 24 are level AA and 31 are level AAA.

What is new in WCAG 2.2?

Nine criteria: 2.4.11 Focus Not Obscured (Minimum), 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance, 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (Minimum) and 3.3.9 Accessible Authentication (Enhanced).

Which level do I need to meet?

Most laws and procurement rules — the European Accessibility Act via EN 301 549, Section 508, the ADA as interpreted by US courts — point at level AA. Meeting AA means meeting every A and AA criterion; AAA is generally not required for whole sites.

Where is my progress stored?

In your browser's local storage, on your machine only. Nothing is uploaded. Export to CSV or Markdown to share an audit or keep a copy, and use Reset to start a fresh one.

Updated · Built by Niraj Kumar