Level Access

WCAG Conformance Levels: How High Should You Aim?

Read the original on levelaccess.com ↗

WCAG has three conformance levels: Level A (minimum), Level AA (the common legal benchmark), and Level AAA (highest). Most organizations should target AA, adding relevant AAA criteria.

Which Web Content Accessibility Guidelines (WCAG) conformance level does your organization actually need to meet? It’s one of the most common questions teams ask when they’re getting started with digital accessibility. The answer shapes how you test, how you design, and even how you choose vendors.

The three WCAG levels build on each other: Each level includes every requirement of the levels below it. So, choosing a target is less about picking a tier and more about deciding how far to go. And that decision can hinge on many factors, including your legal or procurement obligations, your users, and your own organizational priorities and resources.

In this blog, we’ll explore what meeting each WCAG level involves, with real examples from WCAG 2.2. You’ll also learn which levels major laws reference, why there’s no such thing as “ADA compliance levels,” and how to test and document your conformance.

Key insights

  • WCAG has three cumulative conformance levels. Level A covers the most fundamental barriers, Level AA builds on it, and Level AAA is the highest level achievable, providing access for the broadest group of users.
  • Level AA is the right target for most organizations. The World Wide Web Consortium (W3C) doesn’t recommend full Level AAA conformance for entire sites, because not all of the criteria can be applied to all situations. However, individual AAA criteria are often worth adopting where applicable.
  • The Americans with Disabilities Act (ADA) doesn’t define compliance levels. However, WCAG 2.1 Level AA is required by the U.S. Department of Justice’s (DOJ) ADA Title II rule, and WCAG Level AA is also the de facto benchmark for ADA Title III.
  • The Department of Health and Human Services’ (HHS) rule under Section 504 of the Rehabilitation Act mandates WCAG 2.1 AA conformance for HHS funding recipients. Federal agencies must conform to WCAG 2.0 AA to comply with Section 508.
  • Most current regulations treat WCAG 2.0 or 2.1 AA as the legal floor, while WCAG 2.2 AA is a best practice to future-proof compliance and meet a wider range of user needs.
  • Conformance applies to full pages and complete processes, so proving it takes a mix of automated and manual testing, with clear documentation.

What is WCAG? A quick primer on the standard

WCAG is the international technical standard for digital accessibility, published by the W3C’s Web Accessibility Initiative (WAI). Importantly, WCAG is a standard, not a law. That’s why we use the term “WCAG conformance” rather than “WCAG compliance.” However, many laws and regulations, including the DOJ’s ADA Title II rule, Section 508 of the Rehabilitation Act, and EN 301 549 (the standard organizations use to meet the European Accessibility Act) reference WCAG.

WCAG versions

The W3C has published several different versions of WCAG over the years. Here’s how the versions have evolved:

  • WCAG 1.0 (1999): The earliest version of WCAG, no longer in use.
  • WCAG 2.0 (2008): Established the three conformance levels and the success criteria that still form the foundation of the standard.
  • WCAG 2.1 (2018): Added 17 success criteria, many focused on mobile, low vision, and cognitive accessibility.
  • WCAG 2.2 (October 2023): Added nine success criteria and removed 4.1.1 Parsing, for a total of 86 across A, AA, and AAA, with 55 required for Level AA conformance. It’s the current version.

Each version builds on the last. According to the W3C, content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0.

The POUR principles

The success criteria in WCAG 2 are organized under four principles, often referred to with the acronym “POUR”:

  • Perceivable: Information is available to users in a way they can perceive with their senses.
  • Operable: Users can operate navigation and controls, including with the keyboard or assistive technology.
  • Understandable: Content and interface behavior are clear and predictable.
  • Robust: Content works reliably across browsers, devices, and current and future assistive technologies.

The three WCAG conformance levels explained

WCAG assigns every success criterion to one of three conformance levels: A, AA, and AAA. Level A represents the baseline for web accessibility, with each consecutive level including and then building on the previous level. As the W3C explains in its guidance on conformance, this means that a page that conforms at Level AA satisfies all Level A and Level AA success criteria. Level AAA conformance requires meeting all A, AA, and AAA success criteria.

Here’s what each level involves in practice, with examples from WCAG 2.2.

Level A: The minimum

Level A addresses the most fundamental barriers—the issues that are most likely to block access for many users with disabilities. It’s a baseline, not a finish line. Content that meets only Level A can still have significant accessibility problems.

Examples of Level A criteria include:

  • Non-text content (1.1.1): Images, icons, and other non-text content need text alternatives, so screen reader users get the same information as everyone else.
  • Use of color (1.4.1): Color can’t be the only way you convey meaning. If links in body text are distinguished only by blue text, for instance, adding an underline gives users a second cue.
  • Captions (prerecorded) (1.2.2): Prerecorded video with audio, which WCAG calls synchronized media, needs captions. This requirement goes back to WCAG 2.0.

