Complete WCAG 2.2 Checklist for 2026: 35 Points to Check

Why This Checklist Matters

The ADA Title II rule requires WCAG 2.1 AA conformance by April 2026; this 35-point checklist covers all critical criteria across five categories. The ADA Title II final rule requires WCAG 2.1 Level AA conformance by April 24, 2026 for state and local governments serving 50,000+ people. WCAG 2.2 (published October 2023) adds 9 new criteria that strengthen protections — meeting 2.2 ensures you exceed the minimum requirement and stay ahead of future regulatory updates. This checklist covers 35 of the most critical criteria across five categories. Each item maps to a specific WCAG success criterion. Use it alongside our automated accessibility checker for maximum coverage. The fifth category — Voice & AI — goes beyond traditional WCAG criteria to cover emerging accessibility technologies. While not yet mandated by regulation, voice accessibility provides a significant usability improvement and demonstrates accessibility commitment beyond minimum compliance.

Perceivable (10 checks)

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; pre-recorded 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; visual structure matches code structure 1.3.2 Meaningful Sequence Reading order in the DOM matches the visual presentation order 1.3.4 Orientation Content not restricted to a single display orientation (portrait/landscape) 1.4.1 Use of Color Color is not the only means of conveying information (links, errors, required fields) 1.4.3 Contrast (Minimum) Text has 4.5:1 contrast ratio; large text has 3:1 contrast ratio 1.4.4 Resize Text Text can be resized up to 200% without loss of content or functionality 1.4.11 Non-text Contrast UI components and graphical objects have 3:1 contrast against adjacent colors

Operable (10 checks)

2.1.1 Keyboard All functionality operable via keyboard; no keyboard traps 2.1.2 No Keyboard Trap Keyboard focus can be moved away from every component using standard navigation keys 2.2.1 Timing Adjustable Time limits can be turned off, adjusted, or extended (20-second minimum warning) 2.3.1 Three Flashes No content flashes more than 3 times per second 2.4.1 Bypass Blocks Skip-to-content link or other mechanism to bypass repeated navigation 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 is clearly visible on all interactive elements 2.5.1 Pointer Gestures Multipoint/path-based gestures have single-pointer alternatives

Understandable (8 checks)

3.1.1 Language of Page HTML lang attribute set to correct language code 3.1.2 Language of Parts Language changes within content are marked with lang attribute 3.2.1 On Focus No unexpected context changes when elements receive focus 3.2.2 On Input No unexpected context changes when users change form field values 3.2.3 Consistent Navigation Navigation mechanisms appear in the same relative order across pages 3.3.1 Error Identification Input errors are detected and described to the user in text 3.3.2 Labels or Instructions Labels or instructions provided for user input fields 3.3.3 Error Suggestion Suggestions for fixing errors provided when possible

Robust (3 checks)

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 set correctly 4.1.3 Status Messages Status messages use ARIA live regions so screen readers announce them

Voice & AI (4 checks)

Voice Voice Navigation Available Users can navigate the site using voice commands as alternative to keyboard/mouse Voice Voice Form Completion Users can fill out and submit forms using voice input Voice Multilingual Voice Support Voice interface supports multiple languages for diverse user populations AI AI Content Explanation AI assistant can explain page content, describe images, and answer questions about content Add voice AI to your website in 10 minutes

• Try AnveVoice Free
• • 50K tokens free, no card
• • No credit card required
• • One-line embed

Automate Your Accessibility Testing

Automated WCAG testing tools catch only part of the issues instantly; combine them with manual testing, and consider voice AI as an extra layer. Manual checking is thorough but time-consuming. Our free accessibility checker at /checker automates testing for 35 criteria — the same ones in this checklist — and provides specific remediation guidance for each failed check. For ongoing accessibility, AnveVoice provides voice AI that serves as a built-in accessibility layer. Users can navigate your site, fill forms, and access content through natural voice commands — directly addressing the Voice & AI criteria above. AnveVoice Pricing:

• Free: Accessibility checker + 50K tokens
• Growth ($39/mo): 2M tokens + 5 bots, with DOM actions and 50+ languages
• Scale ($129/mo): 8M tokens + unlimited bots

Frequently Asked Questions

Answers about WCAG 2.2 differences, compliance criteria count, automated testing limits, audit frequency, and voice AI accessibility benefits.

• • 50K tokens free, no card
• • No credit card required
• • One-line embed