WCAG Level A vs Level AA 2026 | Which Compliance Level Do You Need?
Last updated: 2026-04-07
WCAG (Web Content Accessibility Guidelines) organizes its success criteria into three conformance levels — A, AA, and AAA — with Level A representing the minimum baseline and Level AAA representing the most rigorous requirements. In practice, the overwhelming majority of legal mandates, regulatory frameworks, and industry standards target WCAG 2.1 Level AA or WCAG 2.2 Level AA as the expected compliance standard. This means that for most organizations, the real decision is not whether to pursue Level AA, but rather how to get there from wherever they currently stand — and whether a Level A baseline is a meaningful intermediate milestone or just a distraction. Understanding the specific criteria that distinguish Level A from Level AA matters both for prioritizing remediation work and for communicating compliance status accurately to legal, procurement, and executive stakeholders. This comparison breaks down what each level actually requires, the practical difference in effort to achieve each, and the legal and business implications of targeting one versus the other in 2026.
At a Glance
| Feature | WCAG Level A | WCAG Level AA |
|---|---|---|
| Number of success criteria (WCAG 2.2) | 25 criteria | 50 criteria (25 A + 25 AA) |
| Color contrast requirement | Not required at Level A | 4.5:1 for normal text, 3:1 for large text (1.4.3) |
| Captions for live audio/video | Prerecorded captions only (1.2.2) | Adds live captions (1.2.4) and audio description (1.2.5) |
| Legal / regulatory status | Below the threshold of ADA, EAA, Section 508, EN 301 549 | Meets or exceeds virtually all major global accessibility laws |
| Focus visibility | Not required at Level A | Required (2.4.7 in WCAG 2.1; stricter 2.4.11 in WCAG 2.2) |
| Text resize | Not required at Level A | 200% resize without loss of content or functionality (1.4.4) |
| Typical remediation effort | Lower — addresses the most obvious and severe barriers | Higher — requires design, development, and content changes across all AA criteria |
WCAG Level A
Pros
- Removes the most severe access barriers that completely prevent users with disabilities from perceiving or operating web content — including missing alt text, keyboard traps, and missing page titles
- Achievable as an early milestone for organizations starting from zero accessibility work, providing a structured foundation before tackling the full AA requirement
- Level A criteria are generally the highest-impact, lowest-controversy fixes — they are rarely ambiguous and represent clear technical requirements that development teams can act on immediately
- Achieving Level A demonstrates a minimum good-faith effort that may be considered in legal contexts, even though it does not satisfy most regulatory mandates on its own
Cons
- Level A alone does not satisfy any major legal standard — the ADA (as interpreted by DOJ guidance), Section 508, EN 301 549, and the European Accessibility Act all reference WCAG AA as the expected conformance level
- Many significant barriers remain at Level A: color contrast requirements (1.4.3, 1.4.11), resize text (1.4.4), and captions for live audio (1.2.4) are all AA criteria
- Communicating 'Level A compliant' to stakeholders can create false confidence — users with visual impairments, low vision, or cognitive disabilities will still encounter significant barriers
- Level A is not sufficient for public procurement in most jurisdictions and will not satisfy supplier questionnaires that reference WCAG 2.1 AA
WCAG Level AA
Pros
- Satisfies the accessibility requirements referenced by ADA DOJ guidance, Section 508, EN 301 549 (EU), the European Accessibility Act, AODA (Canada), and the UK Equality Act — a single compliance target that covers the vast majority of global regulatory frameworks
- Addresses the barriers most commonly cited in ADA and EAA complaints and lawsuits, including color contrast failures, missing captions, and inadequate focus indicators
- WCAG 2.2 AA adds four new criteria (including focus appearance and accessible authentication) that address gaps identified in 2.1, making it the most current and comprehensive baseline for 2026 compliance
- Demonstrates a credible, industry-recognized commitment to accessibility for procurement, investor ESG reporting, and partner due diligence
- Most automated testing tools, manual audit frameworks, and accessibility conformance report (ACR/VPAT) templates are built around the AA criterion set
Cons
- More criteria mean more remediation work — teams unfamiliar with accessibility may underestimate the effort required to achieve full Level AA conformance across a large site or app
- Some AA criteria (such as 1.4.4 Resize Text and 2.4.7 Focus Visible in 2.1) require design and development changes that can conflict with existing brand guidelines or component libraries
- WCAG 2.2 AA introduced criterion 2.4.11 Focus Appearance (minimum) which requires visible focus indicators meeting specific size and contrast ratios — often a design system overhaul for teams with minimal or invisible focus styles
- Full AA conformance does not guarantee a good experience for all users with disabilities — AAA criteria and usability best practices beyond WCAG exist and should still be considered
Our Verdict
Level AA is the correct and essentially universal compliance target for any organization operating under ADA, European Accessibility Act, Section 508, or equivalent regulation — and that now covers virtually all public-facing digital products in the US, EU, UK, and Canada. Level A should be understood as an incomplete baseline, not a final destination: it resolves the most critical barriers but leaves significant gaps that will still expose organizations to legal risk and user harm. Teams with significant accessibility debt should use Level A as an internal progress milestone, but communicate compliance status only once they have achieved full WCAG 2.1 or 2.2 AA conformance and have the audit documentation to support that claim.
Further Reading
Other Comparisons
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.