Level AA: The benchmark for most organizations

Level AA builds on Level A with requirements that remove common barriers for a much wider range of users. It’s the level that’s most commonly referenced by legal requirements, and it’s the target Level Access recommends for most organizations.

Examples of Level AA success criteria include:

  • Contrast (minimum) (1.4.3): Normal text needs a contrast ratio of at least 4.5:1 against its background. Large text (at least 18 point, or 14 point bold) needs at least 3:1. Light blue links on a pale blue background often fall short. You can test your color pairs with our free color contrast checker.
  • Audio description (prerecorded) (1.2.5): Prerecorded video needs audio description of important visual details that the soundtrack doesn’t already convey.
  • Target size (minimum) (2.5.8): New in WCAG 2.2, this criterion sets a minimum size of 24 by 24 CSS pixels for interactive targets such as buttons and links. Some exceptions apply.

Level AAA: The highest achievable level

Level AAA is the highest level of WCAG conformance, ensuring access for the broadest possible group of users. These criteria offer real benefits, but meeting them isn’t always practical or achievable.

Examples include:

  • Contrast (enhanced) (1.4.6): Normal text needs a contrast ratio of at least 7:1, and large text needs at least 4.5:1. The W3C chose 7:1 to compensate for the contrast sensitivity loss typically associated with vision of about 20/80. That helps more people with low vision read text without assistive technology.
  • Sign language (prerecorded) (1.2.6): Prerecorded video with audio needs sign language interpretation.
  • Low or no background audio (1.4.7): Prerecorded audio that’s mostly speech needs to meet one of three conditions, with some exceptions. It can have no background sounds, background sounds users can turn off, or background sounds at least 20 decibels quieter than the speech.

WCAG A vs. AA vs. AAA compared

Here’s how the three levels compare side by side.

Level What it covers Example criteria WCAG 2.2 success criteria Where it’s required
Level A The most fundamental barriers, which can block access entirely Non-text content, use of color, captions (prerecorded) 31 Every law or policy that references Level AA, because the levels are additive
Level AA Common barriers that affect a wide range of users Contrast (minimum), audio description (prerecorded), target size (minimum) 24 (55 total, including Level A) ADA Title II (DOJ rule), Section 508, Section 504 (HHS rule), AODA, ACA, and most other laws referencing WCAG or related standards (e.g., EN 301 549).

Note: Different laws reference different WCAG versions.

Level AAA Enhanced requirements for specific needs and content types Contrast (enhanced), sign language (prerecorded), low or no background audio 31 (86 total, including Levels A and AA) No major law requires full Level AAA conformance.

WCAG AA vs. AAA: Which level should you aim for?

For most organizations, the answer is WCAG Level AA.

Level AAA might seem like the obvious choice. If AA is good, isn’t AAA better? In principle, yes. In practice, the W3C itself doesn’t recommend requiring Level AAA conformance as a general policy for entire sites. Some content simply can’t satisfy every AAA criterion.

Low or no background audio (1.4.7) is a good example. If you have an archive of recorded podcasts with music under the speech, you may not be able to remix every episode. You can still meet Level A and AA requirements for that content, though, such as providing transcripts for audio-only recordings and captions for video.

Key differences between WCAG AA and AAA

To help you better understand whether to aim for Level AA or AAA, here are a few practical examples of how the two levels differ:

  • Scope: Level AA is realistic across an entire website or app. Full Level AAA is often realistic only for specific pages or content types.
  • Contrast: Level AA requires 4.5:1 for normal text and 3:1 for large text. Level AAA raises those to 7:1 and 4.5:1.
  • Media: Level AA adds live captions and audio description to the captions required at Level A. Level AAA adds sign language, extended audio description, and full text alternatives for video.

Where to target WCAG AAA conformance

Just because AAA isn’t always practical or achievable doesn’t mean it has no place in your accessibility work. A smarter approach than site-wide conformance is selective AAA: target Level AA across the board, then adopt individual AAA criteria where they fit your content and your users. For example:

  • High-stakes tasks: A benefits portal where users complete critical applications might adopt certain AAA criteria to ensure its core forms are barrier-free.
  • Key video content: An organization producing new training videos could add sign language interpretation to its most important modules.
  • Complex information: A health or financial services site might apply the reading level guidance in 3.1.5 to explanations of policies and terms.
  • Enhanced contrast: A product team might adopt success criterion 1.4.6, enhanced contrast, for its design system.

Are there ADA compliance levels?

No. The ADA doesn’t define compliance or conformance levels. When people search for “ADA compliance levels,” they usually mean WCAG levels. That’s because WCAG is the technical standard used to measure digital accessibility under the ADA and many other laws. You may also find them called “WCAG compliance levels.”

Here’s which WCAG version and level each major law references.

