WCAG 2.2 Checklist
A comprehensive checklist of WCAG 2.2 Level A and AA success criteria to help you achieve web accessibility compliance.
55 Criteria
Level A & AA Success Criteria
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive
1.1 Text Alternatives
All non-text content has a text alternative
1.2 Time-based Media
Alternatives for prerecorded audio-only and video-only content
Captions for all prerecorded audio content in synchronized media
Alternative or audio description for prerecorded video
Captions for all live audio content in synchronized media
Audio description for all prerecorded video content
1.3 Adaptable
Information and relationships can be programmatically determined
Correct reading sequence can be programmatically determined
Instructions don't rely solely on sensory characteristics
Content doesn't restrict view to a single display orientation
The purpose of input fields can be programmatically determined
1.4 Distinguishable
Color is not used as the only visual means of conveying information
Mechanism to pause, stop, or control audio volume
Text has a contrast ratio of at least 4.5:1
Text can be resized up to 200% without loss of functionality
Text is used instead of images of text where possible
Content can reflow without requiring scrolling in two dimensions
UI components and graphics have a contrast ratio of at least 3:1
No loss of content or functionality when adjusting text spacing
Additional content is dismissible, hoverable, and persistent
2. Operable
User interface components and navigation must be operable
2.1 Keyboard Accessible
All functionality is available from a keyboard
Keyboard focus can be moved away from any component
Single character key shortcuts can be turned off or remapped
2.2 Enough Time
Time limits can be turned off, adjusted, or extended
Moving, blinking, or auto-updating content can be controlled
2.3 Seizures and Physical Reactions
Content does not flash more than three times per second
2.4 Navigable
Mechanism to bypass repeated blocks of content
Pages have descriptive and informative titles
Focus order preserves meaning and operability
Link purpose can be determined from link text or context
More than one way to find pages in a set
Headings and labels describe topic or purpose
Keyboard focus indicator is visible
Focused component is not entirely hidden
2.5 Input Modalities
Single pointer alternative for multipoint or path-based gestures
Function can be aborted, undone, or not executed on up-event
Accessible name contains visible text label
Motion-operated functions have alternative input
Single pointer alternative for dragging
Targets are at least 24x24 CSS pixels
3. Understandable
Information and the operation of user interface must be understandable
3.1 Readable
Default human language of page can be programmatically determined
Language of each passage or phrase can be programmatically determined
3.2 Predictable
Receiving focus does not initiate a change of context
Changing a setting does not automatically cause a change of context
Navigation mechanisms are consistent across a set of pages
Components with same functionality are identified consistently
Help mechanisms appear in the same relative order
3.3 Input Assistance
Input errors are automatically detected and described
Labels or instructions provided for user input
Suggestions provided when an error is detected
Submissions are reversible, checked, or confirmed
Previously entered information is auto-populated
No cognitive function test required for login
4. Robust
Content must be robust enough that it can be interpreted by a wide variety of user agents
4.1 Compatible
UI components have accessible name, role, and state
Status messages can be programmatically determined
Recommended testing tools
Use these tools to help verify your WCAG compliance
Automated Testing
- • Compliable Radar
- • axe DevTools
- • WAVE Evaluator
- • Lighthouse
- • Pa11y
Manual Testing
- • Keyboard navigation
- • Screen reader testing
- • Color contrast analysis
- • Zoom testing (200%)
- • Mobile device testing
Screen Readers
- • NVDA (Windows)
- • JAWS (Windows)
- • VoiceOver (macOS/iOS)
- • TalkBack (Android)
- • Narrator (Windows)
Need help with WCAG compliance?
Let Compliable automatically scan and fix accessibility issues on your website. Start with a free accessibility audit.