Nobody sues a website for hiring the wrong vendor. They sue it for the barriers a screen reader user actually hit. So it is worth asking a narrower, more uncomfortable question: what happens to the overlay widget itself once a demand letter gets written?
It does not disappear. It gets a screenshot. It gets an archive.org capture with a timestamp. It gets pasted, with the little accessibility icon still visible in the corner, into a legal filing as Exhibit A. The widget was supposed to be the thing that kept the site out of court. Instead, it becomes the paper trail that puts it there.
That is the part most sites never plan for. It is not that overlays "don't work" as an abstract technical matter, although they often don't. It is that the widget's own presence, and the marketing language sold alongside it, become documentation a plaintiff's attorney can point to directly.
The Stat: UsableNet's ADA lawsuit tracking finds that a meaningful share of digital accessibility complaints name websites that were already running an accessibility overlay at the time. (Source: UsableNet)
Why the widget itself is the exhibit, not just the site
Most accessibility complaints start from a barrier: a form field with no label, a menu that traps keyboard focus, a video with no captions. That part is the same with or without an overlay installed.
What changes when an overlay is present is the second half of the argument. A plaintiff's attorney does not just need to show the barrier existed. To strengthen a claim of knowledge and disregard, it helps enormously to show the site owner was already aware that accessibility was a live issue and chose a specific response to it.
An overlay widget supplies that proof on its own. The little icon sitting in the corner of the page is a standing, dated admission that someone at the company thought about accessibility, budgeted for it, and installed something. Screenshotted once, archived once, it stays available indefinitely as a record of that decision.
This is a different kind of exposure than a broken form field or a missing alt attribute. Those are technical defects that can be fixed quietly and, in many cases, argued as isolated oversights. A widget sitting in the corner of every page on the site is not quiet and it is not isolated. It is visible to every visitor, on every page, for as long as it stays installed, which means the window during which it can be captured and dated is effectively the entire time it runs.
The paper trail, step by step
Here is the mechanic in more detail, because "it becomes evidence" is vague until you see the actual sequence.
1. The capture. Anyone (a tester, an advocate, a plaintiff's firm doing intake) can screenshot the live page. A browser extension or a service like the Wayback Machine timestamps it automatically, so there is a record of exactly when the overlay was present and what it claimed to do.
2. The marketing language becomes part of the record. Overlay vendors often use confident language ("compliant," "certified," "instant fix") in their own on-page copy or badge. That language did not stay in a sales deck. It sat on the live site, visible to visitors, which means it is fair game to quote back.
3. The letter or complaint. A demand letter or complaint can attach the screenshot as an exhibit, alongside the specific barrier a user encountered. The exhibit does two jobs at once: it documents the barrier still existed, and it documents that the site had already taken a public position on accessibility.
4. The argument about knowledge. From there, the argument writes itself: the company knew accessibility mattered enough to install something and advertise it, and a real user still could not complete a real task. That combination, awareness plus continued failure, is a stronger narrative for a plaintiff to present than a failure alone.
None of this requires an invented statistic to make sense. It is simply how documentation moves from a live webpage into a legal file: screenshot, archive, exhibit, argument.
5. It survives removal. Even if a company removes the overlay after receiving a complaint, the earlier capture does not go away. An archived snapshot from before the removal date can still be entered into the record, which means taking the widget down after the fact does not undo the exhibit that already exists. Whatever position the site takes going forward, the dated record of what it did before the complaint stays intact.
In our own review work, we have seen sites treat the overlay as a closed chapter the moment it is uninstalled, only to find that the screenshot from months earlier is still the thing being discussed. That is a useful, if uncomfortable, illustration of why the timing of the capture matters more than the timing of the fix.
What this means for the "just install something" instinct
We have covered the general case against overlays before, in Accessibility Overlays Are a Lawsuit Magnet, Not a Shield and in Why Accessibility Overlay Widgets Get Sued Too. Both make the case that overlays do not reliably fix the underlying barriers. This piece is about something narrower and, in some ways, more urgent: even if you set aside whether the overlay works, its mere presence changes the story a court hears.
That distinction matters for anyone weighing the decision today. A site with no overlay and real barriers is a company that has not yet addressed accessibility. A site with an overlay and the same real barriers is a company that addressed accessibility publicly, on the record, and the barriers persisted anyway. The second story reads worse in a filing, not better.
Our own litigation tracking piece, Overlay Users Still Get Sued in 2026, covers the scale of that outcome across a large number of companies. And the regulatory side is not theoretical either, as we detailed in The FTC Fine That Shows Overlay Risk Is Regulatory Too, where marketing claims about an overlay's effectiveness became the subject of government action, not just private litigation.
What a defensible position actually looks like
If the goal is to reduce legal exposure rather than just to have installed something, the fix is not a widget, it is a paper trail of a different kind:
- Real remediation against WCAG success criteria, verified with both automated scanning and manual testing, including actual keyboard and screen reader use.
- A dated accessibility statement that describes what has been fixed, what is in progress, and how to report a barrier, hosted at a stable URL rather than inside a script-injected widget.
- A named contact channel for accessibility issues, monitored and responsive, so a user's first move is a support ticket rather than a demand letter.
- Version history of your remediation work, so that if a claim is ever filed, you can show ongoing, good-faith progress rather than a single purchase decision.
The U.S. Department of Justice's ADA guidance and the W3C's Web Accessibility Initiative guidance on accessibility statements both point in the same direction: real conformance work plus honest, specific public communication about where a site stands. Neither treats a bolt-on widget as a substitute for either one.
That is a heavier lift than installing a script tag, and it should be. It is also the version of "we took this seriously" that holds up when someone actually reads the record.
None of these four items are exotic. They are the same practices that any organization serious about compliance already applies to security, privacy, or financial reporting: fix the real thing, document what you did and when, keep a channel open for people to tell you what you missed, and keep a record showing the work continued. Accessibility is not a special case that gets to skip that discipline in favor of a shortcut.
If you want a clear picture of where your own site stands, and what a defensible remediation path would look like for your specific codebase, you can start with a free accessibility audit rather than guessing.
Talk to a person about it
If you are trying to work out whether to remove an existing overlay, how to sequence real fixes, or what a defensible accessibility statement should say for your situation, reach our team directly at experts@wcag.world. You can also get a free accessibility audit to see exactly where the real barriers are before anyone else finds them for you.