← Accessibility Insights & Resources

WCAG Levels A, AA and AAA Explained

What the three WCAG conformance levels mean, how they differ in practice, why laws and contracts ask for AA, and whether you need to think about AAA at all.

Open the WCAG 2.2 AA checklist

WCAG has three conformance levels: A, AA and AAA. Every WCAG success criterion is assigned to one of them. Level A is the minimum. Level AA means you meet every Level A and every Level AA criterion. Level AAA means you meet all three sets. Level AA is the level that laws, contracts and procurement policies almost always ask for, and it's the one most organizations should aim at.

The levels stack. You can't be "AA but not A", and there's no such thing as conforming to "AA only". If someone asks for WCAG Level AA, they're asking for the A and AA criteria together.

You don't need Level AAA for a whole website, and W3C, which publishes WCAG, says it shouldn't be required that way. Some individual AAA criteria are still worth adopting. The rest of this article explains why.

What the three WCAG levels mean

The definitions come from the conformance level requirement in WCAG 2.2:

  • Level A is "the minimum level of conformance". The page satisfies all the Level A success criteria.
  • Level AA: the page satisfies all the Level A and Level AA success criteria.
  • Level AAA: the page satisfies all the Level A, Level AA and Level AAA success criteria.

At each level, WCAG also accepts a "conforming alternate version" of the page in place of the page itself, but that's a narrow exception with its own conditions, not a shortcut.

WCAG conformance levels compared (criteria counts are for WCAG 2.2)
LevelCriteria at this levelCriteria you must meet to conformWhere you'll see it
A3131 (all Level A)The floor. Rarely the stated target on its own.
AA2455 (all Level A and AA) The usual legal and contractual target, including the AODA, the US ADA Title II web rule and Section 508.
AAA3186 (every criterion) Rarely required for a whole site. Individual criteria are adopted where they suit the content or audience.

The counts above are for WCAG 2.2. Earlier versions have fewer criteria, but the three levels work the same way in WCAG 2.0, 2.1 and 2.2. For what each version added, see WCAG 2.0 vs 2.1 vs 2.2.

Level A does not mean "low severity"

It's tempting to read the levels as a priority ranking: A is critical, AA is important, AAA is nice to have. W3C says otherwise. Its guide to the conformance levels states that WCAG 2 "does not suggest any particular level of priority or severity" and that "every criterion is important to one or more user groups".

The working group sorted criteria into levels by weighing several practical factors, including:

  • whether assistive technology can work around a failure
  • whether the criterion can be met on every kind of website and content
  • whether content creators can reasonably learn the skills to meet it
  • how much it limits functionality or visual design

Roughly, Level A criteria cover barriers that users can't work around and that any site can fix. Level AAA criteria are ones that can't be met for all content, or that demand large changes to design or function. That is why a missing form label (Level A) and low-contrast text (Level AA) can both stop someone from using your site, even though they sit at different levels.

Example criteria at each level

The differences are easiest to see by following one topic through the levels. Each row below names the WCAG success criterion so you can look it up.

How requirements on the same topic change from Level A to Level AAA
TopicLevel ALevel AA addsLevel AAA adds
Video and audioCaptions for prerecorded video (1.2.2) Captions for live video (1.2.4) and audio description for prerecorded video (1.2.5) Sign language interpretation for prerecorded video (1.2.6)
Colour and contrastColour is not the only way information is conveyed (1.4.1)Text contrast of at least 4.5:1, or 3:1 for large text (1.4.3)Text contrast of at least 7:1, or 4.5:1 for large text (1.4.6)
Keyboard All functionality works from a keyboard, with a narrow exception for input that depends on the path of movement, such as freehand drawing (2.1.1) The keyboard focus indicator is visible (2.4.7)All functionality works from a keyboard, with no exception (2.1.3)
HeadingsHeadings are marked up as headings in the code (1.3.1)Headings and labels describe the topic or purpose (2.4.6)Section headings are used to organize the content (2.4.10)
LinksLink purpose is clear from the link text plus its context (2.4.4)No further criterion on link purposeLink purpose is clear from the link text alone (2.4.9)
Form errorsErrors are identified and described in text (3.3.1) Suggestions for fixing errors (3.3.3), and a way to review, check or reverse submissions that are legal, financial or change stored data (3.3.4) The same review, check or reverse protection for every submission (3.3.6)
Touch and click targetsNo size requirementTargets at least 24 by 24 CSS pixels, with exceptions (2.5.8, new in WCAG 2.2)Targets at least 44 by 44 CSS pixels, with exceptions (2.5.5)

