A vs AA vs AAA: WCAG Conformance Levels Explained (2024)

Skip to main content

Login

Help CenterOpens in a new tabLogin

LoginOpens in a new tab

Understanding the Difference Between WCAG A, AA, and AAA Conformance

  • Essential Conformance: WCAG A vs. AA vs. AAA
  • WCAG AA vs. AAA: What Level of WCAG Conformance is Recommended?
  • How Do You Test Content for WCAG Level AA Conformance?

A vs AA vs AAA: WCAG Conformance Levels Explained (3)

Back to blog

Posted July 15, 2024

AudioEye Posted July 15, 2024

Ready to see AudioEye in action?

Watch Demo

WCAG Level A, AA, and AAA conformance each have their own set of accessibility criteria that enhance digital accessibility for individuals with disabilities. Each one also has its own degree of strictness. In this post, you will learn more about the differences between each WCAG conformance level.

Originally published June 23, 2022

Digital accessibility has become an integral part of new technologies, and innovators are ensuring that new tools can be used by individuals with disabilities.

To help further accessibility, the World Wide Web Consortium (W3C) created the Web Content Accessibility Guidelines (WCAG), a set of standards for improving the online experience for individuals with disabilities. The guidelines are divided into three levels of conformance to show how well a site meets accessibility standards.

Below, we’ll discuss the differences between each WCAG conformance level and the standards each one includes. We’ll also explain which conformance level you should strive for to comply with accessibility laws and provide an accessible, inclusive experience for users.

A vs AA vs AAA: WCAG Conformance Levels Explained (9)

A vs AA vs AAA: WCAG Conformance Levels Explained (10)

A large box with the term Level AA and two small boxes with the terms Level A and Level AA

Essential Conformance: WCAG A vs. AA vs. AAA

WCAG guidelines are designed to make the internet more accessible and usable for people of all disabilities. Following the guidelines helps you stay compliant with non-discrimination laws, such as the Americans with Disabilities Act (ADA), the European Accessibility Act (EAA), the Accessibility for Ontarians with Disabilities Act (AODA), and other accessibility laws.

The guidelines are based on four main principles: Content must be perceivable, operable, understandable, and robust (also known as the POUR principles).

Success criteria are categorized into three levels of conformance:

  • WCAG Level A: The minimum level of conformance, Level A contains basic success criteria for removing serious accessibility barriers that affect a wide range of users.
  • WCAG Level AA: Level AA removes additional barriers and establishes a level of accessibility that works for most devices and assistive technologies, such as screen readers.
  • WCAG Level AAA: The most strict level of conformance, Level AAA contains additional success criteria to establish the highest possible level of website accessibility.


Each WCAG level builds on the previous level. In other words, to meet the requirements of Level AA, your content needs to follow all Level A and Level AA success criteria. To meet WCAG Level AAA, you’d need to follow all the success criteria included in the WCAG guidelines.

WCAG A vs. AA: What Accessibility Issues are Covered?

To help you understand the differences between each WCAG conformance level, let’s take a closer look at the differences between Level A and Level AA.

Level A is considered the least strict conformance level. It includes success criteria that help you avoid the most serious of accessibility issues that can prevent users with disabilities from effectively using digital content. Some of these criteria include:

  • Keyboard commands and shortcuts that allow users to navigate digital content by a keyboard alone.
  • Alternative text (alt text) is provided for images or other non-text content.
  • Forms include clear labels or instructions on how to complete them correctly.
  • Digital content is optimized for assistive technologies, including screen readers.
  • Information is not portrayed through color alone.

Examples of WCAG 2.1 Level AA Success Criteria

Level AA builds on the success criteria included in Level A and enhances accessibility for users in various contexts. Level AA includes 20 additional criteria to provide a better experience for users with disabilities. These criteria cover essential user experience (UX) issues, such as:

  • Maintaining — at minimum — a color contrast ratio of 4.5:1 between text and background elements.
  • Writing subheadings that are organized logically (i.e., H1, H2, H3, etc.).
  • Keeping navigation mechanisms (such as header and footer links) consistent from page to page.
  • Ensuring content is operable in different display orientations.
  • Providing captions for video content.
  • Ensuring content is fully operable for keyboard users.

A vs AA vs AAA: WCAG Conformance Levels Explained (11)

A vs AA vs AAA: WCAG Conformance Levels Explained (12)