Law or regulation Who it applies to WCAG version and level Key dates
ADA Title II (DOJ rule) U.S. state and local governments WCAG 2.1 Level AA April 26, 2027, for public entities with a total population of 50,000 or more; April 26, 2028, for smaller entities and special district governments
ADA Title III Businesses open to the U.S. public No technical regulation; WCAG Level AA is the de facto benchmark No set compliance date
Section 508 of the Rehabilitation Act U.S. federal agencies; specifically, the information and communication technology (ICT) they develop, buy, maintain, or use WCAG 2.0 Level AA In effect since January 18, 2018
Section 504 of the Rehabilitation Act (HHS rule) Recipients of federal financial assistance from the U.S. Department of Health and Human Services (HHS), such as hospitals, clinics, and Medicaid providers WCAG 2.1 Level AA May 11, 2027, for recipients with 15 or more employees; May 10, 2028, for recipients with fewer than 15 employees
European Accessibility Act (EAA) Covered products and services provided to consumers in the European Union (EU) EN 301 549: V3.2.1 references WCAG 2.1 Level AA; V4.1.1 aligns with WCAG 2.2 Level AA EAA has applied since June 28, 2025; EN 301 549 V4.1.1 published September 2, 2026

Note: EN 301 549 V4.1.1 provides a presumption of conformity under the EAA only once it’s cited in the EU’s Official Journal.

Accessibility for Ontarians with Disabilities Act (AODA) Ontario public-sector organizations, plus businesses and nonprofits with 50 or more employees in Ontario WCAG 2.0 Level AA, except success criteria 1.2.4 Captions (Live) and 1.2.5 Audio Description (Prerecorded) In effect since January 1, 2021, for all websites and web content
Accessible Canada Act (ACA) Canadian federal public-sector entities and federally regulated private-sector organizations, such as banks, with 100 or more employees CAN/ASC-EN 301 549:2024, which references WCAG 2.1 Level AA December 5, 2027, for most federal public-sector requirements; December 5, 2028, for private-sector organizations

The bottom line? WCAG 2.0 or 2.1 Level AA is the legal floor in most current regulations. WCAG 2.2 Level AA is best practice, since it includes every WCAG 2.1 Level AA requirement and Europe is moving to it.

Conformance vs. compliance

These terms often get used interchangeably, but they mean different things. Conformance means meeting a technical standard like WCAG. Compliance means meeting a legal obligation like the ADA or the EAA. WCAG conformance is the strongest way to support legal compliance, but it doesn’t automatically equal it. Laws can include obligations beyond WCAG, such as deadlines, procurement rules, or accessibility statements.

How to reach and prove WCAG conformance

Choosing a target level is the first step. Reaching it, and proving it, takes a structured approach. Here’s what to keep in mind.

Conformance covers full pages and complete processes

The W3C’s conformance requirements apply to full web pages only. You can’t claim conformance by excluding part of a page. If a page is part of a process, every page in that process must conform. One inaccessible step in a checkout flow, for example, means the whole flow doesn’t conform at that level.

Partial conformance has limits

Sometimes content outside your control, like third-party content, prevents a page from conforming. In that case, the W3C allows a statement of partial conformance. Keep in mind that it’s a statement of non-conformance for that content. You’ll still need to monitor it, since content that changes can stop conforming.

Automated and manual testing work best together

Automated scanning finds many common issues quickly and at scale, which makes it ideal for ongoing monitoring. However, many success criteria need human judgment. Is the alt text meaningful? Does the focus order make sense? Can a screen reader user complete a multistep form? Expert manual testing answers those questions. Level Access accessibility audits, for example, pair automated scanning with manual evaluations by accessibility experts. That gives you a complete picture of conformance against the WCAG version and level you choose.

Documentation proves conformance to buyers

If you sell software or digital services, buyers will ask for evidence. A Voluntary Product Accessibility Template (VPAT®) is the standard format for that evidence. Once completed, it becomes an Accessibility Conformance Report (ACR). The ACR documents how your product meets each WCAG success criterion, along with any additional requirements from other relevant standards, such as Section 508 or EN 301 549.

Make WCAG 2.2 Level AA your target

WCAG’s three levels give you a clear path forward. WCAG 2.0 or 2.1 Level AA is the floor most current regulations set. WCAG 2.2 Level AA is best practice. It includes every WCAG 2.1 Level AA requirement, adds criteria for focus, target size, and authentication, and matches where Europe is heading. From there, you can adopt individual AAA criteria where they serve your users.

For more than 25 years, Level Access has helped organizations reach and document WCAG conformance. Our expert testing, guidance, and reporting support every stage of your accessibility program. For a head start, explore our WCAG 2.2 AA summary and checklist. When you’re ready to find out where your digital properties stand, request an accessibility audit today.

The post WCAG Conformance Levels: How High Should You Aim? appeared first on Level Access.