Two patterns stand out. Level AA often puts a number on something Level A leaves open, like contrast. And Level AAA often removes the exceptions that A or AA allow, like the keyboard and error prevention rows.

We cover two of these topics in depth in our guides to colour contrast and video captions and transcripts.

Why laws and contracts settle on Level AA

Level A alone leaves real barriers in place. A site can meet every Level A criterion and still have pale grey text, no visible keyboard focus and layouts that break when zoomed. Level AAA, as W3C itself says, can't be met for all content. Level AA is the highest level that can reasonably be asked of a whole website, which is why it became the standard reference.

You can see this in the rules themselves:

  • Ontario (AODA). The Integrated Accessibility Standards Regulation requires public sector organizations, and private and non-profit organizations with 50 or more employees, to make their public websites conform to WCAG 2.0 Level AA, except for live captions and pre-recorded audio description. Our AODA requirements guide has the details.
  • United States, state and local government. The Department of Justice's ADA Title II web rule names WCAG 2.1 Level AA as the technical standard for web content and mobile apps.
  • United States, federal procurement. The Revised Section 508 Standards require electronic content to conform to the Level A and Level AA success criteria of WCAG 2.0.

The versions differ, but the level is the same every time. Contracts and RFPs follow the same pattern. This is general information, not legal advice.

Do you need WCAG Level AAA?

For a whole website, no. WCAG says so directly, in a note under the conformance level requirement:

"It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content."

That's Note 2 of section 5.2.1 in WCAG 2.2. It's worth knowing the exact wording, because a blanket "must be WCAG AAA" clause still turns up in contracts and internal policies now and then. If you're handed one, point to this note and ask which criteria the other side really cares about.

The note is about requiring AAA across an entire site. It doesn't say AAA criteria are unimportant or should be ignored. The note just before it encourages organizations to report any progress they've made on criteria beyond the level they conform to.

When individual AAA criteria are worth adopting

Treat Level AAA as a menu, not a target. Pick the criteria that fit your content and the people who use it. In our experience these are the ones most often worth the effort:

  • Enhanced contrast (1.4.6). Body text at 7:1 is easy to reach with dark text on a light background and helps people with low vision.
  • Larger targets (2.5.5). Buttons and links at 44 by 44 CSS pixels are easier for everyone on a phone, and matter most for people with tremors or limited dexterity.
  • Link text that stands alone (2.4.9). "Download the 2026 annual report" instead of "click here" helps screen reader users who browse by a list of links.
  • Section headings (2.4.10). Breaking long pages into headed sections is good writing practice anyway.
  • Error prevention on every form (3.3.6). If you already let people review and correct a payment, doing the same on other forms is usually a small step.
  • Timeout warnings (2.2.6). Telling people how long they can be inactive before losing their data helps anyone who needs more time.
  • Animation that can be switched off (2.3.3). Motion triggered by scrolling or clicking can make some people ill.

Others depend on your audience:

  • Sign language interpretation (1.2.6) matters if your videos are aimed at Deaf audiences who use a signed language.
  • Reading level (3.1.5) asks for a simpler version or supplemental content when text needs more than a lower secondary education level to read. That's valuable for public information, health and government content.

If you adopt some AAA criteria, say which ones in your accessibility statement. Don't claim "Level AAA" unless a page meets all of them.

Not sure where your site stands against Level AA?

Run a free automated scan to catch the issues a tool can detect, then work through the full list of Level A and AA criteria with our checklist.

Run a free scan

The WCAG conformance requirements

