ADA Website Compliance

ADA website compliance means building and maintaining a website that people with disabilities can use — and that meets the standard U.S. courts rely on to judge accessibility under the Americans with Disabilities Act. In practice that standard is WCAG 2.1 Level AA, so users of screen readers, keyboards, and other assistive technology can complete every task.

What ADA website compliance means

The Americans with Disabilities Act (ADA) is a civil-rights law that prohibits discrimination against people with disabilities. It predates the modern web, so the law itself doesn’t list HTML rules. Instead, courts, regulators, and settlements have converged on one technical benchmark: the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C’s Web Accessibility Initiative.

In concrete terms, a compliant site works for:

• Someone using a screen reader like NVDA, JAWS, or VoiceOver, which reads the page aloud and relies on correct alt text, headings, and labels.
• Someone navigating by keyboard only — no mouse — who needs a logical focus order and visible focus styles.
• Someone with low vision who needs sufficient color contrast and text that resizes without breaking.
• Someone using voice control, switch devices, or other assistive technology.

Compliance is not a badge or a one-time scan. It’s a property of the code, content, and design working together so that nothing essential is locked behind a barrier.

Is ADA compliance legally required for websites?

This is the question every business owner actually asks, and the honest answer has nuance — so here it is straight, with no fabrication.

The ADA’s Title III prohibits discrimination by “places of public accommodation.” When the law was written, that meant physical spaces: stores, restaurants, hotels, clinics. The unsettled legal question is how far that language reaches onto the web.

• The DOJ position. The U.S. Department of Justice has stated repeatedly — including in published guidance on ada.gov — that the ADA applies to the websites of businesses open to the public. The DOJ has not, however, issued a final regulation that spells out a specific technical standard (like WCAG) for private businesses.
• The 2024 Title II rule. In 2024 the DOJ did finalize a rule under Title II requiring state and local governments to meet WCAG 2.1 AA on set deadlines. That rule covers government, not private business — but it’s the clearest signal yet of where federal expectations are heading, and it names WCAG 2.1 AA explicitly.
• The circuit split. Federal appeals courts disagree on the threshold question. Some circuits hold that a website is a public accommodation in its own right. Others require a “nexus” between the website and a physical location. Because the Supreme Court has not resolved this split, the answer can depend partly on where you are sued.

So: there is no single federal statute that says “your business website must meet WCAG.” But Title III has been applied to websites, the DOJ says the ADA covers the web, and thousands of ADA web lawsuits are filed annually — overwhelmingly against small and mid-sized businesses. For deeper context on how courts treat the law, see our overview of ADA website lawsuits.

If your website is how customers learn about, contact, or buy from you, it is exactly the kind of “public accommodation” plaintiffs target.

This is general information, not legal advice. For your specific situation, consult a qualified ADA defense attorney.

A related standard worth knowing: Section 508 of the Rehabilitation Act requires federal agencies and many of their contractors to make electronic content accessible, and it also points to WCAG. If you sell to government, Section 508 may apply on top of the ADA.

The lawsuit reality for small businesses

The myth is that web accessibility lawsuits hit big, careless corporations. The data points the other way. The typical defendant is a local retailer, restaurant, dental office, law firm, or independent ecommerce brand — businesses without an in-house accessibility team.

A few patterns hold steady year after year:

• There’s no revenue floor. A site doesn’t need heavy traffic to attract a filing — it needs a barrier and a plaintiff who finds it.
• Most disputes start as a demand letter, not a summons. A demand letter is a pre-litigation notice from a plaintiff’s attorney asking you to remediate and settle. It isn’t a court filing, but ignoring it is risky — it often precedes an actual lawsuit.
• Overlays don’t shield you. Businesses running popular accessibility overlay widgets have still been sued, in numbers that reach the hundreds in some years. Courts have not accepted overlays as a defense.

The common thread is simple: the claim has legs when a real person using a screen reader or keyboard can’t complete a meaningful task — buying, booking, or contacting you.

What WCAG 2.1 AA requires (the POUR principles)

WCAG is organized around four principles, remembered with the acronym POUR. Every individual success criterion rolls up into one of them. Here’s what each means in plain language, with concrete examples.

A few of these deserve a closer look because they’re where most sites fail:

• Alt text describes images so a screen reader can convey what a sighted user sees. Decorative images get empty alt; meaningful ones get a real description.
• Color contrast at AA requires a 4.5:1 ratio for normal text. Light-gray text on white is the single most common failure.
• Keyboard navigation means every interactive element — menus, modals, sliders, checkout steps — is reachable and usable with Tab, Enter, and arrow keys, with no traps.
• ARIA (Accessible Rich Internet Applications) attributes patch gaps in HTML for complex widgets, but misused ARIA often makes things worse than no ARIA at all. The rule of thumb: use native HTML first.

For a fuller walkthrough, see WCAG explained for business owners, the specific requirements of WCAG 2.1 AA, and a deeper dive into the POUR principles.

Conformance levels: A, AA, and AAA — and why AA

