Study: AudioEye detects up to 2.5x more issues than other tools
Get ReportWCAG 2.1 Level AA: Who Needs to Follow It and Why
WCAG 2.1 Level AA is the technical standard that U.S. courts and the Department of Justice (DOJ) treat as the default measure of digital accessibility. If your website serves the U.S. public, it almost certainly applies to you. Learn more about WCAG requirements below.
Author: Missy Jensen, Senior SEO Copywriter
Published: 06/09/2026
)
“Do we have to be accessible?” is rarely the real question. Most organizations are aware that accessibility matters, but what they can’t pin down is whether the requirements legally bind them, or which standard they’re actually required to follow.
The answer comes down to who you are and who you serve as a business. WCAG, the Web Content Accessibility Guidelines published by the World Wide Web Consortium (W3C), defines what an accessible website looks like. The law determines who must meet it.
Below is a clean map of both: who must comply, which law puts them there, and why WCAG became the standard everyone points to.
WCAG Conformance Levels, Briefly
WCAG has three conformance levels. Level A covers the most basic requirements. Level AA adds the criteria that affect most users and is the level nearly every accessibility law references. Level AAA is the highest bar and is not expected across an entire site.
Put simply, Level AA is the standard organizations should aim for to meet compliance requirements.
WCAG 2.1 vs. 2.2, and Why 2.1 is Still the Floor
The most recent version of WCAG is WCAG 2.2. Most U.S. law still references WCAG 2.1 Level AA, so 2.1 AA is the binding floor today. That doesn't make 2.2 irrelevant. Meeting 2.2 satisfies 2.1, so building to the newer version improves your site's accessibility and gets ahead of future enforcement.
For more on what changed between versions, see our breakdown of WCAG 2.2.
Who Legally Needs WCAG 2.1 Level AA
Which law makes WCAG your standard depends on who you are and who you serve. Federal agencies and their vendors answer to Section 508. State and local governments must follow Title II of the Americans with Disabilities Act(opens in a new tab) (ADA). Private businesses open to the public are subject to Title III of the ADA. Most organizations fall under just one law, and that law determines which WCAG version you actually owe.
Federal Agencies and Contractors (Section 508)
Section 508 of the Rehabilitation Act requires federal agencies to make their digital technology accessible, and it extends to the vendors that sell to them as well. If you sell to a federal agency, accessibility conformance is part of the procurement process, usually demonstrated with a VPAT or conformance report.
One detail matters here: Section 508 requirements point to WCAG 2.0 Level AA, not 2.1. Plenty of agencies and vendors build to 2.1 or 2.2 anyway, since the newer versions handle mobile and modern interfaces, and one higher bar is easier to manage than several. As noted above, meeting 2.1 satisfies the requirements of 2.0; the legal floor Section 508 is still WCAG 2.0 Level AA.
For more information, check out our explainer on the ADA, Section 508, and WCAG.
State and Local Government (ADA Title II)
ADA Title II covers state and local governments. That includes cities, counties, public universities, K-12 districts, courts, libraries, and special districts. The DOJ’s 2024 Final Rule formally adopted WCAG 2.1 Level AA as the technical standard for the web content and mobile apps these entities provide.
Compliance deadlines were extended in April 2026. Entities with a population of 50,000 or more now have until April 26, 2027. Smaller entities and special districts have until April 26, 2028. The substantive requirement did not change; the standard is still WCAG 2.1 Level AA.
Businesses Open to the Public (ADA Title III)
Title III of the ADA covers private businesses open to the public. Retailers, restaurants, banks, healthcare providers, hotels, and most e-commerce sites fall into this category. Courts and the DOJ have repeatedly applied WCAG 2.1 Level AA as the benchmark in web accessibility cases. A private business with no government ties is still covered if it serves the public.
This is also where most accessibility lawsuits occur. Because Title III gives individuals a private right of action, web accessibility claims have become a steady category of litigation.
)
Why WCAG is the de Facto Standard
An important thing to note about the ADA: it does not name a technical standard. Instead, the DOJ and courts defaulted to WCAG 2.1 Level AA.
This is the distinction that can get confusing. WCAG is not a law. The ADA and Section 508 are laws. WCAG is the technical yardstick against which those laws are measured in practice.
For more on how the ADA and WCAG relate, see our breakdown of the differences between ADA and WCAG.
The Practical Path to WCAG 2.1 Level AA
Meeting WCAG standards takes more than a one-time scan. WCAG 2.1 Level AA has more than 70 success criteria, and a meaningful share of them cannot be detected by software. Automated tools are good at catching common issues, such as missing alt text, low contrast, or unlabeled form fields, and can do so continuously.
But automation can’t tell you whether your page works with a screen reader, whether every function is reachable by keyboard, or whether your link text makes sense in context. Those are judgment calls, and they need a human.
That is why the defensible path combines both automation and human expertise. Automation handles scale, scanning pages, and flagging issues as new content ships. Expert audits go deep, evaluating criteria that require real testing and lived experience with assistive technology. The combination is what holds up over time, because compliance is not a one-time state. It is something you maintain.
Conformance is Not a One-Time Checkbox
“Passing” a one-time accessibility audit is not the finish line. The harder part is maintaining it, when a complaint or procurement review puts your site under the microscope, and you have nothing but scattered scans and half-updated spreadsheets to point to.
AudioEye replaces that scramble with a single, living record. Expert Audits and AI-powered automation work together to find issues and deliver expert-written Custom Fixes, resolving up to 97% of issues. The work documents itself as it happens, so when someone asks you to show proof, it’s already there.
Stop scrambling for proof. See exactly where your site stands against WCAG guidelines, and get the documentation to back it up. Get started with a free scan.
Want to see AudioEye in action? Schedule a demo.
Frequently Asked Questions
Share Article
)
)
)