All 87 WCAG 2.2 Success Criteria
Complete reference guide organized by the four POUR principles. Each criterion is tagged with our scanner's detection coverage — we publish exactly what's automated, what needs assisted review, and what requires manual audit.
Beyond WCAG 2.2 A+AA, our scanner runs 90+ additional checks covering ARIA validity, best practices, and experimental criteria — issues that don't map to a single success criterion but still affect users.
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
1.1 Text Alternatives
Provide text alternatives for any non-text content.
Non-text Content
All non-text content has a text alternative that serves the equivalent purpose.
1.2 Time-based Media
Provide alternatives for time-based media.
Audio-only and Video-only (Prerecorded)
For prerecorded audio-only and video-only media, provide an alternative.
Captions (Prerecorded)
Captions are provided for all prerecorded audio content in synchronized media.
Audio Description or Media Alternative (Prerecorded)
An alternative for time-based media or audio description is provided for prerecorded video.
Captions (Live)
Captions are provided for all live audio content in synchronized media.
Audio Description (Prerecorded)
Audio description is provided for all prerecorded video content in synchronized media.
Sign Language (Prerecorded)
Sign language interpretation is provided for all prerecorded audio content.
Extended Audio Description (Prerecorded)
Where pauses in foreground audio are insufficient, extended audio description is provided.
Media Alternative (Prerecorded)
An alternative for time-based media is provided for all prerecorded synchronized media.
Audio-only (Live)
An alternative that presents equivalent information is provided for live audio-only content.
1.3 Adaptable
Create content that can be presented in different ways without losing information or structure.
Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined.
Meaningful Sequence
When the sequence affects meaning, a correct reading sequence can be programmatically determined.
Sensory Characteristics
Instructions don't rely solely on sensory characteristics like shape, size, visual location, orientation, or sound.
Orientation
Content does not restrict its view and operation to a single display orientation.
Identify Input Purpose
The purpose of input fields that collect user information can be programmatically determined.
Identify Purpose
The purpose of user interface components, icons, and regions can be programmatically determined.
1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
Use of Color
Color is not used as the only visual means of conveying information.
Audio Control
If audio plays automatically for more than 3 seconds, a mechanism is available to pause or stop it.
Contrast (Minimum)
Text and images of text have a contrast ratio of at least 4.5:1.
Resize Text
Text can be resized up to 200% without loss of content or functionality.
Images of Text
Images of text are only used for decoration or where essential.
Contrast (Enhanced)
Text and images of text have a contrast ratio of at least 7:1.
Low or No Background Audio
Prerecorded audio content has no or low background sounds.
Visual Presentation
For blocks of text, a mechanism is available to achieve specific visual presentation.
Images of Text (No Exception)
Images of text are only used for pure decoration or where essential.
Reflow
Content can be presented without loss of information or functionality at 320 CSS pixels width.
Non-text Contrast
User interface components and graphical objects have a contrast ratio of at least 3:1.
Text Spacing
No loss of content or functionality occurs when text spacing is adjusted.
Content on Hover or Focus
Additional content triggered by hover or focus can be dismissed, hovered over, and is persistent.
2. Operable
User interface components and navigation must be operable.
2.1 Keyboard Accessible
Make all functionality available from a keyboard.
Keyboard
All functionality is available using only the keyboard.
No Keyboard Trap
Keyboard focus can be moved away from any component using only a keyboard interface.
Keyboard (No Exception)
All functionality is available using only the keyboard with no exceptions.
Character Key Shortcuts
If keyboard shortcuts use only character keys, they can be turned off, remapped, or are only active on focus.
2.2 Enough Time
Provide users enough time to read and use content.
Timing Adjustable
Time limits can be turned off, adjusted, or extended.
Pause, Stop, Hide
Moving, blinking, scrolling, or auto-updating information can be paused, stopped, or hidden.
No Timing
Timing is not an essential part of the event or activity.
Interruptions
Interruptions can be postponed or suppressed by the user.
Re-authenticating
When an authenticated session expires, the user can continue without loss of data.
Timeouts
Users are warned of the duration of any user inactivity that could cause data loss.
2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
Three Flashes or Below Threshold
Content does not contain anything that flashes more than three times per second.
Three Flashes
Content does not contain anything that flashes more than three times per second.
Animation from Interactions
Motion animation triggered by interaction can be disabled unless essential.
2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
Bypass Blocks
A mechanism is available to bypass blocks of content that are repeated on multiple pages.
Page Titled
Web pages have titles that describe topic or purpose.
Focus Order
Components receive focus in an order that preserves meaning and operability.
Link Purpose (In Context)
The purpose of each link can be determined from the link text alone or from the link text together with its context.
Multiple Ways
More than one way is available to locate a web page within a set of pages.
Headings and Labels
Headings and labels describe topic or purpose.
Focus Visible
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Location
Information about the user's location within a set of pages is available.
Link Purpose (Link Only)
A mechanism is available to allow the purpose of each link to be identified from link text alone.
Section Headings
Section headings are used to organize the content.
Focus Not Obscured (Minimum)
When a component receives keyboard focus, it is not entirely hidden by author-created content.
Focus Not Obscured (Enhanced)
When a component receives keyboard focus, no part of it is hidden by author-created content.
Focus Appearance
The keyboard focus indicator meets minimum size and contrast requirements.
2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
Pointer Gestures
All functionality that uses multipoint or path-based gestures can also be operated with a single pointer.
Pointer Cancellation
For functionality operated using a single pointer, specific conditions about down-event and completion apply.
Label in Name
For user interface components with labels that include text or images of text, the name contains the text presented visually.
Motion Actuation
Functionality that can be operated by device motion can also be operated by user interface components.
Target Size (Enhanced)
The size of the target for pointer inputs is at least 44 by 44 CSS pixels.
Concurrent Input Mechanisms
Content does not restrict use of input modalities available on a platform.
Dragging Movements
All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
Target Size (Minimum)
The size of the target for pointer inputs is at least 24 by 24 CSS pixels.
3. Understandable
Information and the operation of user interface must be understandable.
3.1 Readable
Make text content readable and understandable.
Language of Page
The default human language of each page can be programmatically determined.
Language of Parts
The human language of each passage or phrase can be programmatically determined.
Unusual Words
A mechanism is available for identifying specific definitions of words or phrases used in an unusual way.
Abbreviations
A mechanism for identifying the expanded form or meaning of abbreviations is available.
Reading Level
When text requires reading ability more advanced than lower secondary education, supplemental content is available.
Pronunciation
A mechanism is available for identifying specific pronunciation of words where meaning is ambiguous.
3.2 Predictable
Make Web pages appear and operate in predictable ways.
On Focus
When any component receives focus, it does not initiate a change of context.
On Input
Changing the setting of any user interface component does not automatically cause a change of context.
Consistent Navigation
Navigational mechanisms that are repeated on multiple pages occur in the same relative order.
Consistent Identification
Components that have the same functionality are identified consistently.
Change on Request
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Consistent Help
If a page contains help mechanisms, they are in the same relative order across pages.
3.3 Input Assistance
Help users avoid and correct mistakes.
Error Identification
If an input error is automatically detected, the item that is in error is identified and described in text.
Labels or Instructions
Labels or instructions are provided when content requires user input.
Error Suggestion
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided.
Error Prevention (Legal, Financial, Data)
For pages causing legal commitments or financial transactions, submissions are reversible, checked, or confirmed.
Help
Context-sensitive help is available.
Error Prevention (All)
For pages requiring user information submission, submissions are reversible, checked, or confirmed.
Redundant Entry
Information previously entered by or provided to the user is auto-populated or available for selection.
Accessible Authentication (Minimum)
A cognitive function test is not required for any step in an authentication process.
Accessible Authentication (Enhanced)
A cognitive function test is not required for any step in an authentication process, with no exceptions.
4. Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
Parsing
In content implemented using markup languages, elements have complete start and end tags (obsolete in WCAG 2.2).
Name, Role, Value
For all user interface components, the name and role can be programmatically determined.
Status Messages
Status messages can be programmatically determined through role or properties.
90+ additional checks our scanner catches
WCAG 2.2 A+AA covers the standard. Real users hit issues that don't map to a single success criterion. Our scanner runs additional rules across these categories:
ARIA Validity
Required attributes, allowed roles, parent/child relationships, valid attribute values, deprecated roles.
Best Practices
Landmark uniqueness, page heading-one, region-bounded content, skip-link presence, scrollable region focusability.
Visual & Structural
Tabindex misuse, table headers, list semantics, definition-list structure, blink/marquee deprecation.
Forms & Inputs
Multiple labels, autocomplete validity, button names, select names, input image alt text, frame titles.
Experimental
Emerging WCAG 3.0 candidate rules, evolving best practices flagged before they hit the standard.
Custom AllAccessible Rules
Remediation hooks specific to our widget — detection paired with one-click fixes the open standard doesn't define.
Total scanner checks: 38 WCAG-mapped + 90+ supplementary rules per scan.
Address All 87 Success Criteria
AllAccessible's AI-powered widget helps cover every WCAG 2.2 success criterion through automated remediation and detection. Strengthen accessibility in minutes, not months.