WCAG 2.2 Success Criteria Reference Guide
Complete searchable reference for all WCAG 2.2 success criteria. Filter by conformance level (A/AA/AAA) and search by keyword.
100% client-side - your data never leaves your browser.
1.1.1All non-text content has text alternatives that serve the equivalent purpose.
1.2.1Prerecorded audio-only and video-only content has an alternative.
1.2.2Captions are provided for all prerecorded audio content in synchronized media.
1.2.3An alternative for time-based media or audio description is provided for prerecorded video.
1.2.4Captions are provided for all live audio content in synchronized media.
1.2.5Audio description is provided for all prerecorded video content.
1.2.6Sign language interpretation is provided for all prerecorded audio content.
1.3.1Information, structure, and relationships conveyed through presentation can be programmatically determined.
1.3.2When sequence matters, content can be read in the correct sequence programmatically.
1.3.3Instructions do not rely solely on sensory characteristics such as shape, color, or sound.
1.3.4Content does not restrict its view and operation to a single display orientation.
1.3.5The purpose of each input field that collects user information can be determined.
1.4.1Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
1.4.2A mechanism is available to pause, stop, or adjust audio that plays automatically.
1.4.3Text and images of text have a contrast ratio of at least 4.5:1 (3:1 for large text).
1.4.4Text can be resized up to 200% without loss of content or functionality.
1.4.5Images of text are not used unless the image is essential or customizable.
1.4.10Content can be presented without scrolling in two dimensions at 400% zoom (320px).
1.4.11UI components and graphical objects have a contrast ratio of at least 3:1.
1.4.12No loss of content when text spacing properties are overridden.
1.4.13Content that appears on hover/focus is dismissible, hoverable, and persistent.
2.1.1All functionality is operable through a keyboard interface.
2.1.2Focus can be moved away from any component using keyboard only.
2.1.4Character key shortcuts can be turned off, remapped, or only active on focus.
2.2.1Time limits can be turned off, adjusted, or extended by the user.
2.2.2Moving, blinking, scrolling, or auto-updating information can be paused or stopped.
2.3.1Content does not flash more than three times per second.
2.4.1A mechanism exists to bypass blocks of content repeated on multiple pages (skip nav).
2.4.2Web pages have titles that describe topic or purpose.
2.4.3Focus order preserves meaning and operability.
2.4.4Link purpose can be determined from the link text or its context.
2.4.5More than one way exists to locate a page within a set of pages.
2.4.6Headings and labels describe topic or purpose.
2.4.7Keyboard focus indicator is visible.
2.4.11Focus indicator is not entirely hidden by sticky content.
2.5.1Multipoint or path-based gestures have a single-pointer alternative.
2.5.2Functions can be cancelled: no down-event action, abort/undo on up event, or reversal.
2.5.3Accessible name of a component contains the visible label text.
2.5.4Functionality triggered by device motion can also be triggered by UI components.
2.5.7All drag-based operations have a single-pointer alternative.
2.5.8Target size is at least 24x24 CSS pixels (with exceptions).
3.1.1The default human language of the page can be programmatically determined.
3.1.2Language of content parts different from the default can be programmatically determined.
3.2.1Receiving focus does not initiate a change of context.
3.2.2Changing a setting does not automatically cause a change of context unless advised.
3.2.3Navigation repeated across pages is in the same relative order.
3.2.4Components with the same functionality are identified consistently.
3.3.1Input errors are identified and described to the user in text.
3.3.2Labels or instructions are provided when content requires user input.
3.3.3Error messages provide suggestions for correction when possible.
3.3.4For important submissions: content can be reversed, checked, or confirmed.
3.3.7Previously entered information is auto-populated or available for selection.
3.3.8Authentication does not require cognitive function tests (captcha exceptions exist).
4.1.1Deprecated in WCAG 2.2 - now obsolete for modern browsers.
4.1.2UI components expose name, role, and value to assistive technologies.
4.1.3Status messages can be programmatically determined through roles or properties.
Want automated scanning?
SCOUTb2 runs 25+ accessibility, performance, SEO, and security checks on any page automatically.
Install SCOUTb2 Free