Examples of accessibility criteria such as closed captions and alt text

WCAG AA vs. AAA: What Level of WCAG Conformance is Recommended?

The W3C recommends conforming to WCAG 2.1 Level AA. Websites that follow all Level AA success criteria are generally considered accessible for most users with disabilities. For example, in public statements and settlement agreements, the U.S. Department of Justice has referenced WCAG Level AA as a reasonable standard for following the accessibility requirements of the ADA. More simply, Level AA success criteria can help you stay compliant with the law.

As mentioned above, WCAG Level AAA is considered the most strict conformance level. The success criteria included in this level are more technical and detailed. For example, Success Criterion 2.5.5 Target Size recommends a target size of 44 by 44 CSS pixels except when the user agent or the target predetermines the target size in a sentence or block of text. Another example is Success Criterion 2.3.3 Animation from Interactions which allows users to disable animations on a web page.


Both success criteria mentioned above are not required for Level AA conformance. Rather, they’re capabilities that further enhance accessibility and usability for users with disabilities.

Should You Ignore WCAG Level AAA Guidelines?

Some types of content cannot conform with certain Level AAA success criteria, and WCAG 2.1 does not recommend Level AAA conformance as a general policy for entire websites.

More simply, if your goal is WCAG Level AA conformance, Level AAA recommendations are optional. However, following Level AAA guidance may make your website more operable for some people with disabilities. Since the ultimate goal of accessibility is to provide the best experience for users, it’s a good idea to follow Level AAA requirements wherever possible.

One important note: Disabilities impact people in a variety of ways, and even if a site fully conforms with WCAG 2.1 Level AAA, it may not be fully accessible to every individual user. When prioritizing accessibility remediations, remember that Level A and Level AA criteria will more noticeably affect your site’s overall accessibility.

A vs AA vs AAA: WCAG Conformance Levels Explained (13)

A vs AA vs AAA: WCAG Conformance Levels Explained (14)

An internet browser showing warning messages and a magnifying glass

How Do You Test Content for WCAG Level AA Conformance?

If you’re looking to test your digital content for WCAG conformance, there are two main approaches: you can test your content against WCAG success criteria yourself or use accessibility testing tools.

Automated Accessibility Testing

Automated accessibility testing involves using accessibility testing tools to automatically scan your digital content for WCAG violations. Most tools will scan your content’s code to find common accessibility issues and flag them in a report.

While automated accessibility testing can save you time, it does have some limitations — the biggest one being that automated tools can only test for common WCAG violations. More complex issues — ones that can significantly impact the user experience — may only be identified through manual testing.

For example, automated tools can check images to see if images include alt text. However, these tools can’t report on the quality of the alt text and whether it’s actually helpful to users.

Manual Accessibility Testing

As we mentioned above, automated testing does have its limitations. Manual testing helps to address accessibility barriers that software alone can’t detect — and helps you determine if your content is actually usable by individuals with disabilities. The process usually tests for accessibility features like keyboard-only commands, screen reader compatibility, alt text accuracy, appropriate heading and subheading order, and more.

The biggest drawback to manual accessibility testing is that it can be time-consuming, expensive, and only provides a snapshot of your site’s accessibility. That snapshot can quickly become outdated as every time you publish new content, you’ll have to re-test for accessibility.

It also requires some technical expertise and an in-depth understanding of WCAG success criteria. Having individuals with disabilities test your digital content for accessibility can help streamline the process, but it can still take time to review all your digital content for accessibility.


At AudioEye, we recommend using a combination of manual and automated testing to audit your site for WCAG 2.1 conformance. Doing so allows you to enjoy the speed of automation and the expertise of human testers. We use this hybrid approach in our own approach by leveraging the experience of the industry’s leading accessibility experts with the power of technology. This allows us to find — and fix — many common WCAG violations automatically while our team of experts identifies more complex accessibility issues.

Start By Scanning Your Website for WCAG Issues

Globally, about 1 billion people live with disabilities, and if your website isn’t accessible, you’re missing an opportunity to connect with potential visitors. When your content meets WCAG 2.1 conformance, you’ll enjoy the substantial benefits of digital accessibility — including a much wider audience, better user interactions, and even improved search engine optimization (SEO).

