WCAG Conformance Levels A, AA, AAA Compared

1. What WCAG conformance levels really mean

The Web Content Accessibility Guidelines (WCAG) are organized into principles, guidelines and individual success criteria, and each of those criteria is assigned to exactly one of three conformance levels: A, AA or AAA. One often overlooked detail matters here: the levels are cumulative. Level AA automatically includes every Level A criterion, and Level AAA additionally includes every A and AA criterion. So these are not three separate catalogs, but a staged requirement hierarchy that gets stricter and more comprehensive with each level.

A common misconception is that AAA simply means "the best, most complete accessibility" and should therefore always be the goal. The W3C itself explicitly contradicts this in the official WCAG documentation: not every AAA criterion can be satisfied for every type of content, and some criteria even conflict with other goals of a website. The three levels are not a pure quality scale, but a trade-off between achievable benefit, technical effort, and universal applicability across all content types.

2. Level A: the absolute minimum requirements

Level A covers the criteria without which content remains fully inaccessible to certain user groups, not merely uncomfortable. This includes alternative text for informative images (1.1.1), full keyboard operability without a mouse (2.1.1), the absence of keyboard traps (2.1.2), programmatically determinable structure for screen readers (1.3.1), and correct name, role, value exposure for all interactive components (4.1.2). These criteria prevent hard blockers: a form that cannot be operated by keyboard, or an image without alt text inside a link, locks out screen reader or keyboard users entirely, not just partially.

That is exactly why Level A alone is practically never sufficient as a standalone goal. It removes the most severe access barriers but leaves out many criteria that are decisive for everyday usability, such as color contrast or text scaling. The example below shows typical Level A basics in a Hyvä form: an associated label, meaningful alt text, and a custom element that is fully keyboard operable.

<!-- Level A: form fields need a programmatically associated label -->
<form novalidate>
  <div class="mb-4">
    <label for="email" class="block text-sm font-medium mb-1">Email address</label>
    <input type="email" id="email" name="email" required
           aria-describedby="email-hint email-error"
           class="border rounded px-3 py-2 w-full">
    <p id="email-hint" class="text-xs text-gray-500">We only use this address to confirm your order.</p>
    <p id="email-error" class="text-xs text-red-600" role="alert" hidden>Please enter a valid email address.</p>
  </div>

  <!-- Level A: informative images need meaningful alt text -->
  <img src="/media/free-shipping-badge.svg" alt="Free shipping on orders over 50 euros" width="120" height="40">

  <!-- Level A: custom controls must be keyboard operable and focusable -->
  <div role="button" tabindex="0" id="add-to-cart"
       x-on:click="addToCart()" x-on:keydown.enter="addToCart()" x-on:keydown.space.prevent="addToCart()">
    Add to cart
  </div>
</form>

3. Level AA: the realistic target standard

Level AA adds the criteria that make the biggest perceivable difference for the broad majority of users: a minimum contrast of 4.5:1 for normal text and 3:1 for large text (1.4.3), the ability to scale text up to 200 percent without loss of function or content (1.4.4), reflow of content up to 400 percent zoom without horizontal scrolling (1.4.10), a visible focus indicator (2.4.7), consistent navigation across pages (3.2.3), and concrete error suggestions on form errors (3.3.3). These criteria are achievable with reasonable effort for practically any content type, without fundamentally changing design decisions.

That is exactly why Level AA is the level almost every relevant law and standard worldwide references, from the European EN 301 549 to Germany's BFSG to the prevailing case law around the US-American ADA. AA is the point where benefit and effort strike a balance that is workable for commercial websites. The CSS example below shows two typical AA requirements: contrast-safe color values and a visible focus ring that is never stripped away with outline: none.

/* AA: contrast ratio at least 4.5:1 for normal text, 3:1 for large text */
:root {
  --color-text: #1f2937;      /* on white background: ratio approx. 12.6:1 */
  --color-link: #1d4ed8;      /* on white background: ratio approx. 8.6:1 */
  --color-muted: #4b5563;     /* on white background: ratio approx. 7.1:1, safely above 4.5:1 */
}

