Home / Guides / Overlays

Why overlay widgets don't stop lawsuits

The pitch is irresistible: paste one line of JavaScript, a little accessibility icon appears, and you're "compliant." It's irresistible because fixing code is work and a widget is not. Here's what the pitch leaves out.

The record

• Sites with overlays installed still get sued. A meaningful share of accessibility lawsuits in recent years named sites that already had an overlay running. Plaintiffs' firms can detect overlays, and some treat them as a signal the underlying site was never actually fixed.
• Regulators have acted on overlay marketing. The FTC took action against a major overlay vendor over claims that its product made sites compliant. "One line of code = compliance" is precisely the claim that drew scrutiny.
• Overlays can interfere with the tools they claim to serve. Screen reader users frequently report overlays breaking pages that were partially usable before, and disability-community open letters have asked vendors to stop marketing them as fixes.

Why they can't work in principle

An overlay is a layer of JavaScript that tries to patch symptoms at display time. It cannot add the alt text only you know, restructure heading logic, fix a form built without labels, or make a custom widget keyboard-operable in the way the underlying code requires. The failures that attract lawsuits live in the code. That's where the fix has to live too.

What actually reduces risk

1. An honest audit of what's broken, ranked by severity: automated scanning plus human review.
2. Real remediation in the code, prioritized by user impact and legal exposure.
3. Documentation of the effort: dates, fixes, re-scans. Good faith leaves a paper trail.
4. Monitoring so new content doesn't quietly reintroduce old failures.