Meeting the success criteria is only the first of five conformance requirements in WCAG. All five must be satisfied before a page conforms at any level.

  1. Conformance level. One of the three levels is met in full. Meeting most of the AA criteria is not Level AA.
  2. Full pages. Conformance is for whole web pages only. You can't exclude part of a page, such as a chat widget or an embedded map, and claim the rest conforms. Each responsive variation of the page, such as the mobile layout, counts too.
  3. Complete processes. When a page is one step in a process, every page in that process has to conform at the same level or better. WCAG's own example is an online store: every page from selecting a product to the end of checkout must conform for any of them to conform.
  4. Accessibility-supported technologies. You can only rely on ways of using technologies that work with assistive technology and browsers.
  5. Non-interference. Anything on the page that isn't accessible must not block people from using the rest of it. Four criteria apply to all content on the page no matter what: audio control, no keyboard trap, the three flashes threshold, and the ability to pause, stop or hide moving content.

The second and third requirements have the biggest practical effect. A booking flow with one inaccessible date picker doesn't conform, however good the other pages are. This is why a proper audit tests whole journeys from start to finish, not a handful of separate pages. See what a website accessibility audit involves.

One more point: conformance claims are optional. WCAG says authors can conform without making a claim. If you do make one, it must include the date, the WCAG version, the level, the pages covered and the technologies relied on.

What "partially conforms" means

You'll see this phrase in three places, and it means something different in each. In WCAG's own terms, there is no partial level: a page either meets all the requirements for a level or it doesn't conform at that level.

In WCAG itself

WCAG defines a statement of partial conformance for two specific situations. The first is content you don't control, such as user comments or advertisements inserted from other sources. The statement takes the form "This page does not conform, but would conform to WCAG 2.2 at level X if the following parts from uncontrolled sources were removed." The second is a page in a language that assistive technology doesn't yet support.

Neither covers your own code. "We haven't fixed the menu yet" is not partial conformance in the WCAG sense.

In accessibility statements

W3C's accessibility statement generator offers "partially conformant" as a status, meaning "some parts of the content do not fully conform to the accessibility standard". This is the everyday use: an honest way to say you're close but have known gaps. If you use it, list the gaps. Our guide on how to write an accessibility statement shows how.

In a VPAT or ACR

An Accessibility Conformance Report rates each criterion separately. "Partially Supports" there means some functionality of the product does not meet that one criterion. It says nothing about the product's overall level. The report has separate tables for Level A, AA and AAA, and the AAA table is the only one where "Not Evaluated" is allowed, according to the US government's guidance on creating an ACR. More in what a VPAT and an ACR are.

Which level should you aim for?

  • Aim for Level AA. It's what the law and most contracts expect, and it removes the barriers that most often stop people.
  • Don't stop at Level A. It's a milestone on the way, not a target. If you're fixing a site in stages, order the work by how badly each barrier blocks people, not by its level.
  • Add the AAA criteria that suit your audience. Report them, but keep your conformance claim at AA.
  • Check the version as well as the level. "Level AA" means different sets of criteria in WCAG 2.0, 2.1 and 2.2. A contract should name both.

Our audits test against WCAG 2.2 Level AA by default, which also covers the AODA's WCAG 2.0 Level AA baseline. See our fixed packages for what each one covers.

Frequently asked questions

What is WCAG Level AA?

Level AA is the middle of WCAG's three conformance levels. A page conforms at Level AA when it meets every Level A and every Level AA success criterion, along with WCAG's other conformance requirements. In WCAG 2.2 that's 55 criteria.

Does Level AA include Level A?

Yes. The levels are cumulative. Level AA conformance requires all the Level A criteria as well, and Level AAA requires all of A and AA.

Do I need WCAG AAA?

Not for a whole site. WCAG itself says Level AAA is not recommended as a general policy for entire sites, because some content can't satisfy every AAA criterion. Adopting individual AAA criteria that suit your content, such as enhanced contrast or larger targets, is a better approach.

Is Level A enough to comply with the AODA?

No. Where the AODA's website rule applies, it requires WCAG 2.0 Level AA, with exceptions only for live captions and pre-recorded audio description.

Can a website be partly Level AA?

Not in WCAG's terms. A page conforms at a level only when it meets all of that level's criteria, and a multi-step process conforms only when every page in it does. You can describe a site as partially conformant in an accessibility statement, as long as you list what falls short.

Are Level A issues more serious than Level AA issues?

Not necessarily. W3C says the levels don't indicate priority or severity. How serious a failure is depends on what it blocks and how often people run into it. A Level AA contrast failure on your checkout button can do more harm than a Level A issue on a page few people visit.