Take the first step to WCAG conformance and identify the most common WCAG criteria that your websGlobally, about 1.3 billion people have a disability. If your website isn’t accessible, you’re missing a chance to connect with users. If your digital content meets WCAG 2.1 conformance standards, you expand the reach of your customer base. Plus, you create a more usable environment for all users, regardless of their ability.


Ready to take the first step towards WCAG conformance? Get started by identifying common accessibility issues using AudioEye’s free Website Accessibility Checker. Enter your URL below to get started.

Frequently asked questions

WCAG is designed to make digital content more accessible for individuals with disabilities. The guidelines include a number of success criteria that help remove accessibility barriers that prevent users with disabilities from easily accessing or using digital content.

WCAG was created by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). The organization regularly reviews the guidelines and makes updates as needed.

WCAG is divided into four principles: Perceivable, Operable, Understandable, and Robust. These principles are incorporated into success criteria, which are testable statements that website owners can use to determine whether content is accessible for users with disabilities.

Adhering to WCAG guidelines ensures individuals with disabilities can use and access digital content. Additionally, WCAG Level AA is the globally accepted standard for digital accessibility. Failing to follow the guidelines can result in legal action, including lawsuits or demand letters, which can be expensive and reputation-damaging.

While WCAG is considered to be a voluntary set of standards, the Department of Justice and other government agencies worldwide have mandated WCAG 2.1 Level AA as mandatory for organizations. Failure to adhere to WCAG standards can result in legal action.

The biggest difference between WCAG 2.0 and 2.2 is the number of success criteria they include. Version 2.0 includes more than 60 success criteria, while version 2.2 has close to 90.

Ready to see AudioEye in action?

Watch Demo

Ready to test your website for accessibility?

Scan your website now.

Share post

Keep Reading

  • A vs AA vs AAA: WCAG Conformance Levels Explained (15)

    Can software help your organization comply with Section 508? Here’s an overview.

    compliance

    September 09, 2024

  • A vs AA vs AAA: WCAG Conformance Levels Explained (16)
    WCAG 3.0 and the Future of Accessibility Standards

    Here's what you need to know about WCAG 3.0, from its release date to its impact on the future of web accessibility standards.

    compliance

    September 07, 2024

  • A vs AA vs AAA: WCAG Conformance Levels Explained (17)
    Does My Website Have to Be ADA Compliant?

    Unsure about ADA website compliance? Discover why and how to make your site accessible and inclusive for all.

    compliance

    August 27, 2024

Solutions

  • AudioEye Plans
  • Digital Accessibility Platform
  • Developer Tools
  • Trusted Certification
  • AudioEye Assurance
  • Expert Audit
  • Accessibility Training
  • AudioEye Plans
  • Digital Accessibility Platform
  • Developer Tools
  • Trusted Certification
  • AudioEye Assurance
  • Expert Audit
  • Accessibility Training

Company

  • About Us
  • Investor RelationsOpens in a new tab
  • Partner Program
  • AudioEye® A11iance Team
  • Careers
  • Blog
  • Press Center
  • Case Studies
  • Our Accessibility Statement
  • Our Trusted Certification
  • Security Commitment
  • About Us
  • Investor RelationsOpens in a new tab
  • Partner Program
  • AudioEye® A11iance Team
  • Careers
  • Blog
  • Press Center
  • Case Studies
  • Our Accessibility Statement
  • Our Trusted Certification
  • Security Commitment

Guidance

  • WCAG 2.2 Compliance
  • WCAG A, AA, AAA
  • ADA Compliance
  • ADA Compliance Checklist
  • Does My Site Have To Be ADA Compliant?
  • ADA vs Section 508 Compliance
  • Section 508 Compliance
  • AODA Compliance
  • WCAG 2.2 Compliance
  • WCAG A, AA, AAA
  • ADA Compliance
  • ADA Compliance Checklist
  • Does My Site Have To Be ADA Compliant?
  • ADA vs Section 508 Compliance
  • Section 508 Compliance
  • AODA Compliance

Accessibility

  • What Is Digital Accessibility?
  • Accessible Web Design Guide
  • Web Accessibility Checklist
  • Building for Digital Accessibility at Scale
  • How to Choose a Web Accessibility Platform for Agencies
  • Making Accessibility Visible
  • 15 Stats on the Importance of Web Accessibility
  • What Is Digital Accessibility?
  • Accessible Web Design Guide
  • Web Accessibility Checklist
  • Building for Digital Accessibility at Scale
  • How to Choose a Web Accessibility Platform for Agencies
  • Making Accessibility Visible
  • 15 Stats on the Importance of Web Accessibility