/* AA: focus indicator must stay visible, never remove it with outline: none */
a:focus-visible,
button:focus-visible,
input:focus-visible {
  outline: 2px solid #1d4ed8;
  outline-offset: 2px;
}

/* AA: content must reflow at 400% zoom without horizontal scrolling */
.product-grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(16rem, 1fr));
  gap: 1.5rem;
}

4. Level AAA: why it is rarely mandated in full

Level AAA contains the strictest criteria in the WCAG: sign language interpretation for video (1.2.6), extended audio description (1.2.7), enhanced contrast of 7:1 (1.4.6), link text that is understandable without surrounding context (2.4.9), context-sensitive help at every form field (3.3.5), a reading level capped at lower secondary education (3.1.5), and the complete removal of time limits without exception (2.2.3). Each individual criterion makes sense, but combined and applied across an entire website they are practically almost impossible to fully implement.

The W3C itself points out that full AAA conformance for an entire website is not recommended as a general policy, because not every criterion can be satisfied for every content type. Producing sign language interpretation for every single product video of an online store is rarely economically realistic. A reading level capped at lower secondary education also often conflicts with technical content, such as detailed product data sheets. That is why both EN 301 549 and Germany's BFSG explicitly exclude Level AAA from the mandatory scope and consistently reference Level AA instead.

5. Legal framework: BFSG, EN 301 549 and the WCAG levels

Germany's Barrierefreiheitsstärkungsgesetz (BFSG) has required certain consumer products and services, including e-commerce websites, banking services and e-books, to be accessible since June 28, 2025. In substance, the BFSG points to the European standard EN 301 549, which in turn defines WCAG 2.1 Level AA as its harmonized technical benchmark. A shop operator who falls within the scope of the BFSG and implements Level AA thereby satisfies the central substantive requirement of the law. Level AAA does not appear anywhere in the BFSG as an obligation.

Outside Germany, the legal landscape converges on the same standard: EU Directive 2016/2102 for public sector bodies requires WCAG 2.1 Level AA, and in the United States, case law under the Americans with Disabilities Act (ADA) regularly cites WCAG 2.1 AA as the de facto proof standard in settlements and rulings, despite the statute itself lacking an explicit technical requirement. For internationally operating shops this means Level AA is not just the German benchmark, it is the most widely recognized legal baseline globally.

6. Success criteria per level: concrete examples

A direct comparison within the same principle makes the difference between levels tangible. Under the "Perceivable" principle, criterion 1.4.3 at Level AA requires a contrast of at least 4.5:1, while the related criterion 1.4.6 at Level AAA requires an enhanced contrast of 7:1, without replacing the AA criterion. Under the "Operable" principle, 2.4.4 at Level A requires that a link's destination be understandable in context, for example through the surrounding sentence, while 2.4.9 at Level AAA requires the link text alone, with no context at all, to be understandable.

Criterion numbering follows the pattern guideline.criterion, for example 1.4.3 for the third criterion of the fourth guideline under the first principle. The W3C's official WCAG quick reference can be filtered directly by conformance level, making it the most practical reference for checking exactly which criterion applies at which level for a specific feature before implementation begins.

7. Retrofitting selected AAA criteria

Even though full AAA conformance is neither mandated nor realistically achievable for most commercial websites, selectively adopting individual AAA criteria pays off wherever the benefit clearly outweighs the effort. Enhanced contrast of 7:1 for critical call-to-action buttons like the buy button costs little but noticeably helps users with limited vision. Context-independent link text also improves screen reader navigation via the links list, a feature many blind users actively rely on.

The spirit of criterion 2.2.3 (No Timing) is particularly effective: instead of ending a session after a fixed time without warning, offer an unlimited extension option. That combines the AA requirement 2.2.1 (Timing Adjustable) with the stricter AAA principle, without giving up session security. Important for external communication: such selective AAA additions should be explicitly documented, without claiming full AAA conformance that would not survive an audit.

// Combine AA "timing adjustable" with the AAA "no timing" spirit:
// never force a logout without an unlimited extension option
const SESSION_WARNING_MS = 60_000;
let sessionTimer;

function scheduleSessionWarning(sessionDurationMs) {
  clearTimeout(sessionTimer);
  sessionTimer = setTimeout(showExtendDialog, sessionDurationMs - SESSION_WARNING_MS);
}

