skip to content

What do the WCAG conformance levels A, AA and AAA mean, and why is AA the usual target?

level: middleimportance: must knowfreq 74%

answer

  1. Three letters, and they stack
  2. A claim needs everything below it too
  3. One level is what buyers usually ask for
  4. The top level is not a product target

basics

~20 s

Every WCAG success criterion carries one level. A claim at AA means every level A and every level AA criterion is satisfied — the levels stack. AA is the common target because AAA cannot be met across all content.

solid answer

~50 s

A level is a property of a **criterion**, assigned when it was written. The assignment reflects whether the requirement is essential and whether it can be met for all kinds of content — not how hard it is to implement. Levels **stack**: a claim at AA requires every level A criterion too, so one unmet A criterion means the page conforms at no level at all. You can watch the ladder on a single subject: captions for prerecorded media sit at level A (1.2.2 Captions (Prerecorded)), captions for live media at AA (1.2.4 Captions (Live)), and sign-language interpretation of prerecorded media at AAA (1.2.6 Sign Language (Prerecorded)). AA is the target because it is where the essential and universally applicable requirements land, and because many jurisdictions' public-sector rules and enterprise procurement questionnaires reference the standard at that level.

go deeper

for a junior

Know the three letters and that they stack: a claim at AA means every level A criterion and every level AA criterion is satisfied. Saying that cleanly, without hedging, is most of what is asked at this level.

for a middle

Explain what a level is assigned for — necessity and applicability to all content, not implementation effort — and show the ladder with one subject that appears at more than one level. Expect to be pushed on what a failure at A does to an AA claim.

for a senior

An interviewer expects you to price the target: what AA costs across real screens, why a single A failure sinks the claim, and how you answer a buyer who asks for AAA. Bring version and scope into the answer without being prompted.

for a principal

Own the commitment. Decide the level and version the organisation will stand behind, which AAA criteria are worth adopting individually, and how you keep teams from an over-claim that a customer's own spot-check can falsify.

## What a level actually is A conformance level is a property of a **success criterion**, not of a feature, a team or a product. Every criterion in WCAG is published at exactly one of three levels, and that level was assigned when the criterion was written, by asking questions like: is this essential rather than merely helpful? Can it be satisfied for all kinds of content, in all technologies, without changing what the content fundamentally is? Does it require skills a competent team can reasonably be expected to have? Would it constrain presentation so much that whole categories of design become impossible? Note what is not on that list: **implementation difficulty**. Level is about necessity and universal applicability, not about how many hours the fix takes. Some level A criteria are expensive on a given product; some AAA criteria are nearly free. ## The three levels, and how they stack | Level | What a claim at this level requires | Where it shows up | |---|---|---| | **A** | Every level A criterion satisfied | The floor; failures here usually mean a user cannot complete the task at all | | **AA** | Every level A **and** every level AA criterion satisfied | The practical product target, and the level most external commitments name | | **AAA** | Every A, AA **and** AAA criterion satisfied | Adopted criterion by criterion; rarely claimed for a whole product | The stacking is the fact candidates most often miss. **There is no such thing as conforming at AA while failing a level A criterion.** A single unmet level A criterion means the page conforms at no level — not at A, and not partially at AA. Conformance is binary, per page, per level. A good way to feel the ladder is to watch one subject climb it: - 1.2.2 Captions (Prerecorded), at level **A** — captions for recorded media. Essential, and achievable for any content that has a script or can be transcribed. - 1.2.4 Captions (Live), at level **AA** — the same user need for live media. Still essential to many users, but it costs real operational capacity. - 1.2.6 Sign Language (Prerecorded), at level **AAA** — genuinely valuable, and beyond what most organisations can supply for all of their content. Nothing about that ladder is a statement of how hard the code is. It is a statement about how universally the requirement can be applied. ## Why AA is the level everyone names Two reasons, and they reinforce each other. - **AA is where the standard's own judgement lands** for requirements that are both essential and universally applicable. A product that satisfies only level A is claimable but still hard for many people to use. - **AA is the level external commitments reference.** Many jurisdictions' public-sector rules and a large share of enterprise procurement questionnaires ask for conformance at level AA against a named version of the standard. The specifics differ everywhere, so the safe general statement is simply this: if a buyer asks about accessibility at all, they will almost certainly ask about AA. That is why 'we are targeting AA against a named version, across these screens' is a meaningful sentence in a planning meeting and 'we are aiming for accessibility' is not. ## Why AAA is not a whole-product target The standard itself advises against requiring AAA conformance as a general policy for entire sites, because it is not possible to satisfy every level AAA criterion for some content. That is not a loophole, it is a structural fact about what those criteria ask for. Committing a product to full AAA therefore commits it to a claim it can never truthfully publish, and the predictable outcome is that the team quietly stops measuring anything. The mature pattern is: 1. **Target AA for the whole product**, with the version named, and treat any level A or AA failure as a defect with an owner and a date. 2. **Adopt selected AAA criteria** where they matter for your users and are achievable for your content — and describe that as meeting those specific criteria, never as conforming at AAA. 3. **Never claim a level you have not verified across the claimed scope.** An over-claim is worse than a modest one precisely because it is checkable by anyone. ## What an interviewer is listening for - That levels **stack**, and that one level A failure sinks an AA claim outright. - That a level reflects necessity and universality rather than effort. - That AAA is a source of individual criteria to adopt, not a product goal. - That the answer to 'which level?' always arrives with 'which version?' and 'over which screens and which processes?'. A level on its own is not a target; it is half of one.

  • Your product meets every AA criterion except one, on one screen. What can you publish?
    No claim for that screen at that level — conformance is per page and binary. You can claim conformance for the pages and processes that do satisfy the level, state that scope precisely, and record the failing screen as a known defect with an owner and a target date. A scoped, honest claim is publishable; a blanket one is not.
  • When is adopting an individual AAA criterion the right call?
    When it addresses a barrier your actual users hit and your content can meet it consistently across releases. Adopt it as a product rule, verify it like any other requirement, and describe it as meeting that specific criterion. Never describe it as conforming at AAA, which commits you to every AAA criterion across the whole claimed scope.
  • A buyer asks for AAA conformance wherever possible. How do you answer?
    Explain that AAA is not a whole-product level: the standard advises against requiring it as a general policy because some content cannot satisfy every AAA criterion. Offer AA across a named scope and version as the commitment, plus a short list of AAA criteria you actually meet and verify. That is stronger than a vague yes because it is checkable.

saying these in an interview costs you the question

  • Claims AA while a level A criterion is still failing
  • Says the level measures how hard a fix is
  • Promises full AAA conformance for an entire product
  • Thinks AAA replaces A and AA rather than adding
  • Gives a level without naming a version or scope