By Mehdi HassanWhat does ADA website compliance require?
ADA website compliance requires that your website doesn't shut people with disabilities out of what you offer the public. Title III of the Americans with Disabilities Act covers places of public accommodation, and many courts treat business websites as part of that. The law doesn't spell out a technical standard for private websites, so the working answer is WCAG Level AA.
The Justice Department's guidance on web accessibility and the ADA says businesses have flexibility in how they make their sites accessible, and points to WCAG as a helpful standard. Settlement agreements commonly name WCAG 2.1 AA or later. If you target WCAG 2.2 AA, you're aligned with what plaintiffs, courts and enterprise buyers ask for. For the wider legal picture, including EU rules, see our hub on website accessibility compliance.
Does the ADA apply to websites?
In most cases, yes, the ADA applies to business websites, though courts don't fully agree on where the line is. Some federal courts require a link between the website and a physical place of business, like a store or restaurant. Others treat a website as a public accommodation on its own. Either way, a site that sells to US consumers is a realistic target.
Rule | Who it covers | Web standard |
|---|---|---|
ADA Title III | Private businesses open to the public | None in the regulation; WCAG AA in practice |
ADA Title II | State and local governments | WCAG 2.1 AA under the 2024 rule |
Section 508 | Federal agencies and their purchases | WCAG 2.0 AA via the 508 standards |
State laws (for example California's Unruh Act) | Businesses serving that state's residents | Often follow the ADA; can add damages |
State law is why ADA website compliance is more than a federal question. Some state laws allow money damages that the ADA itself doesn't, which helps explain why so many cases are filed in state courts. For startups, the takeaway is the same: the location of your company doesn't protect you if your customers are in the US.
What does the lawsuit data say about ADA risk?
The lawsuit data says website accessibility claims are common and growing, and they reach businesses of every size. Seyfarth Shaw, which tracks ADA Title III filings, counted 3,117 federal website accessibility lawsuits in 2025, up 27% from the year before. UsableNet's count, which includes state courts, comes to about 4,900.
- Federal website accessibility suits in 2025 (Seyfarth)
- 3,117
- Increase in federal filings over 2024 (Seyfarth)
- +27%
- Suits in 2025 including state courts (UsableNet)
- ~4,900
Both counts miss demand letters that settle before anything is filed, so the real number of disputes is higher. What the data can't tell you is your odds. What it does show is a steady pipeline of claims, many from repeat plaintiffs and firms that test sites with the same tools you can use yourself.
That's the useful insight: claims usually start with problems that are easy to find. Missing alt text on product images, unlabeled form fields, buttons that can't be reached by keyboard, and checkouts a screen reader can't finish. Fix those and you remove most of the low-effort claims.
What should you fix first for ADA compliance?
Fix the flows where a person spends money, books or signs up first, then the shared components every page uses, then content. That order follows the risk: a blocked checkout is a clear denial of service, while a contrast issue on an old blog post is a weaker claim. It's also the order that fixes the most pages per hour of work.
Priority | What to check | Why |
|---|---|---|
1. Transaction flows | Checkout, booking, signup, demo request | Blocking these denies the service itself |
2. Navigation and header | Menu, search, skip link, focus order | Breaks every page if it fails |
3. Forms and components | Labels, errors, buttons, modals | One fix repairs many pages |
4. Media | Alt text on product images, video captions | Easy for testers to spot |
5. Third-party embeds | Chat, schedulers, cookie banners | Often the hidden blocker |
6. Older content | Blog posts, PDFs, archived pages | Lower risk; fix in batches |
Our WCAG 2.2 checklist breaks these down by who fixes them. If you're not sure where your site stands, start with our routine for how to test website accessibility, a short keyboard and screen-reader pass you can run on each key flow.
Hypothetical example: prioritizing fixes on a small ecommerce site
For example, suppose a direct-to-consumer brand with 40 products gets a scan showing hundreds of issues. Most are repeats: the same product card missing alt text, the same unlabeled quantity field, the same low-contrast sale badge.
Instead of fixing issues one by one, the team fixes the product card, quantity input and badge components, and the count drops sharply. Then they test checkout with VoiceOver and find the shipping-method radio buttons aren't announced. That one issue matters more than everything else on the list, because it stops a purchase.
Is my website ADA compliant? How to tell
You can't prove ADA compliance with a scan, but you can get a good read on it in an afternoon. Run an automated checker like axe or Lighthouse on your key pages, then try to complete your main flows with only a keyboard, then with a screen reader. If you can't finish a purchase or signup that way, the site isn't compliant.
- Automated scan. Catches missing alt text, contrast failures, empty links and missing labels. It finds part of the problems, not all.
- Keyboard test. Can you reach and use every link, button and field with Tab, Enter and Space, and always see where focus is?
- Screen-reader test. Do buttons and fields announce what they are? Are errors read out?
- Zoom test. Does the page work at 200% zoom and at phone width?
For a formal answer, especially if you sell to large companies or have had a complaint, a manual audit gives you a documented issue list. Our guide to accessibility audit cost explains what different audits include.
What should you do if you get an ADA demand letter?
If you get an ADA demand letter, don't ignore it and don't panic-buy a widget. Get an attorney involved, document the current state of your site and start real fixes. A credible remediation plan helps your position; an overlay installed the day after a letter arrives usually doesn't.
Call a lawyer
Find counsel who handles ADA Title III website cases. Many letters follow a pattern, and experienced counsel knows how they usually resolve.
Capture the current site
Save screenshots and scan reports of the pages named in the letter, with dates. You'll want a clear before and after.
Fix the named issues first
Repair the specific barriers the letter describes, then the flows they sit in.
Commit to a full remediation plan
Plan the rest of the work against WCAG 2.2 AA with dates. Settlements commonly require this anyway.
Publish an accessibility statement
Our accessibility statement template shows how to state your standard, known issues and contact route.
How does the ADA Title II rule affect businesses?
The ADA Title II rule affects businesses indirectly. In 2024 the Justice Department set WCAG 2.1 AA as the required standard for state and local government websites and apps, with phased compliance dates; check ada.gov for the current ones. It doesn't apply to private companies directly, but it changes what public-sector buyers ask of their vendors.
If you sell software or services to cities, school districts, public universities or state agencies, expect accessibility requirements in contracts and requests for proposals. Treat WCAG 2.1 AA as the floor and 2.2 AA as the target. Add an accessibility page to your B2B trust pages so buyers find the evidence quickly, and if you're planning a rebuild anyway, our framework on whether to migrate your website helps decide if fixing or rebuilding makes more sense.