WCAG defines three conformance levels. Choosing the right target matters, because aiming too low leaves you exposed and aiming for the wrong ceiling wastes effort.

The takeaway: target Level AA. It’s the level regulators reference, the level plaintiffs measure you against, and the level that actually delivers a usable experience without demanding the impossible.

How to know if you’re at risk

You can’t fix what you can’t see, and most owners overestimate their site because the barriers are invisible to anyone not using assistive technology.

• Automated scanners are a useful first pass, but independent testing consistently shows they catch only an estimated 30–40% of real WCAG issues. They’re good at flagging missing alt attributes and low-contrast values; they’re blind to whether your checkout actually works with a keyboard or whether your alt text is meaningful.
• Manual testing is where real risk surfaces. A human operates the site with a screen reader and keyboard, confirming that each task can be completed start to finish. This catches the issues that actually drive lawsuits.

The reliable way to get a true picture is a proper website accessibility audit that combines both methods and produces a prioritized roadmap. Want a quick starting signal first? Run a free scan to see surface-level issues, or work through our ADA compliance checklist.

What real compliance requires (not overlays)

Here’s the hard truth that the industry’s marketing obscures: accessibility overlays do not make a site compliant.

An overlay is a script you paste into your site that layers a toolbar or widget on top — font-size buttons, contrast toggles, a one-line promise of instant ADA compliance. The problem is structural: an overlay sits on top of your code. It does not repair the underlying HTML, ARIA, labels, contrast, or focus order that screen readers and keyboards actually depend on.

The consequences are well documented:

• Businesses running overlays still get sued. Overlay-related cases have numbered in the hundreds in recent years.
• Many screen reader users distrust overlays and disable them on sight, because they often interfere with the assistive tech the user already has configured.
• Courts have not treated overlays as evidence of conformance.

The durable path is manual remediation — a human correcting the semantic structure, labels, contrast, focus order, and forms in the code itself, then verifying the fix with real assistive technology. We lay out the full evidence in do accessibility overlays work? and the alternative in accessibility remediation.

The remediation process, step by step

Genuine compliance follows a predictable arc. Skipping steps is how businesses end up “fixed” but still vulnerable.

1. Audit. Combine automated scanning with manual screen-reader and keyboard testing against WCAG 2.1 AA. The output is a prioritized list of findings, not a vague score. Start with a website accessibility audit.
2. Remediate. Fix the findings in the source code — semantic HTML, correct labels, contrast, focus management, accessible forms and components. This is manual remediation, not a widget.
3. Document. Produce a VPAT (Voluntary Product Accessibility Template) / Accessibility Conformance Report and publish an accessibility statement, so your good-faith conformance is on record.
4. Monitor. Sites change — new pages, new plugins, new campaigns. Ongoing checks catch new barriers before a plaintiff does.

Our ADA compliance services bundle these steps so you’re not managing four separate efforts.

What ADA compliance costs

There’s no honest fixed price, because cost is driven by your site, not a menu. The real drivers are:

• Size and complexity. A 10-page brochure site is a different job than a 5,000-SKU store with a custom checkout.
• How much is broken. A site built on accessible foundations needs lighter remediation than one with deep structural issues.
• Technology stack. Custom JavaScript apps and heavily templated sites can take more effort than a clean CMS theme.
• Documentation and monitoring. A one-time fix costs less than an ongoing program — but the ongoing program is what keeps you compliant as the site evolves.

The math worth internalizing: remediating proactively is almost always cheaper than getting a demand letter, paying to settle, and then paying to remediate anyway — because settling never makes the code accessible. See our full ADA compliance cost breakdown for how to budget realistically.

Platform and industry relevance

ADA expectations don’t change by platform — WCAG 2.1 AA is WCAG 2.1 AA whether you’re on Shopify, WordPress, Wix, Squarespace, or a custom build. What changes is where the common barriers live.

• Ecommerce sites (Shopify, WooCommerce, BigCommerce) tend to fail in checkout flows, product filters, and dynamic cart widgets — exactly the interactive paths that break for assistive technology. See Shopify ADA compliance.
• WordPress sites inherit accessibility from their theme and plugins, which vary wildly in quality; a single page builder or slider can introduce dozens of issues. See WordPress accessibility.
• Service businesses — restaurants, healthcare practices, law firms, real estate, hotels — are frequent targets because the inaccessible task (booking, contacting, ordering) is obvious and central.

No platform is automatically compliant out of the box, and none is hopeless. What matters is testing your actual site against the standard. A great resource for the broader practitioner community is WebAIM, whose research underpins much of how the field tests for real-world accessibility.

The bottom line for business owners

ADA website compliance comes down to one thing: can a real person using a screen reader or keyboard use your site to do what your customers do? The standard courts measure that against is WCAG 2.1 AA, the lawsuit risk falls hardest on small businesses, and overlays don’t protect you — real, manual conformance does.

The cheapest moment to act is before a demand letter arrives. Run a free accessibility scan to see where you stand, or talk to a human about a full audit and remediation plan.

Not legal advice. For guidance on a specific demand letter or lawsuit, consult a qualified ADA defense attorney.