WCAG 2.2 checklist for Level A and AA

A working checklist for the Level A and AA success criteria in WCAG 2.2, grouped by the four WCAG principles. Use it to plan manual checks alongside an automated scan.

By Allie. Published and last reviewed October 16, 2026.

WCAG 2.2 is a W3C Recommendation. It builds on WCAG 2.0 and 2.1, and the W3C says content that conforms to 2.2 also conforms to 2.0 and 2.1. Each success criterion is marked Level A, AA or AAA. Most legal and procurement requirements that mention WCAG point at Level AA, which includes every Level A criterion too. This checklist covers A and AA only.

Two housekeeping notes from the W3C: 2.2 adds nine new success criteria (six at Level A or AA, three at AAA), and it removes 4.1.1 Parsing, which the W3C calls obsolete. A checklist cannot prove conformance. Conformance applies to complete pages and complete processes, such as a whole checkout.

New in WCAG 2.2 (Level A and AA)

• 2.4.11 Focus Not Obscured (Minimum), AA. When a control gets keyboard focus, it is not entirely hidden by content you created, such as a sticky banner.
• 2.5.7 Dragging Movements, AA. Anything you can do by dragging can also be done with a single pointer without dragging, for example arrow buttons to reorder a list.
• 2.5.8 Target Size (Minimum), AA. Pointer targets are at least 24 by 24 CSS pixels, or have enough spacing, with some exceptions such as inline links in text.
• 3.2.6 Consistent Help, A. If you offer help (contact details, chat, a self-help link) on several pages, it appears in the same place relative to other content.
• 3.3.7 Redundant Entry, A. Do not make people re-enter information they already gave in the same process, unless it is essential or needed for security.
• 3.3.8 Accessible Authentication (Minimum), AA. Logging in must not require a cognitive function test, such as remembering a password or solving a puzzle, unless there is an alternative or a helper. Allowing password managers and paste meets this.

Perceivable

• 1.1.1 Non-text content (A). Images, icons and controls have a text alternative that serves the same purpose. Purely decorative images are hidden from assistive technology.
• 1.2.1 to 1.2.5 Time-based media (A, AA). Prerecorded audio and video have alternatives, captions for prerecorded video with audio, audio description or a media alternative, and live captions for live audio (AA).
• 1.3.1 Info and relationships (A). Headings, lists, tables, form labels and groupings are marked up in code, not only styled to look that way.
• 1.3.2 Meaningful sequence (A). The reading order in the code makes sense.
• 1.3.3 Sensory characteristics (A). Instructions do not rely only on shape, colour, size or position, such as “click the green button on the right”.
• 1.3.4 Orientation (AA). The page works in both portrait and landscape unless one is essential.
• 1.3.5 Identify input purpose (AA). Fields that collect personal details, such as name and email, are marked with the right autocomplete value.
• 1.4.1 Use of colour (A). Colour is not the only way to show information, an error or a required field.
• 1.4.2 Audio control (A). Audio that plays automatically for more than 3 seconds can be paused, stopped or turned down.
• 1.4.3 Contrast, minimum (AA). Text has a contrast ratio of at least 4.5:1, or 3:1 for large text.
• 1.4.4 Resize text (AA). Text can be enlarged to 200 percent without losing content or function.
• 1.4.5 Images of text (AA). Use real text rather than pictures of text, except for logos or where the look is essential.
• 1.4.10 Reflow (AA). Content works at a width of 320 CSS pixels without two-dimensional scrolling, except for things like maps and data tables.
• 1.4.11 Non-text contrast (AA). Controls, their states and meaningful graphics have at least 3:1 contrast against their neighbours.
• 1.4.12 Text spacing (AA). Nothing breaks when a user increases line, paragraph, letter and word spacing.
• 1.4.13 Content on hover or focus (AA). Tooltips and pop-ups that appear on hover or focus can be dismissed, hovered over and stay visible until dismissed.

Operable

