Complete WCAG 2.2 Checklist for 2026: 35 Points to Check
This checklist covers 35 critical WCAG accessibility criteria across 5 categories: Perceivable (10 checks), Operable (10 checks), Understandable (8 checks), Robust (3 checks), and Voice & AI (4 checks). Use it alongside AnveVoice's free accessibility checker at /checker for maximum coverage. The ADA Title II deadline requires WCAG 2.1 AA compliance by April 24, 2026.
Category 1: Perceivable (10 Checks)
Content must be presentable in ways all users can perceive.
- 1.1.1 Non-text Content: All images have meaningful alt text; decorative images use alt="" or role="presentation"
- 1.2.1 Audio/Video Alternatives: Pre-recorded audio has transcripts; video has captions or audio description
- 1.2.2 Captions (Prerecorded): All pre-recorded video content has synchronized captions
- 1.3.1 Info and Relationships: Semantic HTML used for headings, lists, tables, landmarks
- 1.3.2 Meaningful Sequence: Reading order in DOM matches visual presentation
- 1.3.4 Orientation: Content not restricted to a single display orientation
- 1.4.1 Use of Color: Color is not the only means of conveying information
- 1.4.3 Contrast (Minimum): Text has 4.5:1 contrast ratio; large text has 3:1
- 1.4.4 Resize Text: Text resizable up to 200% without loss of content
- 1.4.11 Non-text Contrast: UI components and graphical objects have 3:1 contrast
Category 2: Operable (10 Checks)
All interface components and navigation must be operable by all users.
- 2.1.1 Keyboard: All functionality operable via keyboard; no keyboard traps
- 2.1.2 No Keyboard Trap: Focus can be moved away from every component
- 2.2.1 Timing Adjustable: Time limits can be turned off, adjusted, or extended
- 2.3.1 Three Flashes: No content flashes more than 3 times per second
- 2.4.1 Bypass Blocks: Skip-to-content link available
- 2.4.2 Page Titled: Every page has a descriptive, unique title
- 2.4.3 Focus Order: Tab order follows a logical, meaningful sequence
- 2.4.6 Headings and Labels: Headings and labels describe topic or purpose
- 2.4.7 Focus Visible: Keyboard focus indicator clearly visible
- 2.5.1 Pointer Gestures: Multipoint gestures have single-pointer alternatives
Category 3: Understandable (8 Checks)
Content and interface operation must be understandable.
- 3.1.1 Language of Page: HTML lang attribute set correctly
- 3.1.2 Language of Parts: Language changes marked with lang attribute
- 3.2.1 On Focus: No unexpected context changes on focus
- 3.2.2 On Input: No unexpected context changes on input
- 3.2.3 Consistent Navigation: Navigation in same relative order across pages
- 3.3.1 Error Identification: Input errors described in text
- 3.3.2 Labels or Instructions: Labels provided for user input
- 3.3.3 Error Suggestion: Suggestions for fixing errors provided
Category 4: Robust (3 Checks)
Content must work with assistive technologies.
- 4.1.1 Parsing: HTML validates without significant errors; no duplicate IDs
- 4.1.2 Name, Role, Value: All UI components have accessible names and ARIA roles
- 4.1.3 Status Messages: Status messages use ARIA live regions
Category 5: Voice & AI (4 Checks)
Emerging accessibility criteria for voice and AI technologies.
- Voice Navigation: Users can navigate site using voice commands
- Voice Form Completion: Users can fill out and submit forms using voice
- Multilingual Voice: Voice interface supports multiple languages
- AI Content Explanation: AI can explain page content and answer questions
Frequently Asked Questions
What is WCAG 2.2 and how does it differ from WCAG 2.1?
WCAG 2.2 adds 9 new success criteria to WCAG 2.1 including Focus Not Obscured, Dragging Movements, Target Size Minimum, Consistent Help, and Accessible Authentication. The ADA Title II rule requires WCAG 2.1 AA, but meeting 2.2 provides better accessibility and future-proofs compliance.
How many WCAG 2.1 AA criteria must I meet?
WCAG 2.1 Level AA includes 50 success criteria: all 30 Level A criteria plus 20 Level AA criteria. Our checklist covers 35 of the most critical and commonly-failed points across 5 categories.
Can automated tools check all WCAG criteria?
No. Automated tools typically detect 30-40% of WCAG violations. Issues like meaningful alt text quality, logical reading order, and content understandability require manual testing. Use automated scans as a starting point, then supplement with manual and screen reader testing.
What are the most commonly failed WCAG criteria?
Based on 2025 lawsuit data: missing alt text (1.1.1, 58%), low color contrast (1.4.3, 52%), missing form labels (1.3.1, 47%), keyboard inaccessibility (2.1.1, 41%), and missing document language (3.1.1, 38%).
How does voice AI relate to WCAG compliance?
Voice AI addresses multiple WCAG criteria: alternative input modalities (2.5), content accessibility (1.1, 1.3), error prevention (3.3), and consistent help (3.2.6). AnveVoice provides a conversational interface for navigation, forms, and content access.
Automate Your Accessibility Testing
AnveVoice provides a free accessibility checker testing all 35 criteria above, plus voice AI that addresses the Voice & AI category. Check your site in 2 minutes at anvevoice.app/checker. Voice AI plans from $39/month.