What belongs in a WCAG 2.2 AA checklist?

Level AA includes every applicable Level A criterion as well as the AA criteria. It applies to complete pages and complete processes, so checking one component or one step isn't enough.

Where can automated checks help a WCAG review?

  • Missing text alternatives

    An absent image alternative is a useful automated clue. A person still needs to judge what the image communicates.

  • Markup for controls and language

    Tools can flag some naming or language-markup problems. A reviewer needs to judge whether the information is accurate and useful.

W3C's tool-selection guidance explains that automated results require human judgment; a passing result isn't a conformance decision.

WCAG 2.2 A and AA criteria and what to review

CriterionWhat it asks forHow to check itFull requirement
1.1.1 Non-text ContentProvide alternatives for non-text information, with the criterion's exceptions for decoration and other uses.Inspect markup and judge the equivalent meaning.W3C's explanation
1.2.1 Audio-only and Video-only (Prerecorded)Provide equivalent information for prerecorded audio-only or video-only content, subject to the stated text-alternative exception.Review the alternative against the recording.W3C's explanation
1.2.2 Captions (Prerecorded)Caption prerecorded audio in synchronized media, except clearly labeled media alternatives to text.Check caption coverage and accuracy.W3C's explanation
1.2.3 Audio Description or Media Alternative (Prerecorded)Provide an audio description or a full media alternative for prerecorded synchronized video, allowing the stated exception.Compare the alternative with the video.W3C's explanation
1.2.4 Captions (Live)Caption live audio in synchronized media.A person reviews coverage and accuracy.W3C's explanation
1.2.5 Audio Description (Prerecorded)Describe important video information the existing audio doesn't convey.Watch the prerecorded video with its audio description.W3C's explanation
1.3.1 Info and RelationshipsExpose the structure and relationships conveyed visually through code or text.Inspect semantics and the resulting reading experience.W3C's explanation
1.3.2 Meaningful SequenceExpose a correct reading order when sequence changes the meaning.Read the content in its programmatic order.W3C's explanation
1.3.3 Sensory CharacteristicsGive instructions that don't depend only on appearance, position or sound.Read instructions without those sensory cues.W3C's explanation
1.3.4 OrientationAllow portrait and landscape unless one orientation is essential.Try both orientations.W3C's explanation
1.3.5 Identify Input PurposeIdentify the purpose of supported fields collecting common personal information.Markup can help identify missing input-purpose information; review applicability.W3C's explanation
1.4.1 Use of ColorCommunicate visual information with something besides color alone.Review errors, states and other visual signals.W3C's explanation
1.4.2 Audio ControlLet users stop, pause or independently adjust audio that autoplays for more than three seconds.Try the controls for autoplaying audio.W3C's explanation
1.4.3 Contrast (Minimum)Use at least 4.5:1 text contrast, or 3:1 for large text, subject to the criterion's exceptions.Measure the real text and background colors, then review context.W3C's explanation
1.4.4 Resize TextKeep text usable at 200% resizing, except captions and text images.Inspect the resized layout and controls.W3C's explanation
1.4.5 Images of TextUse real text where possible, allowing the criterion's customization and essential-presentation exceptions.Review images that contain words.W3C's explanation
1.4.10 ReflowKeep ordinary vertically scrolling content usable at 320 CSS pixels without sideways scrolling. Two-dimensional content has exceptions.Review the layout; the criterion also specifies a height for horizontally scrolling content.W3C's explanation
1.4.11 Non-text ContrastGive required control and graphic details at least 3:1 contrast with adjacent colors, allowing the stated exceptions.Measure relevant colors and identify which details carry meaning.W3C's explanation
1.4.12 Text SpacingKeep content usable when users apply the criterion's line, paragraph, letter and word spacing.Apply the specified overrides and inspect for lost content.W3C's explanation
1.4.13 Content on Hover or FocusMake added hover or focus content dismissible, hoverable and persistent where required.Try the popup with pointer and keyboard; check the exceptions.W3C's explanation
2.1.1 KeyboardSupport keyboard operation without precise keystroke timing, except inherently path-dependent functions.Complete the available actions using a keyboard.W3C's explanation
2.1.2 No Keyboard TrapLet keyboard users leave a component and explain any nonstandard exit method.Enter and leave each interactive component.W3C's explanation
2.1.4 Character Key ShortcutsAllow single-character shortcuts to be turned off, remapped to include a key such as Ctrl or Alt, or limited to the focused component.Review shortcut settings and activation.W3C's explanation
2.2.1 Timing AdjustableLet users turn off, adjust or extend content time limits unless a stated exception applies.Test each time limit against the full criterion.W3C's explanation
2.2.2 Pause, Stop, HideProvide the required controls for automatic motion and updates, allowing essential-activity exceptions.Inspect moving content and automatic updates.W3C's explanation
2.3.1 Three Flashes or Below ThresholdAvoid more than three flashes per second unless they remain below the specified thresholds.Evaluate flashing content against the defined thresholds.W3C's explanation
2.4.1 Bypass BlocksProvide a way past content blocks repeated across pages.Verify the available bypass mechanism works.W3C's explanation
2.4.2 Page TitledGive each page a title that identifies its topic or purpose.Compare page titles with their actual content.W3C's explanation
2.4.3 Focus OrderPreserve meaning and operation in sequential keyboard focus order.Follow focus through the task.W3C's explanation
2.4.4 Link Purpose (In Context)Make a link's purpose clear from its text or programmatically associated context, allowing generally ambiguous cases.Read each link with its available context.W3C's explanation
2.4.5 Multiple WaysOffer another way to locate pages, except pages within or resulting from a process.Review routes through the site.W3C's explanation
2.4.6 Headings and LabelsGive headings and labels words that explain their topic or purpose.Read them in context; presence alone is insufficient.W3C's explanation
2.4.7 Focus VisibleProvide a mode of operation where keyboard focus is visible.A person follows focus while operating controls.W3C's explanation
2.4.11 Focus Not Obscured (Minimum)Don't let author-created content entirely hide a control receiving keyboard focus.Inspect focused controls near sticky panels and other page content.W3C's explanation
2.5.1 Pointer GesturesOffer a single-pointer alternative to multipoint or path-based gestures unless they're essential.Try the action without the complex gesture.W3C's explanation
2.5.2 Pointer CancellationPrevent or let users cancel accidental pointer activation using the criterion's options and exceptions.Check press, release and cancellation behavior.W3C's explanation
2.5.3 Label in NameInclude the visible text label in a control's accessible name.Compare the visible and programmatic names.W3C's explanation
2.5.4 Motion ActuationOffer controls for motion-triggered actions and a way to disable motion activation, subject to the stated exceptions.Try the alternative and motion settings.W3C's explanation
2.5.7 Dragging MovementsOffer a single-pointer alternative to dragging unless an exception applies.Try the same action without dragging.W3C's explanation
2.5.8 Target Size (Minimum)Make pointer targets at least 24 by 24 CSS pixels or satisfy a stated exception, such as sufficient spacing.Measure targets and assess spacing, inline and other exceptions.W3C's explanation
3.1.1 Language of PageIdentify the page's default language programmatically.Inspect the language declaration and actual content.W3C's explanation
3.1.2 Language of PartsIdentify the language of passages that differ from surrounding content, with the stated exceptions.Language markup offers clues; a person identifies the actual language.W3C's explanation
3.2.1 On FocusKeep receiving focus from triggering a change of context.Focus each control and observe the result.W3C's explanation
3.2.2 On InputWarn before a setting change automatically triggers a change of context.Change settings and check advance warnings.W3C's explanation
3.2.3 Consistent NavigationKeep repeated navigation in the same relative order unless the user changes it.Compare navigation across pages.W3C's explanation
3.2.4 Consistent IdentificationIdentify repeated components with the same function consistently across pages.Compare the names and functions of repeated components.W3C's explanation
3.2.6 Consistent HelpKeep repeated help mechanisms in a consistent relative order unless the user changes it.Compare help placement across relevant pages.W3C's explanation
3.3.1 Error IdentificationIdentify automatically detected input errors and describe them in text.Submit invalid values and inspect the messages.W3C's explanation
3.3.2 Labels or InstructionsProvide labels or instructions for required user input.Review what each input asks the user to supply.W3C's explanation
3.3.3 Error SuggestionGive known correction suggestions for detected input errors unless doing so would undermine security or purpose.Read validation responses for recoverable errors.W3C's explanation
3.3.4 Error Prevention (Legal, Financial, Data)Make consequential submissions reversible, checked with correction or reviewable before confirmation.Examine financial, legal, stored-data and test-response submissions covered by the criterion.W3C's explanation
3.3.7 Redundant EntryReuse or offer previously supplied information within the same process unless a stated exception applies.Trace repeated data entry across the process.W3C's explanation
3.3.8 Accessible Authentication (Minimum)Avoid required memory or puzzle tests at sign-in unless assistance, an alternative or another stated exception applies.Review the complete sign-in flow, including password-manager and paste support.W3C's explanation
4.1.2 Name, Role, ValueExpose control names, roles, adjustable properties and updates to assistive technology.Inspect semantics and test control changes.W3C's explanation
4.1.3 Status MessagesLet assistive technology announce status changes without requiring focus on the message.Inspect semantics and listen to updates during real interactions.W3C's explanation

How does WCAG 2.2 AA differ from WCAG 2.1 AA?

  • WCAG 2.2 adds four AA criteria (Focus Not Obscured, Dragging Movements, Target Size and Accessible Authentication) and two at Level A, and removes 4.1.1 Parsing.

  • W3C intends a site that conforms to 2.2 to also conform to 2.1, so it meets policies that name 2.1. If a policy holds you to 2.1, you may still need to test and report 4.1.1.

Frequently asked questions

Does WCAG 2.2 AA require the AAA criteria?

No. Level AA requires the applicable Level A and AA criteria. Level AAA adds further requirements; it isn't another name for AA. W3C doesn't recommend requiring AAA for whole sites, since some content can't meet every AAA criterion.