Is Your Website ADA Compliant? The 2026 Guide

If you sell anything online, someone has probably told you your website needs to be “ADA compliant.” They’re mostly right — but almost everything around that phrase is muddled, and the confusion is exactly what fuels both opportunistic lawsuits and useless overlay subscriptions. This guide cuts through it: what the law actually says in 2026, what standard you’re held to, and the concrete steps that move you from exposed to defensible.

Is website accessibility actually required by the ADA?

The Americans with Disabilities Act (1990) never mentions websites — the web barely existed. But Title III of the ADA prohibits discrimination by “places of public accommodation,” and for two decades courts have increasingly held that a business’s website is part of that public accommodation. The Department of Justice has repeatedly affirmed this position, and in 2024 it issued a final rule formally adopting WCAG 2.1 Level AA as the technical standard for state and local government websites under Title II.

For private businesses (Title III), there is still no single federal regulation spelling out a pixel-level standard — and that ambiguity is the whole problem. Courts fill the gap by pointing to the same place everyone else does: the Web Content Accessibility Guidelines.

What standard do I have to meet?

In practice, target WCAG 2.1 Level AA at minimum, and treat WCAG 2.2 AA as the direction of travel (2.2 is the current version and adds criteria around focus visibility, dragging, and target size). Settlement agreements and demand letters routinely name WCAG 2.1 AA specifically. If you conform to 2.2 AA, you exceed what nearly every demand letter asks for.

We keep a plain-English breakdown of every criterion in our WCAG 2.2 checklist — it’s the fastest way to see what “AA” actually involves without reading the spec.

Who has to comply

• E-commerce and retail — the single most-targeted category (~70% of web accessibility suits).
• Any business with a physical location whose website connects to goods or services (restaurants, clinics, banks, gyms, hotels).
• State and local government sites and apps — now explicitly covered under the DOJ’s 2024 Title II rule with hard deadlines.
• Increasingly, web-only businesses — courts in several circuits treat a website itself as a place of public accommodation.

If you’re selling to people in the EU as well, the bar is higher and the deadline has already passed — see our European Accessibility Act guide.

What happens if you don’t

The realistic risk in the U.S. isn’t a government regulator knocking — it’s a private demand letter. A plaintiff’s firm runs an automated scan against thousands of sites, finds machine-detectable failures (missing alt text, low contrast, unlabeled form fields), and sends a settlement demand. Most businesses settle in the $5,000–$25,000 range plus the cost of remediation, because fighting costs more.

Filings hit 3,948 in 2025, up roughly 24% year over year. We break the numbers down by state and industry in the lawsuit data guide.

How to make your website ADA compliant

1. Audit honestly. Start with an automated scan to find the machine-detectable issues fast, then layer manual testing (keyboard-only navigation, a screen reader pass, zoom to 200%). Automated tools catch 30–50% of WCAG issues; the rest need a human.
2. Fix the source code, not the symptoms. Add real alt text, label form fields, fix color contrast, ensure everything works with a keyboard, and use semantic HTML and ARIA correctly.
3. Prioritize by impact. Critical and serious issues on high-traffic pages (home, product, checkout) first. A blocked checkout is both the worst user experience and the most-cited complaint.
4. Re-test and monitor. Sites change weekly; a fixed issue silently regresses when a developer ships a new component. Continuous monitoring catches regressions before a plaintiff does.
5. Keep a dated record. A documented, ongoing remediation effort is your strongest defense. “We test continuously and here is the audit trail” beats “we installed a widget” every time.

Three myths that get businesses sued

Myth 1: “An accessibility overlay makes me compliant.” It doesn’t — and saying so is what got accessiBe a $1M FTC fine. Overlays sit on top of broken code and have become litigation targets themselves. Here’s the full story.

Myth 2: “I passed an automated checker, so I’m safe.” A clean automated scan is necessary, not sufficient. It misses the half of WCAG that requires judgment — meaningful alt text, logical reading order, sensible focus management.

Myth 3: “It’s a one-time project.” Compliance is a moving target because your site is. The businesses that stay out of trouble treat accessibility as ongoing maintenance, not a launch task.