Accessibility overlays don't prevent ADA lawsuits. They trigger them.
The widget added a “lawsuit magnet” to your site, not a shield. Here's what the court record shows — and what actually works.
What overlays promise — and what actually happens.
- —Add one line of JavaScript and your site becomes WCAG 2.1 AA compliant.
- —Our AI automatically remediates accessibility violations across your entire site.
- —You're protected from ADA lawsuits the moment the widget is installed.
- —No developer required. No code changes needed.
- —Endorsed by the disability community.
- ✗Courts have explicitly rejected overlay vendor agreements as a defense to ADA claims. The widget is not compliance.
- ✗Automated tools cannot detect or fix most meaningful accessibility barriers — screen reader compatibility requires correct semantic HTML.
- ✗Plaintiffs' firms have confirmed they specifically target sites displaying overlay widgets, using them as a signal that the underlying site is broken.
- ✗The National Federation of the Blind, the country's largest blindness organization, has formally opposed overlay technology in public statements and regulatory filings.
- ✗Over 2,000 ADA lawsuits have been filed against websites that had an overlay widget installed at the time of filing.
Why overlays fail — even when they work as advertised.
Screen readers ignore the overlay
Overlays inject a UI layer on top of your existing HTML. They do not modify the underlying DOM that screen readers parse. A button with no accessible label is still a button with no accessible label — the overlay just adds a floating panel that most assistive technology users have learned to dismiss.
Overlays introduce new WCAG violations
The overlay widget itself is often inaccessible. Common failures include focus traps that strand keyboard users inside the widget panel, conflicting ARIA announcements that confuse screen readers, and overlay controls that fail 1.4.3 contrast requirements. You paid for a tool that makes compliance worse.
Courts evaluate the accessible experience, not your vendor invoice
Federal judges and DOJ investigators look at what a person using a screen reader or keyboard actually experiences on your site. An invoice from an overlay vendor is not evidence of an accessible site. Multiple courts have ruled explicitly that the presence of an overlay is not a defense to an ADA claim.
Sued despite having an overlay widget installed.
These cases are documented in federal court filings. The presence of an overlay widget did not prevent the lawsuit, and in several cases was cited as evidence the defendant knew about the accessibility problem.
Robles v. Domino's Pizza — reached the Ninth Circuit. The court rejected the argument that a third-party tool satisfied ADA obligations.
Sued under the ADA for website inaccessibility. An overlay widget does not satisfy the legal standard the court applied.
Named in ADA and Rehabilitation Act complaints related to website and online course accessibility.
Named in ADA and Rehabilitation Act complaints related to website and online course accessibility.
Filed in the Central District of California. Overlay widgets have been explicitly criticized in related advocacy as creating a false sense of coverage.
All cases referenced are part of the public federal court record. This is not an exhaustive list. Case outcomes vary; inclusion here reflects that an overlay widget did not prevent litigation from being filed.
What actually holds up — in court and in practice.
Fix the underlying code
Real accessibility means correct semantic HTML — proper ARIA labels, keyboard-navigable controls, sufficient color contrast, and working form inputs. These are changes made in your codebase, not masked by a widget layer on top of it. Sturdly surfaces each violation with a copy-paste fix your developer can apply in minutes.
Document the effort
Courts have consistently rewarded good-faith, ongoing remediation efforts even when a site isn't fully compliant yet. What they require is a timestamped audit trail showing you identified violations, prioritized them, and fixed them over time. Sturdly builds that record automatically with every scan.
Monitor for regressions
New features, A/B tests, CMS updates, and third-party scripts introduce new violations every week. Daily monitoring catches regressions the moment they appear — before a plaintiff's firm finds them. Sturdly runs axe-core against every page on your site every morning and alerts you when anything breaks.
Overlay widget vs. Sturdly.
Run a free scan — see what's actually broken on your site, overlay or not.
No card required. Paste your URL and get a full WCAG violation report in under two minutes — the same axe-core analysis that plaintiffs' firms use to identify targets.
If you already have an overlay installed, we'll show you what it's not catching.
Start a free scan →No account required · Results in under 2 minutes