"I Want the Best. Make It AAA."
A client says it in the kickoff call like it's the easiest decision he'll make all quarter. His agency has just finished pitching a redesign, and when the topic of accessibility comes up, he waves a hand and says: "Just make it AAA compliant. I don't want the minimum, I want the best."
Nobody in the room pushes back. It sounds reasonable. Nobody wants to be the person who argues for "less."
Three months later, the project is over budget, a chunk of the site's video library still doesn't have sign-language interpretation, some of the marketing copy has been rewritten to bring it down to a "lower reading level" and now sounds nothing like the brand, and the agency is quietly explaining to the client that certain AAA criteria can't be satisfied for certain content types — not because of a lack of effort, but because the standard's own authors say so.
The client didn't need AAA. He needed AA. He just didn't know there was a difference, and nobody told him before the invoices started arriving.
This is the conversation that should have happened in that kickoff call. Let's have it now.
WCAG Isn't One Bar — It's Three
The Web Content Accessibility Guidelines organize every success criterion into one of three conformance levels: A, AA, and AAA. They're not three different standards competing for attention — they're tiers, each one building on the last. AA includes everything in A. AAA includes everything in AA plus more. Think of them less like three separate exams and more like a single ladder with three rungs, where each rung requires everything below it.
The mistake almost everyone makes is assuming the ladder is a straightforward "better, best" progression, where climbing higher is always the right move. It isn't. Each rung was designed with a specific purpose, and the top rung was explicitly not designed to be a universal target. Understanding why is the entire point of this article.
Level A: The Floor, Not a Goal
Level A covers the baseline barriers — the failures so fundamental that a site with them isn't really usable by a meaningful number of people with disabilities, full stop.
A few examples:
- 1.1.1 Non-text Content — images, icons, and non-text elements need alt text. Not perfect alt text. Just alt text that exists at all.
- 2.1.1 Keyboard — everything on the page that a mouse can do, a keyboard has to be able to do too. No functionality can be locked behind a hover or a click alone.
- 4.1.2 Name, Role, Value — interactive elements need to correctly expose what they are and what state they're in to assistive technology, so a screen reader can actually announce "button, expanded" instead of announcing nothing useful at all.
If a site fails Level A, the barriers aren't subtle. A screen reader user might hit a form with zero labels. A keyboard-only user might tab into a menu and simply get stuck, with no way out and no way forward. These aren't edge cases or nice-to-haves — they're the difference between a site that technically loads and a site a disabled user can actually operate.
Level A matters. But it is a floor, not a destination. Stopping here still leaves real legal exposure and a genuinely broken experience for a lot of users.
Level AA: Where the Law Actually Lives
This is the level that matters most for the overwhelming majority of organizations, and it's worth being specific about why, because "AA is the standard" isn't an opinion — it's what the actual legal and regulatory text says.
- The DOJ's Title II rule for state and local government websites specifically names WCAG 2.1 AA as the standard.
- EN 301 549, the technical standard that the EU's European Accessibility Act relies on, is built around WCAG AA.
- Most ADA Title III settlements in the U.S. — the kind that show up after a lawsuit or a demand letter — target AA as the negotiated outcome.
In other words: when a regulator, a court, or a settlement agreement says "be accessible," AA is almost always the specific bar they mean. Not A. Not AAA. AA.
What does AA actually add on top of A? A few representative examples:
- 1.4.3 Contrast (Minimum) — text needs a contrast ratio of at least 4.5:1 against its background. This is the rule behind why light-gray text on a white background, which looks stylish in a mockup, routinely fails.
- 2.4.7 Focus Visible — when a user tabs to a link or button, there has to be a visible indicator showing where focus landed. No more silently losing your place.
- 3.3.3 Error Suggestion — when a form field fails validation, the error message has to actually suggest how to fix it, not just say "invalid input."
None of these are exotic asks. They're specific, testable, achievable requirements that meaningfully improve usability for people with low vision, motor impairments, and cognitive disabilities — which is exactly why lawmakers and courts converged on AA as the practical, enforceable line. It's rigorous enough to matter and realistic enough to actually apply across an entire real-world website.
Level AAA: The Ceiling the W3C Itself Warns You Off
Here's the part that surprises almost everyone, including plenty of agencies who should know better: the W3C's own conformance documentation explicitly states that AAA conformance for entire sites is not recommended as a general policy.
That's not a hedge. That's the standard's authors telling you directly not to blanket-mandate the top level.
Why? Because some AAA criteria are, by design, impossible to satisfy uniformly across an entire site's content. A few examples make this concrete:
- 1.2.6 Sign Language (Prerecorded) requires sign-language interpretation for all prerecorded audio content. Applied literally, site-wide, that means every video, every podcast embed, every recorded webinar needs a sign-language interpreter track. For most organizations, that's not a stretch goal — it's simply not realistic to apply universally.
- 1.4.6 Contrast (Enhanced) raises the contrast bar to 7:1, well above AA's 4.5:1. Achievable in plenty of places, genuinely difficult in others without gutting a brand's visual identity.
- 3.1.5 Reading Level asks that content be understandable at a lower secondary education reading level, or that a simplified alternative be provided. For a site publishing complex technical or legal content, that's a real problem — you can't always simplify a contract clause or a clinical description without changing its meaning.
This is exactly what happened to the client from the opening story. He asked for "the best" without knowing that "the best," applied as a blanket policy, includes criteria the standard's own authors consider unrealistic for general use. His agency spent budget chasing something the client never actually needed — and in some cases, couldn't fully deliver, through no fault of their own.
So What Should You Actually Target?
The practical answer, for nearly every business, nonprofit, and government site: target WCAG 2.1/2.2 Level AA as your baseline, and layer in specific AAA criteria selectively, where they're low-cost and high-value, rather than committing to full AAA across the board.
A short list of what that looks like in practice:
- Build to AA as the contractual, legal, and functional target — this is what regulators and courts actually check.
- Where enhanced contrast (7:1) is easy to apply without harming brand or design — do it. It's a low-cost AAA win.
- Support reduced-motion preferences where relevant — another AAA-adjacent improvement that's cheap and genuinely helpful.
- Don't mandate full-site sign-language interpretation, universal 7:1 contrast, or a rewritten reading level across all content, unless a specific legal or contractual obligation actually requires it.
- Document your target level clearly before development starts, so nobody discovers three months in that "AAA" meant something very different than they imagined.
Getting this wrong costs money in both directions. Stop at Level A, and you're carrying real legal risk plus a genuinely broken experience for keyboard and screen-reader users. Mandate blanket AAA, and you're burning budget chasing criteria that may not even apply cleanly to your content types — sign-language tracks for every video, simplified rewrites of technical content, contrast ratios that fight your brand guidelines every step of the way.
The Confident Answer
There's no prize for picking the highest-sounding label. WCAG AA is not "the minimum you can get away with" — it's the specific, deliberate standard that regulators, courts, and the EU's own technical framework converged on because it's rigorous and achievable at the same time. AAA isn't "extra credit" for the whole site — it's a set of individually valuable criteria meant to be applied selectively, exactly as the W3C itself recommends.
If you're heading into a redesign, an audit, or a legal conversation and someone on your team says "let's just go AAA," that's the moment to stop and get specific about what's actually required, what's actually achievable, and what's actually going to protect the organization. Guessing at the right conformance level is how budgets get blown on criteria that were never the target in the first place.
WCAG.World scopes every engagement against the conformance level that actually matches your legal exposure and your content — not the level that sounds most impressive in a kickoff call. See what a properly scoped AA compliance engagement looks like before you commit budget to the wrong target.