WCAG 2.2 AA Accessibility Readiness Guide
WCAG 2.2 AA is the technical baseline many accessibility checks, procurement expectations, and regional standards commonly reference.
This guide is for general accessibility-readiness planning. It is not legal advice, a certification, or a substitute for manual accessibility and compliance review.
Who this may apply to
- Public websites and web applications
- Design systems and reusable components
- Content, forms, navigation, and mobile experiences
- Teams preparing for manual accessibility review
WCAG relationship
WCAG is the shared technical reference behind many regional accessibility requirements. It provides testable criteria, while local rules define who may be covered and what formal process may apply.
What the readiness check can surface
- Missing image alternatives and weak accessible names
- Heading-order and landmark signals that affect page structure
- Form-label, error-message, and input-purpose readiness signals
- Keyboard, focus, and skip-link readiness issues
- Contrast and mobile interaction signals that need attention
What still needs manual review
- Keyboard journeys across complete user tasks
- Screen reader experience and announcement quality
- Content meaning, plain-language quality, and alternative formats
- Context-specific interpretation of WCAG success criteria
Common readiness issues
Interactive controls without clear accessible names
Forms that lack labels, instructions, or error recovery support
Content hierarchy that makes page structure hard to follow
Insufficient contrast on text, controls, or focus indicators
Mobile controls that are difficult to activate reliably
Official sources
FAQ
Is WCAG 2.2 AA a law?
WCAG is a technical standard. Many laws, policies, and procurement rules reference or align with it, but legal scope and process depend on the region and organization.
Can automated checks cover all WCAG criteria?
No. Automated checks can surface useful readiness signals, but many WCAG criteria require human judgment, assistive-technology review, and task-based testing.
Why start with WCAG for readiness planning?
WCAG gives teams a common technical vocabulary for finding barriers, prioritizing fixes, and preparing for deeper manual review.
How does the Website Accessibility Readiness Check use WCAG?
It looks for practical WCAG-aligned signals across structure, forms, navigation, contrast, and mobile interaction so teams can identify likely priorities before manual review.
Related standards
Start with the Website Accessibility Readiness Check
Scan a public URL to find practical accessibility, usability, forms, navigation, and mobile interaction signals before planning manual review.
Run the Website Accessibility Readiness Check