function showExtendDialog() {
  const dialog = document.getElementById('session-extend-dialog');
  dialog.showModal();
  // Move focus into the dialog, keep it accessible via keyboard only
  dialog.querySelector('[data-action="extend"]').focus();
}

function extendSession() {
  fetch('/customer/section/extend', { method: 'POST' })
    .then(() => scheduleSessionWarning(getSessionDurationMs()));
}

8. Testing and proving conformance: tools, audits, statement

Conformance to a given level does not come from a one-time claim, it comes from a traceable testing methodology. Automated tools like axe-core, the Lighthouse accessibility audit or WAVE reliably cover roughly 30 to 40 percent of all WCAG criteria, mostly structural and programmatically checkable aspects such as missing alt text, contrast violations or invalid ARIA markup. The rest, such as logical reading order, sensible focus order, or actual screen reader comprehensibility, requires manual testing: keyboard-only walkthroughs and testing with real screen readers such as NVDA or VoiceOver.

For legally sound proof under the BFSG and the EU directive, a published accessibility statement is additionally required, one that documents the conformance level achieved, the testing methodology used, known exceptions, and a feedback contact for users. This statement can be stored as structured schema.org metadata, so that automated checking systems and search engines can also associate the documented conformance level with the page.

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "url": "https://mironsoft.de/accessibility-statement",
  "accessibilitySummary": "Conformance level WCAG 2.1 Level AA, supplemented with selected AAA criteria.",
  "accessibilityConformance": "WCAG 2.1 Level AA",
  "accessibilityFeature": [
    "alternativeText",
    "structuralNavigation",
    "highContrastDisplay",
    "resizeText"
  ],
  "accessibilityHazard": "none",
  "lastReviewed": "2026-06-01",
  "author": { "@type": "Organization", "name": "Mironsoft" }
}

9. WCAG levels in direct comparison

In practical implementation, for example in a Hyvä theme, Level A starts with structural basics: skip links, semantic landmark elements, and a logical heading hierarchy. In a cleanly built Hyvä template these basics cost barely any extra effort, because the theme already favors lean, semantic HTML over generic div soup. That makes Hyvä shops a structurally favorable starting point for Level AA.

<!-- Level A/AA baseline in a Hyva layout: skip link plus landmark roles -->
<a href="#main-content"
   class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:bg-white focus:px-4 focus:py-2 focus:rounded">
  Skip to main content
</a>

<header role="banner">
  <nav aria-label="Main navigation">…</nav>
</header>

<main id="main-content" role="main">
  <h1>Product catalog</h1>
  <!-- page content -->
</main>

<footer role="contentinfo">…</footer>

The table below compares five typical requirement areas and shows what is still missing at Level A alone, what Level AA adds as the recommended practical standard, and which optional AAA extension goes beyond that.

The table makes clear why the effort between levels does not scale linearly: the jump from A to AA brings a perceivable improvement for almost every user at a manageable implementation cost, while the full jump to AAA is, in many rows, either barely practicable or hard to reconcile with other criteria. That is exactly why selectively adopting individual AAA rows remains the more economically sound strategy compared to claiming full, sitewide AAA conformance.

10. Summary

The WCAG conformance levels A, AA and AAA form a cumulative hierarchy, not three separate catalogs. Level A removes the most severe access barriers but is practically never sufficient as a standalone goal. Level AA adds the criteria that make the biggest difference for the broad majority of users, such as contrast, scalability and consistent navigation, and is exactly the standard referenced by the BFSG, EN 301 549 and the vast majority of international case law. Level AAA contains the strictest criteria, but according to the W3C itself is not intended as a complete, sitewide goal for every website.

The economically sensible strategy is therefore rarely "all or nothing": implement, test and document Level AA as the binding baseline, and selectively add individual AAA criteria wherever the benefit for a specific user group clearly outweighs the implementation effort, such as enhanced contrast on critical buttons or removing forced time limits. Anyone who documents this prioritization cleanly reliably meets the legal requirements while delivering noticeably more value than a bare-minimum Level A implementation.

11. FAQ: WCAG Conformance Levels A, AA, AAA