Overlays versus Root-Level Remediation: Why Quick Fixes Fail Legal and Technical Scrutiny

Accessibility widgets and JavaScript overlays are everywhere. They promise to make a website or digital product compliant with a single line of code, with no development overhaul required. For publishers under pressure to respond to institutional accessibility requirements, that pitch is understandably appealing. The problem is that it does not work, and the legal record is now making that impossible to ignore.

What Overlays Actually Do

A third-party overlay is a JavaScript layer applied on top of existing web content. It typically presents users with a toolbar offering settings like font resizing, contrast adjustment, or “screen reader mode.” The underlying HTML, EPUB structure, or PDF tagging remains untouched.

This creates a fundamental technical problem. Screen readers such as JAWS, NVDA, and VoiceOver interact directly with the source document structure, including the DOM, the semantic markup, the ARIA attributes, and the reading order embedded into the file. An overlay running on top of that structure cannot retroactively fix missing heading hierarchies, mislabeled form fields, untagged images, or broken reading order. In many documented cases, overlays actively interfere with how screen readers parse a page, creating a worse experience for the very users they are intended to support. The core issue is that overlays treat accessibility as a presentation problem, when in reality, it is a structural one.

The Legal Picture

Publishers and platform providers that have relied on overlays as a compliance strategy are now facing a specific and growing legal risk. Courts and plaintiffs are not just rejecting overlays as insufficient evidence of compliance; they are targeting them directly.

The data from recent years is stark:

• In 2024, over 1,000 businesses were sued despite having accessibility widgets installed, accounting for more than 25% of all digital accessibility lawsuits filed that year.

• In the first half of 2025 alone, 456 lawsuits specifically targeted websites with overlays in place, representing 22.6% of all ADA accessibility filings.

• In January 2025, the FTC reached a $1 million settlement with a leading overlay provider for misleading businesses by marketing its product as a guaranteed compliance solution.

The legal argument plaintiffs consistently make is that overlays fail to address actual code-level accessibility barriers. Courts have been receptive to that argument. Having an overlay installed is not a defense; in many cases, it has become evidence of a company’s awareness of accessibility obligations paired with a choice not to address them substantively.

Why Root-Level Remediation Is the Only Defensible Strategy

Genuine accessibility conformance requires fixing the source. For publishers, that means the following:

• Semantic HTML and EPUB structure: Proper heading hierarchies, landmark regions, list markup, and logical reading order built into the file, not applied as a visual layer on top of it.

• Tagged PDFs: Documents structured with accurate tag trees so that assistive technologies can navigate content meaningfully, including tables, figures, and footnotes.

• ARIA where it adds value: Roles, states, and properties applied at the component level to communicate interactive behavior to assistive technologies, not as a blanket fix applied by a script.

• Alt text at the source: Image descriptions authored and embedded in the content itself, not generated by an overlay that has no knowledge of what the image actually conveys in context.

Root-level remediation is more resource-intensive upfront. However, for publishers producing EPUBs, PDFs, and web-based reading platforms at scale, a structured workflow that embeds accessibility from the onset is far more cost-effective than repeated reactive remediation. It is far more defensible when a procurement team or plaintiff's attorney requests evidence of accessibility conformance.

What This Means for Publishers

Institutional buyers are becoming more technically sophisticated in how they evaluate accessibility claims. A completed ACR that claims WCAG 2.1 AA conformance will not hold up if the underlying product relies on an overlay to achieve it. Procurement teams, accessibility auditors, and assistive technology users can all identify the difference.

Publishers who have deployed overlays on their platforms or recommended them to partners should view this moment as a prompt to assess what genuine remediation would require, before a legal or procurement challenge forces the issue.

At S4Carlisle, our accessibility services are built around root-level remediation: WCAG 2.2 AA audits, structured EPUB and PDF workflows, semantic tagging, and VPAT documentation that reflects actual conformance. As a Benetech Global Certified Accessible vendor, we work within the source content, not on top of it.

To discuss what genuine accessibility remediation looks like for your digital products, contact us at sales@s4carlisle.com.