Support

  • Help CenterOpens in a new tab
  • LoginOpens in a new tab
  • System StatusOpens in a new tab
  • Contact Us
  • Schedule A Demo
  • Request Legal Support
  • Request Partner SupportOpens in a new tab
  • Apply to Become a Partner
  • Technical DocumentationOpens in a new tab
  • Help CenterOpens in a new tab
  • LoginOpens in a new tab
  • System StatusOpens in a new tab
  • Contact Us
  • Schedule A Demo
  • Request Legal Support
  • Request Partner SupportOpens in a new tab
  • Apply to Become a Partner
  • Technical DocumentationOpens in a new tab
  • Terms of Service
  • Privacy Policy
  • Trust CenterOpens in a new tab
  • Cookie Settings

Copyright ©2024 AudioEye, Inc. All rights reserved. AUDIOEYE is a U.S. registered trademark of AudioEye, Inc. The products of AudioEye are protected by patents. For additional information, visit our intellectual property page or contact us via email.

A vs AA vs AAA: WCAG Conformance Levels Explained (2024)
Top Articles
Who is entitled to disability benefits?
is it possible to see the private key of a certificate ? ( i mean a computer's private key )
English Bulldog Puppies For Sale Under 1000 In Florida
Katie Pavlich Bikini Photos
Gamevault Agent
Pieology Nutrition Calculator Mobile
Hocus Pocus Showtimes Near Harkins Theatres Yuma Palms 14
Hendersonville (Tennessee) – Travel guide at Wikivoyage
Doby's Funeral Home Obituaries
Compare the Samsung Galaxy S24 - 256GB - Cobalt Violet vs Apple iPhone 16 Pro - 128GB - Desert Titanium | AT&T
Vardis Olive Garden (Georgioupolis, Kreta) ✈️ inkl. Flug buchen
Craigslist Dog Kennels For Sale
Things To Do In Atlanta Tomorrow Night
Non Sequitur
Crossword Nexus Solver
How To Cut Eelgrass Grounded
Pac Man Deviantart
Alexander Funeral Home Gallatin Obituaries
Shasta County Most Wanted 2022
Energy Healing Conference Utah
Testberichte zu E-Bikes & Fahrrädern von PROPHETE.
Aaa Saugus Ma Appointment
Geometry Review Quiz 5 Answer Key
Icivics The Electoral Process Answer Key
Allybearloves
Bible Gateway passage: Revelation 3 - New Living Translation
Yisd Home Access Center
Home
Shadbase Get Out Of Jail
Gina Wilson Angle Addition Postulate
Celina Powell Lil Meech Video: A Controversial Encounter Shakes Social Media - Video Reddit Trend
Walmart Pharmacy Near Me Open
Marquette Gas Prices
A Christmas Horse - Alison Senxation
Ou Football Brainiacs
Access a Shared Resource | Computing for Arts + Sciences
Vera Bradley Factory Outlet Sunbury Products
Pixel Combat Unblocked
Cvs Sport Physicals
Mercedes W204 Belt Diagram
'Conan Exiles' 3.0 Guide: How To Unlock Spells And Sorcery
Teenbeautyfitness
Where Can I Cash A Huntington National Bank Check
Topos De Bolos Engraçados
Sand Castle Parents Guide
Gregory (Five Nights at Freddy's)
Grand Valley State University Library Hours
Holzer Athena Portal
Hello – Cornerstone Chapel
Stoughton Commuter Rail Schedule
Selly Medaline
Latest Posts
Article information

Author: Tyson Zemlak

Last Updated:

Views: 5847

Rating: 4.2 / 5 (63 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Tyson Zemlak

Birthday: 1992-03-17

Address: Apt. 662 96191 Quigley Dam, Kubview, MA 42013

Phone: +441678032891

Job: Community-Services Orchestrator

Hobby: Coffee roasting, Calligraphy, Metalworking, Fashion, Vehicle restoration, Shopping, Photography

Introduction: My name is Tyson Zemlak, I am a excited, light, sparkling, super, open, fair, magnificent person who loves writing and wants to share my knowledge and understanding with you.