WCAG 2.2 success criteria index
Pick a success criterion to see which component patterns on this site are commonly affected by it — useful for citing findings directly in an audit report.
- 1.1.1Non-text ContentLevel AWCAG 2.0
Icons, images, and controls without visible text have a text alternative.
No mapped component pages yet.
Read the Understanding doc - 1.2.1Audio-only and Video-only (Prerecorded)Level AWCAG 2.0
Prerecorded audio-only has a transcript; prerecorded video-only has a description or transcript.
Read the Understanding doc - 1.2.2Captions (Prerecorded)Level AWCAG 2.0
Synchronized captions are provided for prerecorded video that has an audio track.
Read the Understanding doc - 1.2.3Audio Description or Media Alternative (Prerecorded)Level AWCAG 2.0
Prerecorded video provides audio description of the visuals, or a full text alternative for the media.
Read the Understanding doc - 1.2.5Audio Description (Prerecorded)Level AAWCAG 2.0
Prerecorded video provides audio description of important visual information not conveyed by the audio.
Read the Understanding doc - 1.3.1Info and RelationshipsLevel AWCAG 2.0
Structure and relationships conveyed visually are also programmatically determinable.
AccordionBreadcrumbCheckbox (incl. tri-state)ComboboxLink vs. ButtonListbox (single & multi-select)NavigationRadio GroupSwitchTableGrid (interactive data grid)Read the Understanding doc - 1.3.5Identify Input PurposeLevel AAWCAG 2.1
Form fields collecting common user info use correct autocomplete attributes.
Read the Understanding doc - 1.4.1Use of ColorLevel AWCAG 2.0
Color is not the only visual means of conveying information or state.
No mapped component pages yet.
Read the Understanding doc - 1.4.2Audio ControlLevel AWCAG 2.0
Audio that plays automatically for more than 3 seconds can be paused, stopped, or muted independently.
Read the Understanding doc - 1.4.3Contrast (Minimum)Level AAWCAG 2.0
Text has a contrast ratio of at least 4.5:1 (3:1 for large text).
No mapped component pages yet.
Read the Understanding doc - 1.4.4Resize TextLevel AAWCAG 2.0
Text can be resized up to 200% without loss of content or functionality.
No mapped component pages yet.
Read the Understanding doc - 1.4.10ReflowLevel AAWCAG 2.1
Content reflows to a single column at 320 CSS px wide without two-dimensional scrolling.
No mapped component pages yet.
Read the Understanding doc - 1.4.11Non-text ContrastLevel AAWCAG 2.1
UI component boundaries/states and graphical objects have 3:1 contrast against adjacent colors.
No mapped component pages yet.
Read the Understanding doc - 1.4.12Text SpacingLevel AAWCAG 2.1
No loss of content when users override line, paragraph, letter, and word spacing.
No mapped component pages yet.
Read the Understanding doc - 1.4.13Content on Hover or FocusLevel AAWCAG 2.1
Content revealed on hover/focus (e.g. tooltips) is dismissible, hoverable, and persistent.
Read the Understanding doc - 2.1.1KeyboardLevel AWCAG 2.0
All functionality is operable through a keyboard interface with no specific timing.
AccordionAlert & Alert DialogButton (incl. toggle button)CarouselCheckbox (incl. tri-state)ComboboxDialog (Modal)Disclosure (Show/Hide)Link vs. ButtonListbox (single & multi-select)Menu & Menu ButtonSkip LinkRadio GroupSliderSwitchTableGrid (interactive data grid)TabsTooltipPaginationDate PickerVideo PlayerRead the Understanding doc - 2.1.2No Keyboard TrapLevel AWCAG 2.0
Keyboard focus can always be moved away from a component using standard navigation.
Read the Understanding doc - 2.2.2Pause, Stop, HideLevel AWCAG 2.0
Moving, blinking, or auto-updating content lasting more than 5 seconds can be paused, stopped, or hidden.
Read the Understanding doc - 2.4.1Bypass BlocksLevel AWCAG 2.0
A mechanism (such as a skip link or landmarks) is available to bypass blocks of content repeated on multiple pages.
Read the Understanding doc - 2.4.2Page TitledLevel AWCAG 2.0
Each page has a title that describes its topic or purpose.
No mapped component pages yet.
Read the Understanding doc - 2.4.3Focus OrderLevel AWCAG 2.0
Focusable components receive focus in an order that preserves meaning and operability.
Alert & Alert DialogBreadcrumbCarouselComboboxDialog (Modal)Menu & Menu ButtonNavigationSkip LinkGrid (interactive data grid)TabsDate PickerRead the Understanding doc - 2.4.4Link Purpose (In Context)Level AWCAG 2.0
The purpose of each link is clear from its text, or from its text plus programmatic context.
No mapped component pages yet.
Read the Understanding doc - 2.4.6Headings and LabelsLevel AAWCAG 2.0
Headings and labels describe topic or purpose.
Read the Understanding doc - 2.4.7Focus VisibleLevel AAWCAG 2.0
Any keyboard-operable UI has a visible focus indicator.
Read the Understanding doc - 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.2
The focused element is not entirely hidden by author-created content (e.g. sticky headers).
No mapped component pages yet.
Read the Understanding doc - 2.4.13Focus AppearanceLevel AAAWCAG 2.2
The focus indicator is large enough and has sufficient contrast against adjacent colors.
No mapped component pages yet.
Read the Understanding doc - 2.5.1Pointer GesturesLevel AWCAG 2.1
Path-based or multipoint gestures have a single-pointer alternative.
No mapped component pages yet.
Read the Understanding doc - 2.5.2Pointer CancellationLevel AWCAG 2.1
Functions triggered by a single pointer can be aborted or undone before completion.
No mapped component pages yet.
Read the Understanding doc - 2.5.3Label in NameLevel AWCAG 2.1
The accessible name contains the visible text label.
Read the Understanding doc - 2.5.7Dragging MovementsLevel AAWCAG 2.2
Functionality using a dragging movement has a single-pointer alternative (e.g. slider with buttons).
Read the Understanding doc - 2.5.8Target Size (Minimum)Level AAWCAG 2.2
Pointer targets are at least 24x24 CSS pixels, unless spaced, inline, or essential.
Read the Understanding doc - 3.1.1Language of PageLevel AWCAG 2.0
The default human language of the page is programmatically set (e.g. <html lang>).
No mapped component pages yet.
Read the Understanding doc - 3.2.1On FocusLevel AWCAG 2.0
Receiving focus does not trigger an unexpected change of context.
Read the Understanding doc - 3.2.2On InputLevel AWCAG 2.0
Changing a setting does not automatically trigger an unexpected change of context.
No mapped component pages yet.
Read the Understanding doc - 3.3.1Error IdentificationLevel AWCAG 2.0
Input errors are identified and described to the user in text.
Read the Understanding doc - 3.3.2Labels or InstructionsLevel AWCAG 2.0
Labels or instructions are provided when content requires user input.
Read the Understanding doc - 3.3.3Error SuggestionLevel AAWCAG 2.0
If an input error is detected and suggestions are known, they are provided to the user.
Read the Understanding doc - 3.3.7Redundant EntryLevel AWCAG 2.2
Information previously entered is auto-populated or available for the user to select.
Read the Understanding doc - 4.1.2Name, Role, ValueLevel AWCAG 2.0
For all UI components, name, role, and value are programmatically determinable; states and changes are announced.
AccordionAlert & Alert DialogBreadcrumbButton (incl. toggle button)CarouselCheckbox (incl. tri-state)ComboboxDialog (Modal)Disclosure (Show/Hide)Link vs. ButtonListbox (single & multi-select)Menu & Menu ButtonNavigationRadio GroupSliderSwitchTableGrid (interactive data grid)TabsTooltipForm patternsPaginationDate PickerVideo PlayerRead the Understanding doc - 4.1.3Status MessagesLevel AAWCAG 2.1
Status messages can be programmatically determined via role or properties (e.g. aria-live) without receiving focus.
Read the Understanding doc