A small e-commerce client in Boca forwarded me an email last year titled "URGENT: ADA Compliance Violation." A law firm claimed the site was inaccessible to blind users and wanted a few thousand dollars to go away. No customer had ever complained. It was a template.
That's how most owners first hear about website accessibility and ADA compliance: the scary letter. Here's the calm version: who has to comply, the real risk in 2026, why overlay widgets are a trap, and the fixes that do most of the work.
Who actually has to comply
"ADA compliance" means Title III of the Americans with Disabilities Act. It was written in 1990 and never mentions websites, which is why this area is still messy. Courts have broadly covered consumer-facing sites, especially in the Eleventh Circuit (Florida), the Second (New York) and the Ninth (California).
- Q1Are you a state or local government site?YesYes, with a written standard. A 2024 DOJ rule requires WCAG 2.1 AA on a fixed timeline.
- Q2Does the public buy, book or pay through your site?YesAssume you're covered. E-commerce is the bullseye for demand letters.
- Q3Do you have a physical location the site supports?YesLikely covered. Don't count on the 'nexus' argument saving you.
- B2B or a small brochure site is lower risk, not zero. Doing it right is cheap enough that it's still worth it.
Public-sector work is its own world; I cover it in what it costs to build a government website.
The real legal risk, minus the fear-mongering
The risk is real, but it has a knowable shape. A small number of firms and repeat plaintiffs file most suits, usually over issues an automated scanner flagged. Demand letters vastly outnumber lawsuits, because paying a few thousand dollars is cheaper than litigating.
A site that passes the obvious checks and shows a genuine accessibility effort is a bad target, and serial firms move on. If a letter lands, don't panic-pay without a lawyer, but don't ignore it either.
Why accessibility overlay widgets are a trap
- Doesn't fix the underlying code
- Often breaks screen readers users already run
- Plaintiffs specifically target overlay sites
- Fixes the actual markup
- Works with assistive tech
- Helps SEO and conversions too
Accessibility professionals have widely signed an "Overlay Fact Sheet" recommending against them, and in 2025 the FTC fined accessiBe $1 million over its compliance claims. When the regulator fines the "solution," that's your answer.
The standard and the fixes that matter
Courts reference the Web Content Accessibility Guidelines (WCAG). Target Level AA; AAA isn't expected. WCAG 2.1 AA is the settled baseline and 2.2 AA (late 2023) is the smart bet, adding 24-pixel touch targets and visible focus. A small set of issues accounts for most real problems:
- Alt text on meaningful images (empty alt on decorative ones)
- Contrast of 4.5:1 for body text, 3:1 for large text and UI
- Everything works by keyboard, with no traps
- Visible focus states (style them, never delete them)
- Real labels on every form field, errors described in text
- One h1, a logical heading outline, proper landmarks
- No unpausable carousels; honor reduced-motion settings
- Link text that says where it goes, not 'click here'
None of this is exotic. It's competent front-end engineering, and nearly every item doubles as SEO: Google's crawler is effectively a well-funded screen-reader user. Estimates put working-age adults with a disability at roughly one in four, so this is a quarter of your market, not an edge case.
How to actually test it
- 1Automated scanaxe DevTools, WAVE or Lighthouse. Free and fast.
- 2Keyboard-only passPut the mouse away and use the whole site.
- 3Screen-reader passNVDA on Windows or VoiceOver on Mac and iOS.
- 4Human auditFor stores and anything that takes payments.
Scanners catch only 30–40% of issues, so run both kinds. If you'd rather not do it yourself, a free audit tells you where you stand before anyone spends a dollar.
Build it in vs. bolt it on: the real cost math
Built in from the start by a competent team, accessibility adds very little. Retrofitting a finished site is where it gets expensive.
| Item | Range |
|---|---|
| Manual audit | $1,500–$5,000+ |
| Remediation, small brochure site | $3,000–$10,000 |
| Remediation, mid-size site with store | $15,000–$50,000+ |
Every client who came to us after a demand letter learned it the hard way. On a new site, insist accessibility is in scope from day one. It's baked into how we price and build, as our pricing page shows.
Frequently asked questions
Does my small business really have to be ADA compliant?
If the public transacts with you online, assume yes. A tiny brochure site is lower risk, but doing it right is cheap enough that "lower risk" isn't a reason to skip it.
Will an accessibility widget or overlay protect me from a lawsuit?
No. Overlays don't fix the underlying code, and sites running them have been sued by the thousands. Spend the money on the actual site.
What standard do I need to meet?
WCAG 2.1 AA is the baseline courts reference; WCAG 2.2 AA is the smart target for anything built today.
I already got a demand letter. What do I do?
Don't panic-pay, and don't ignore it. Talk to a lawyer and start real remediation in parallel; a genuine, ongoing effort is your best position.
Want a straight answer about your site? See how we build accessibility into every web development project, or get in touch and we'll talk it through, no fear-mongering required.