• 2.1.1 Keyboard (A). Everything works from the keyboard.
• 2.1.2 No keyboard trap (A). Keyboard focus can always be moved away from any control.
• 2.1.4 Character key shortcuts (A). Single-key shortcuts can be turned off, remapped or only work on focus.
• 2.2.1 Timing adjustable (A). Time limits can be turned off, adjusted or extended.
• 2.2.2 Pause, stop, hide (A). Moving, blinking or auto-updating content that lasts over five seconds can be paused, stopped or hidden.
• 2.3.1 Three flashes or below threshold (A). Nothing flashes more than three times in one second, unless below the flash thresholds.
• 2.4.1 Bypass blocks (A). A skip link or landmarks let people jump past repeated navigation.
• 2.4.2 Page titled (A). Each page has a title that describes its topic or purpose.
• 2.4.3 Focus order (A). Keyboard focus moves in an order that keeps meaning.
• 2.4.4 Link purpose in context (A). You can tell where a link goes from its text and surrounding context. Avoid bare “click here”.
• 2.4.5 Multiple ways (AA). More than one way to find a page, such as navigation plus search or a site map.
• 2.4.6 Headings and labels (AA). Headings and labels describe their topic or purpose.
• 2.4.7 Focus visible (AA). The keyboard focus indicator is visible.
• 2.5.1 Pointer gestures (A). Multi-finger or path-based gestures have a single-pointer alternative.
• 2.5.2 Pointer cancellation (A). Actions are not triggered on the down-event only, so people can abort a mistaken press.
• 2.5.3 Label in name (A). A control's accessible name contains its visible label text.
• 2.5.4 Motion actuation (A). Features triggered by shaking or tilting also have a normal control and can be turned off.

Understandable

• 3.1.1 Language of page (A). The page language is set, for example <html lang="en">.
• 3.1.2 Language of parts (AA). Passages in another language are marked.
• 3.2.1 On focus (A) and 3.2.2 On input (A). Focusing a control or changing a setting does not unexpectedly change the context, for example submit a form or open a new window.
• 3.2.3 Consistent navigation (AA) and 3.2.4 Consistent identification (AA). Repeated navigation keeps the same order, and the same functions are labelled the same way.
• 3.3.1 Error identification (A). Errors are identified and described in text.
• 3.3.2 Labels or instructions (A). Fields have labels or instructions.
• 3.3.3 Error suggestion (AA). When a fix is known, the error message suggests it.
• 3.3.4 Error prevention for legal, financial and data (AA). Submissions that commit money or legal terms, or change stored data, can be reversed, checked or confirmed.

Robust

• 4.1.2 Name, role, value (A). Every custom control exposes a name and role, and its states and values can be read and set by assistive technology. Native HTML controls already do this when used as intended.
• 4.1.3 Status messages (AA). Messages such as “3 results found” or “added to cart” are announced to screen readers without moving focus.

Which items can software check?

Some items, such as missing alt attributes, text contrast, a missing lang attribute and missing form labels, can be partly or fully tested by software. Many others, such as whether alt text is accurate, whether focus order makes sense, whether captions are right or whether a task can be done with a keyboard, need a person. Read what automated testing can and cannot catch.

Frequently asked questions

What is new in WCAG 2.2 compared with 2.1?

The W3C lists nine new success criteria. Six are Level A or AA: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). 4.1.1 Parsing was removed.

Do I need to meet Level AAA?

The W3C notes that it does not recommend requiring Level AAA conformance as a general policy for entire sites, because some AAA criteria cannot be met for some content. Most requirements that reference WCAG point to Level AA.

Does passing this checklist mean my page conforms?

No. Conformance covers full pages and complete processes and must be judged by testing with people and assistive technology. A checklist is a planning aid, not a certificate.

Sources

We checked these pages when writing this guide.

• WCAG 2.2, W3C Recommendation
• What's New in WCAG 2.2, W3C WAI

More guides

• Accessibility for nonprofits
• Accessibility barriers for small businesses
• Fixing common axe issues
• What automated testing can and cannot catch

This guide is general information, not legal advice, and Allie reports do not certify conformance with WCAG or any law.