There are 31 Level A and 24 Level AA criteria. Rows marked NEW IN 2.2 were added in WCAG 2.2; skip them if you are reporting against WCAG 2.1, and add 4.1.1 Parsing instead. The questions are a plain-language summary, not the normative text. When a row is borderline, read the full criterion and its “Understanding” document on the W3C site.
1. Perceivable
People can perceive the content: text alternatives, captions, structure, color and contrast, and layout that adapts.
| No. | Criterion | Ask your team |
|---|---|---|
| 1.1.1 | Non-text ContentLevel A | Do images, icons, and charts have text alternatives that give the same information? |
| 1.2.1 | Audio-only and Video-only (Prerecorded)Level A | Do prerecorded audio-only or video-only clips have a transcript or an equivalent alternative? |
| 1.2.2 | Captions (Prerecorded)Level A | Do prerecorded videos with sound have accurate captions? |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded)Level A | Do prerecorded videos have audio description or a full text alternative? |
| 1.2.4 | Captions (Live)Level AA | Do live videos with sound have captions? |
| 1.2.5 | Audio Description (Prerecorded)Level AA | Do prerecorded videos have audio description of important visual content? |
| 1.3.1 | Info and RelationshipsLevel A | Are headings, lists, tables, and form labels marked up so assistive technology can tell what they are? |
| 1.3.2 | Meaningful SequenceLevel A | Does the reading order in the code match the order people see on screen? |
| 1.3.3 | Sensory CharacteristicsLevel A | Do instructions work without relying only on shape, size, position, or sound? |
| 1.3.4 | OrientationLevel AA | Does content work in both portrait and landscape orientation? |
| 1.3.5 | Identify Input PurposeLevel AA | Do fields that collect the user’s own details (name, email, address) identify their purpose with autocomplete? |
| 1.4.1 | Use of ColorLevel A | Is color never the only way information is shown, such as status, errors, required fields, or links? |
| 1.4.2 | Audio ControlLevel A | If audio plays automatically for more than 3 seconds, can people pause it or turn it down? |
| 1.4.3 | Contrast (Minimum)Level AA | Is normal text at least 4.5:1 against its background, and large text at least 3:1? |
| 1.4.4 | Resize TextLevel AA | Can text be resized to 200% without losing content or function? |
| 1.4.5 | Images of TextLevel AA | Is text shown as real text rather than images of text, except in logos? |
| 1.4.10 | ReflowLevel AA | Does content reflow at 320 CSS pixels wide without scrolling in two directions? |
| 1.4.11 | Non-text ContrastLevel AA | Do controls, focus indicators, and meaningful graphics have at least 3:1 contrast? |
| 1.4.12 | Text SpacingLevel AA | Does content still work when people increase line, letter, word, and paragraph spacing? |
| 1.4.13 | Content on Hover or FocusLevel AA | Can tooltips and pop-ups that appear on hover or focus be dismissed, hovered, and kept open? |
2. Operable
People can operate the interface: keyboard access, enough time, no seizure risks, clear navigation, and pointer and touch input.
| No. | Criterion | Ask your team |
|---|---|---|
| 2.1.1 | KeyboardLevel A | Can every function be used with a keyboard alone? |
| 2.1.2 | No Keyboard TrapLevel A | Can keyboard users always move focus out of every component, including dialogs and widgets? |
| 2.1.4 | Character Key ShortcutsLevel A | If there are single-key shortcuts, can people turn them off or remap them? |
| 2.2.1 | Timing AdjustableLevel A | If there are time limits, can people turn them off, adjust them, or extend them? |
| 2.2.2 | Pause, Stop, HideLevel A | Can people pause, stop, or hide content that moves, blinks, scrolls, or updates on its own? |
| 2.3.1 | Three Flashes or Below ThresholdLevel A | Does nothing flash more than three times in any one second? |
| 2.4.1 | Bypass BlocksLevel A | Can people skip repeated blocks such as navigation, with a skip link or landmarks? |
| 2.4.2 | Page TitledLevel A | Does every page or screen have a title that describes it? |
| 2.4.3 | Focus OrderLevel A | Does keyboard focus move in an order that keeps meaning and operation intact? |
| 2.4.4 | Link Purpose (In Context)Level A | Is each link’s purpose clear from its text or its immediate context? |
| 2.4.5 | Multiple WaysLevel AA | Is there more than one way to find a page, such as navigation, search, or a sitemap? |
| 2.4.6 | Headings and LabelsLevel AA | Do headings and labels describe their topic or purpose? |
| 2.4.7 | Focus VisibleLevel AA | Is keyboard focus always visible? |
| 2.4.11 | Focus Not Obscured (Minimum)Level AA NEW IN 2.2 | Is the focused element never completely hidden by sticky headers, footers, or overlays? |
| 2.5.1 | Pointer GesturesLevel A | Can anything done with multi-finger or path-based gestures also be done with a single tap or click? |
| 2.5.2 | Pointer CancellationLevel A | Do actions run on release rather than on press, or can they be aborted or undone? |
| 2.5.3 | Label in NameLevel A | Does each control’s accessible name include its visible label text? |
| 2.5.4 | Motion ActuationLevel A | Can anything triggered by shaking or tilting also be done through the interface, and be turned off? |
| 2.5.7 | Dragging MovementsLevel AA NEW IN 2.2 | Can anything done by dragging also be done with a single click or tap? |
| 2.5.8 | Target Size (Minimum)Level AA NEW IN 2.2 | Are click and tap targets at least 24 by 24 CSS pixels, or spaced so they don’t crowd each other? |
3. Understandable
People can understand the content and how the interface behaves: language, predictable behavior, and help with input.
| No. | Criterion | Ask your team |
|---|---|---|
| 3.1.1 | Language of PageLevel A | Is the default language of each page set in the code? |
| 3.1.2 | Language of PartsLevel AA | Are passages in a different language marked with their language? |
| 3.2.1 | On FocusLevel A | Does moving focus to an element never cause an unexpected change of context? |
| 3.2.2 | On InputLevel A | Does changing a setting or field never cause an unexpected change of context without warning? |
| 3.2.3 | Consistent NavigationLevel AA | Does repeated navigation appear in the same order across pages? |
| 3.2.4 | Consistent IdentificationLevel AA | Are components with the same function labeled the same way throughout? |
| 3.2.6 | Consistent HelpLevel A NEW IN 2.2 | Is help, such as contact details, chat, or a help link, in the same relative place on every page? |
| 3.3.1 | Error IdentificationLevel A | When an input error is detected, is the field identified and the error described in text? |
| 3.3.2 | Labels or InstructionsLevel A | Do fields that need input have labels or instructions? |
| 3.3.3 | Error SuggestionLevel AA | When an error is detected and a fix is known, is the fix suggested? |
| 3.3.4 | Error Prevention (Legal, Financial, Data)Level AA | For legal, financial, or data-changing submissions, can people review, correct, or reverse them? |
| 3.3.7 | Redundant EntryLevel A NEW IN 2.2 | Is information already entered in a process filled in or selectable, rather than asked for again? |
| 3.3.8 | Accessible Authentication (Minimum)Level AA NEW IN 2.2 | Can people sign in without a memory or transcription test, or is an alternative offered? |
4. Robust
Content works with current and future assistive technologies: names, roles, values and status messages.
| No. | Criterion | Ask your team |
|---|---|---|
| 4.1.2 | Name, Role, ValueLevel A | Do custom controls expose their name, role, state, and value to assistive technology? |
| 4.1.3 | Status MessagesLevel AA | Are status messages, such as “Saved” or a results count, announced without moving focus? |
From checklist to report
Once your team has answered these questions, you have what you need for a VPAT. For each row, choose a conformance level and write a remark in your own words.
VPAT Draft Desk asks these same questions one at a time and turns your answers into a finished WCAG 2.2 or 2.1 report in PDF and Word.
Start your VPAT