Accessibility Overlay Widgets Do Not Make You ADA-Compliant
Key takeaways
- Accessibility overlay widgets don’t make you ADA-compliant. Courts and disability advocates have said so repeatedly.
- ADA lawsuits against small businesses are still climbing — projected up 20-25% again in 2026, with 432 new filings in August alone.
- Overlays can actually make sites worse for real screen-reader users, and plaintiffs’ firms are specifically flagging them.
- The fix is real WCAG 2.2 AA work — semantic HTML, alt text, keyboard navigation, contrast — not a $49/month script tag.
- Settlements average $15,000-$50,000, which is a lot more than doing the work right the first time.
You’ve seen the little blue accessibility icon that pops up in the corner of a website — the one that opens a menu of font-size sliders, contrast toggles, and “screen reader mode.” Sales reps for the companies behind those widgets have been calling East Texas small businesses hard for the last two years. The pitch: “Install our one line of code, get ADA-compliant instantly, avoid getting sued.”
I’ll say it plainly: that pitch is wrong, and it’s putting small businesses at more legal risk, not less.
Why the overlay pitch exists
ADA website lawsuits are a real problem. There were more than 5,100 filed in 2025, midyear 2026 numbers are projecting another 20-25% increase, and in August 2026 alone, plaintiffs filed 432 new federal complaints against businesses over website accessibility. Most of those businesses had never thought about accessibility a day in their lives. So the fear is legitimate.
That’s the market the overlay companies feed on. A $49-$99/month script tag that promises to fix the problem sounds like a bargain compared to a $30,000 settlement. The problem is that it doesn’t fix the problem.
What overlays actually do
The typical overlay widget does three things:
- Adds a floating button in the corner
- Opens a menu with visual settings (font size, contrast, cursor)
- Optionally, tries to run automated fixes on your HTML — guessing at alt text, adding ARIA labels, rewriting elements
Numbers 1 and 2 are cosmetic. They help sighted users with mild visual preferences, which is nice but wasn’t the legal problem. Number 3 is where things get dangerous, because guessing at accessibility metadata often produces worse results than not doing it at all.
An overlay that mislabels your “Contact” button as “Submit” for a screen-reader user has just broken their experience worse than the original site did.
What the courts and advocates are saying
The National Federation of the Blind has publicly opposed automated overlays. Actual screen-reader users have posted case study after case study showing overlay-equipped sites failing basic navigation tests. And — this is the part small-business owners need to hear — plaintiffs’ firms are specifically searching for overlay-equipped sites now, because those sites are easier to demonstrate as non-compliant.
The overlay was supposed to be your shield. In several 2025-2026 lawsuits, it turned out to be a target.
The real fix (and why it’s not scary)
What the courts actually expect is that your website conforms to WCAG 2.1 or 2.2 Level AA. That standard is not a mystery, and for a normal 8-15 page small-business site, it’s not a $30,000 project. The core work is:
| Accessibility fix | Effort |
|---|---|
| Real alt text on every image (written by a human, not guessed) | Small |
| Semantic HTML — real headings, real buttons, real links | Depends on the theme |
| Keyboard-only navigation works (Tab, Enter, Escape) | Small if built right, painful if bolted on |
| Text contrast passes 4.5:1 minimum | Small — usually a palette tweak |
| Form fields with real labels and error messages | Small |
| Video captions and PDF alternatives | Ongoing |
Most of the work happens once, during design. A well-built WordPress site with a good theme and a designer who thought about accessibility from the start is 80% of the way there before you ever add content.
What to say when the overlay sales rep calls
They will call. When they do:
- Ask if they will indemnify you against ADA lawsuits (they won’t).
- Ask them to point to a case where their widget prevented a lawsuit (they can’t).
- Ask what happens to the ARIA labels their AI guessed wrong (they mumble).
That usually ends the call.
What to do this month if you’re worried
- Run a free audit. WAVE (wave.webaim.org) and Google Lighthouse both give you an honest snapshot in minutes.
- Fix the top three issues. Usually contrast, alt text, and heading order. That kills the most common bot-generated demand letters.
- Get a real human review annually. A designer who knows WCAG 2.2 can catch what automated tools miss — like a keyboard trap in your booking widget.
- Document your work. A written accessibility statement and a summary of your audit history is genuine good-faith evidence.
Where people go wrong (and when to call a pro)
The two biggest mistakes: (1) installing an overlay and assuming the problem is solved, and (2) ignoring accessibility entirely and hoping the demand letters don’t come. Neither works. Call a pro when you want a real WCAG 2.2 AA audit, a fix plan, and a written accessibility statement that would actually hold up if a plaintiff came calling. It’s not exotic work — it’s just careful web design. And it costs a small fraction of a settlement.
Frequently Asked Questions
Is an accessibility overlay ever the right answer?
Rarely, and never as a standalone strategy. Some organizations use them as a supplement on top of real WCAG-conformant sites, mostly for user-preference features like text spacing. But if the underlying site isn’t accessible, the overlay doesn’t save you.
What’s the difference between WCAG 2.1 and 2.2?
WCAG 2.2 (published late 2023) added a handful of new success criteria, mostly around focus visibility, dragging alternatives, and touch target sizes. For a small business, 2.2 AA is the current target — but if you’re on 2.1 AA and staying maintained, you’re in defensible shape.
My site is on Wix / Squarespace. Am I safe from ADA lawsuits?
No. The platform doesn’t matter to a plaintiff. What matters is whether the site as-shipped works with a screen reader and a keyboard. Wix and Squarespace themes vary in quality, and your own content choices (images without alt text, PDFs, videos without captions) are usually where the trouble starts.
How much does a real accessibility audit cost for a small business site?
For a 10-20 page site, expect $500-$1,500 for a thorough manual audit and remediation plan. Fixes on top of that vary — usually another $500-$2,000 if the site is well-built, more if it’s a wreck. Either way: cheaper than $30,000.
Worried an overlay isn’t enough? Let’s do a real audit and give you a defensible fix plan.