← Back to Blog

Understanding WCAG Conformance Levels: A, AA, and AAA

If you're working on web accessibility, you've probably heard about "WCAG Level AA" or similar terms. But what do these levels actually mean, and which one should you target? Let's break it down.

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines. Developed by the World Wide Web Consortium (W3C), these guidelines provide a shared standard for making web content accessible to people with disabilities.

The current version is WCAG 2.1, though WCAG 2.2 was recently released. Most legal requirements and organizational policies reference WCAG 2.1.

The Three Conformance Levels

WCAG success criteria are organized into three levels of conformance:

Level A: The Basics

Level A includes the most fundamental accessibility requirements. Without these, some users literally cannot access your content at all.

Examples of Level A requirements:

  • All images have alternative text
  • Videos have captions (prerecorded)
  • Pages have descriptive titles
  • Links can be distinguished from surrounding text
  • Content can be accessed using only a keyboard

Think of Level A as: The minimum to make your site usable at all for users with disabilities.

Level AA: The Standard Target

Level AA includes everything in Level A plus additional requirements that address more barriers. This is the level most commonly referenced in accessibility policies, laws, and regulations.

Examples of Level AA requirements:

  • Color contrast ratios of at least 4.5:1 for normal text
  • Text can be resized up to 200% without loss of functionality
  • Multiple ways to navigate the site (search, sitemap, etc.)
  • Form inputs have visible labels
  • Error messages identify the specific field with the error

Think of Level AA as: A reasonably accessible experience for most users with disabilities.

Level AAA: The Gold Standard

Level AAA includes the most stringent requirements. While admirable to achieve, WCAG itself notes that it may not be possible to satisfy all Level AAA criteria for all content types.

Examples of Level AAA requirements:

  • Color contrast ratios of at least 7:1 for normal text
  • Sign language interpretation for video content
  • Extended audio descriptions
  • No timing limits on user interactions
  • Simplified content alternatives

Think of Level AAA as: Enhanced accessibility for specific user needs or content types.

Which Level Should You Target?

For most organizations, Level AA is the right target.

Here's why:

  • Legal requirements: Most accessibility laws and regulations reference WCAG 2.1 Level AA
  • Industry standard: It's what courts, regulators, and accessibility professionals typically expect
  • Achievable: Unlike AAA, Level AA conformance is realistic for most websites
  • Meaningful impact: AA addresses the most common and significant barriers

A Note on "Conformance"

Technically, WCAG conformance is all-or-nothing for a given level. To claim "Level AA conformance," every applicable success criterion must be met.

In practice, most organizations aim for Level AA as a target while acknowledging they may not achieve perfect conformance on every page. What matters is demonstrating good faith effort and continuous improvement.

How to Prioritize

If you're just starting your accessibility journey, here's a practical approach:

  1. Start with Level A: Address the most fundamental barriers first
  2. Move to Level AA: Work through the additional requirements systematically
  3. Consider AAA selectively: Implement AAA criteria where they're most valuable for your users

Within each level, prioritize based on user impact. Fixing a keyboard trap (which completely blocks some users) is more urgent than perfecting color contrast ratios.

Beyond Conformance

Remember that WCAG conformance is a floor, not a ceiling. The goal isn't to check boxes—it's to create genuinely usable experiences for people with disabilities.

User testing with people who have disabilities will often reveal issues that automated testing and WCAG audits miss. The guidelines are valuable, but they're not a substitute for understanding your users' actual experiences.