Overlay widgets promise one-line-of-code ADA compliance. The data tells a different story: FTC enforcement, rising lawsuits, and 800+ professionals who signed a public statement opposing them.
An accessibility overlay (also called a widget, toolbar, or plugin) is a piece of JavaScript that loads on top of your website. It typically adds a small icon in the corner of the screen that opens a toolbar with options like "increase text size," "high contrast mode," or "screen reader mode."
The critical problem: overlays do not change your website's source code. They inject JavaScript that attempts to modify the rendered page in the browser. The underlying HTML — the code that screen readers, search engines, and assistive technology actually read — remains broken.
This means missing alt text stays missing. Unlabeled form fields stay unlabeled. Broken heading hierarchy stays broken. Keyboard traps stay trapped. The overlay paints over these problems without fixing them.
When you cancel your overlay subscription, every "fix" vanishes instantly because nothing was ever actually repaired.
This list is informational. Compliapoint is not affiliated with any overlay vendor. Our assessment is based on published enforcement actions, court filings, and technical analysis of overlay technology.
These are not opinions — they are technical limitations inherent to the overlay approach.
Overlays inject JavaScript on top of broken HTML. The actual source code — what screen readers parse, what search engines index, what courts examine — remains unchanged.
Image alt text is stored in your HTML or database. JavaScript cannot retroactively add meaningful descriptions to images it has never seen before. AI-generated alt text is frequently wrong.
Form fields need <label> elements associated in the HTML. Overlays cannot reliably associate labels with inputs, especially in complex forms, multi-step processes, and dynamic content.
Keyboard traps, missing focus indicators, and inaccessible interactive components (menus, modals, tabs) are structural HTML/CSS/JS problems. An overlay layer cannot repair the navigation underneath it.
Heading hierarchy (H1 through H6) must be correct in the source HTML. Overlays cannot restructure your document outline. Screen reader users navigate by headings — this is critical.
Cancel your overlay subscription and every "fix" vanishes immediately. You have paid $200–$500/year with zero permanent improvement to your website. Source remediation is permanent.
We have compiled the enforcement actions, lawsuit data, and migration guidance into dedicated resources.
The January 2025 FTC ruling against accessiBe — what happened, what it means, and why it matters for every overlay user.
Read the analysisHow plaintiffs' attorneys use the presence of an overlay against you in court. The data on overlay-related lawsuits and settlements.
See the dataHow to safely remove your overlay widget and transition to source-level compliance. Step-by-step migration path.
Get the guideOver 800 accessibility professionals, advocates, and organizations have signed a public statement opposing the use of overlay widgets. Signatories include representatives from:
Read the full statement at overlayfactsheet.com
Source-level WCAG 2.2 remediation that actually fixes your code. One-time cost. Permanent results. Documentation that holds up in court.