Introduction
If you've searched for "AAA compliance," you've probably run into a wall of conflicting information. WCAG levels describe technical accessibility conformance; laws like the ADA create legal obligations. Related, but not the same thing.
That distinction matters if you ship B2B software, enterprise SaaS, or public-facing digital services in the US. Get it wrong and you either overinvest in criteria that don't apply, or underinvest and face procurement delays and legal exposure.
This article breaks down what WCAG actually means, how Levels A, AA, and AAA differ, why AA has become the default target for most organizations, and when select AAA criteria are worth applying.
TL;DR
- WCAG has three conformance levels (A, AA, AAA); each higher level includes everything below it.
- Level A covers foundational barriers; AA broader usability; AAA the most specialized criteria.
- Most organizations should target Level AA, based on applicable laws, procurement rules, and their specific users.
- WCAG is not itself a US law; meeting a level does not prove legal compliance—consult qualified counsel.
What Is WCAG and Why Is It Important?
WCAG stands for Web Content Accessibility Guidelines, developed by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative. It sets testable success criteria for making digital content usable by people with disabilities — criteria you can check pass or fail against.
Every WCAG criterion maps back to four principles, known as POUR:
- Perceivable — Content must be presented in ways users can perceive, such as text alternatives for images
- Operable — Interfaces must work via keyboard, not only mouse or touch
- Understandable — Forms, navigation, and language must behave predictably
- Robust — Content must work reliably with assistive technologies like screen readers
Version vs. Conformance Level
These two terms get mixed up constantly. The version identifies the edition of the guidelines — WCAG 2.0, 2.1, or 2.2. The conformance level (A, AA, AAA) identifies how demanding an individual success criterion is. WCAG 2.2 is the current W3C Recommendation (December 2024). It added new success criteria and kept the A/AA/AAA structure introduced in WCAG 2.0.
WCAG conformance applies to a defined product, page set, or content scope at a specific point in time. It does not mean your entire company or every product you've shipped is "accessible."
How WCAG Connects to US Law
The Department of Justice's 2024 ADA Title II final rule specifies WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. Section 508, which covers federal agency technology, incorporates WCAG 2.0 Level AA for web and non-web electronic content.
Private businesses fall under ADA Title III, and DOJ guidance does not designate WCAG as an official Title III technical standard. Courts often reference WCAG in litigation, but no regulation locks every private-sector website to a specific level.
That gap is why "we're WCAG 2.2 AA compliant" and "we're ADA compliant" are not interchangeable claims.
Yes Yes Know builds accessibility audits around that distinction. We evaluate websites and products against WCAG 2.2 AA and map each finding to the criterion it violates — without treating that technical work as a legal determination.
WCAG Conformance Levels: A, AA, and AAA
The three levels are cumulative. Level AA requires satisfying all Level A criteria plus Level AA criteria. Level AAA requires satisfying Level A, AA, and AAA. You can't skip to AAA without covering the lower levels first.
Level A: Foundational Accessibility
Level A is the floor. It addresses barriers that can block some users from accessing content at all. These are not inconveniences but outright dead ends.
Common Level A requirements include:
- Text alternatives for images and non-text content (SC 1.1.1)
- Full keyboard operability for all interactive functionality (SC 2.1.1)
- Labels or instructions on form inputs (SC 3.3.2)
- Seizure protection — no content flashing more than three times per second (SC 2.3.1)
Level A is necessary, but it's rarely sufficient. Most legal frameworks, procurement contracts, and real-world usability needs go well beyond it.
Level AA: The Practical Standard for Most Organizations
Level AA is where most organizational accessibility programs land, and for good reason. It tackles the barriers people actually run into day to day: low contrast text, hidden focus indicators, content that breaks on mobile, and unclear error messages.
A few defining AA criteria:
- Contrast (Minimum) — text needs at least a 4.5:1 ratio against its background; large text (18pt, or 14pt bold) only needs 3:1 (W3C, SC 1.4.3)
- Resize Text — content must resize up to 200% without breaking
- Focus Visible — keyboard users need a visible indicator of where they are
- Reflow — content must work at 320px width without two-dimensional scrolling
Why AA specifically? It's the level named in the ADA Title II rule for government sites and baked into Section 508 for federal procurement. Enterprise buyers running through VPAT reviews frequently expect it too. Verify the specific law, contract, or policy that applies to your organization, but AA is the reasonable default starting point for a remediation roadmap.
Level AAA: Enhanced or Aspirational Accessibility
Level AAA is the ceiling. It adds stricter, more specialized requirements meant to serve a wider range of situations and disabilities.
Examples include:
- Contrast (Enhanced) — a 7:1 ratio for normal text, versus AA's 4.5:1 (W3C, SC 1.4.6)
- Sign Language (Prerecorded) — full sign-language interpretation for synchronized media
- Extended Audio Description — for video where standard pauses aren't long enough
- No Timing — removing time limits on interactions almost entirely
- Reading Level — supplemental content when text requires above lower-secondary reading ability
The W3C itself is explicit here: it doesn't recommend requiring AAA conformance for entire websites. Some AAA criteria conflict with a piece of content's actual purpose, or simply can't apply universally. You can't add sign language interpretation to every video on a data dashboard, for instance.
The smarter approach: target AA across your product, then apply select AAA criteria to your highest-stakes experiences: authentication flows, healthcare intake forms, financial transactions, critical alerts, or frequently used B2B workflows.
| Level | Purpose | Typical Examples | Cumulative? |
|---|---|---|---|
| A | Removes access blockers | Alt text, keyboard access, labels | Baseline |
| AA | Broader usability standard | Contrast, resize, focus visibility, reflow | Includes A |
| AAA | Enhanced/specialized support | Enhanced contrast, sign language, no timing | Includes A + AA |
How to Choose the Right WCAG Level
The right target isn't "the highest one available." It depends on your legal context, your users, and your product's realistic constraints.
Factors to weigh:
- Legal and contractual requirements — Are you covered by ADA obligations, Section 508, state public-sector rules, or a customer contract naming a specific WCAG version and level?
- Product scope and user impact — Prioritize core journeys: sign-in, search, data tables, charts, payments, alerts, and any workflow users with disabilities rely on most.
- Current maturity — Look honestly at your design system, legacy content, third-party components, and your team's capacity to test and fix issues.
- Testing and evidence — Combine automated scans with manual keyboard testing, screen reader checks, and, where feasible, testing with actual people with disabilities.
- Long-term maintenance — Build accessibility requirements into design, QA, and release processes so conformance doesn't rely on a single one-time audit.
This is where a structured audit earns its keep. Yes Yes Know's accessibility audits combine automated tooling with manual screen-reader testing using NVDA or VoiceOver, keyboard-only navigation review, and focus-order checks.
Our flat-fee $5,000 audit evaluates a website or product against WCAG 2.2 AA, maps every finding to its specific criterion, and rates severity as critical, serious, moderate, or minor. That turns a long list of technical findings into a roadmap your design and dev teams can act on.
For B2B software vendors facing procurement pressure from government agencies, higher education, or large enterprise buyers requesting a VPAT, that prioritization matters more than chasing a perfect score across every criterion.
What to Check Before Finalizing a WCAG Target
Before you publish an accessibility claim on your website, in a sales deck, or in a VPAT, check these details.
Never describe your product as simply "WCAG compliant." Instead, name:
- The WCAG version (2.0, 2.1, or 2.2)
- The conformance level (A, AA, or AAA)
- The exact product or page scope evaluated
- The testing methods used
- Any known exceptions
- The date of assessment
Don't rely solely on automated scans. Automated tools catch code-level issues like missing alt attributes, but they miss cognitive load problems, confusing interaction patterns, and most screen-reader-specific breakdowns. Manual testing fills that gap.
Don't choose AAA only for marketing appeal, and don't treat AA as a permanent finish line either. Document which specific AAA improvements genuinely help your users, then build ongoing remediation and regression testing around them—not a one-off project that falls out of date.
Accessibility statements, VPATs, and ACRs should accurately reflect the evidence behind them. When you need help turning test results into a defensible claim, Yes Yes Know supports audit interpretation, accessible design, and remediation planning. Founder Jen Bullard holds CPACC certification through the International Association of Accessibility Professionals. We offer this as expert guidance for your process, not as legal certification. That determination belongs with your legal counsel.
Conclusion
WCAG's A, AA, and AAA levels are cumulative conformance tiers, not competing standards, and not laws in themselves. For most US organizations, Level AA is the practical baseline — but the specific legal or contractual requirement governing your product still needs direct verification.
Treat accessibility as an ongoing product practice, not a checkbox:
- Audit real workflows
- Involve actual users with disabilities
- Fix the highest-impact barriers first
- Apply AAA improvements selectively, where they genuinely improve access for people using your product
Frequently Asked Questions
What are the differences between WCAG 2.2 AA and AAA levels of accessibility?
AAA includes all A and AA criteria plus additional, more demanding requirements. AA is the far more common organizational target; AAA criteria are typically applied selectively to high-impact features rather than an entire product.
What are the three levels of accessibility?
Level A covers foundational, access-blocking barriers. Level AA addresses broader usability needs like contrast and navigation. Level AAA adds the most demanding criteria, and each higher level includes everything below it.
What is AA and AAA in color contrast?
WCAG 2.2's AA standard requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. AAA raises that to 7:1 for normal text. Always verify current ratios and applicable exceptions against W3C's published guidance.
What are the new WCAG guidelines for 2026?
WCAG 2.2 remains the current W3C Recommendation. WCAG 3.0 exists only as a Working Draft. W3C explicitly states that draft status doesn't imply endorsement and the document may still change significantly. Don't treat WCAG 3.0 as finalized guidance yet.
What does WCAG stand for?
WCAG stands for Web Content Accessibility Guidelines, developed by the W3C through its Web Accessibility Initiative. It's a set of technical accessibility criteria, not a standalone US law.
