What is an accessibility overlay and why isn't it compliance?

An accessibility overlay is a JavaScript script added to an existing site that promises to make it compliant with digital accessibility rules without touching the source code. It works at runtime: after the page has already loaded, it manipulates the DOM to enlarge text, increase contrast, or attempt to infer ARIA roles on elements. It is a product distinct from the regulatory obligation that made it popular: the European Accessibility Act requires conformance with technical standards, and several vendors sold the overlay as a shortcut to reach it in an afternoon rather than through a real audit and remediation. The digital accessibility community, including the people who write the WCAG and ARIA specifications, has spoken out almost unanimously against this promise, not because the idea is worthless in principle, but because automated runtime fixes cannot correct what is wrong in the content's structure, and in several documented cases they make the experience worse for people already using their own assistive technology.

Why a layer of JavaScript cannot be enough

The limit is structural, not an implementation flaw fixable in the next release. An overlay acts on the page's presentation after it has loaded, but it cannot invent semantic information that the underlying markup does not carry. It cannot rebuild an incorrect heading structure, cannot fix a reading order that a screen reader follows when the HTML does not mirror the visual order, cannot generate a real text alternative for an image or video that lacks one, and cannot unlock a flow that a keyboard cannot reach, such as a focus trap or a dropdown the tab key never gets to. These are properties of the content and its architecture, not of its visual presentation. There is also a concrete interference problem: many people with disabilities already use their own screen reader, their own browser zoom, or their own extensions, and an overlay attempting to manipulate the same DOM in parallel conflicts with those tools. The result documented by the accessibility community is often a worse experience than having no overlay installed at all.

An enterprise example

The strongest evidence comes from litigation and regulators, not from an industry opinion. The Overlay Fact Sheet had been signed by over 800 accessibility professionals, developers and organizations by 2026, including editors and contributors of the WCAG, ARIA and HTML specifications and in-house accessibility experts at Google, Microsoft, Apple, BBC, Shopify, ServiceNow and Dell: the shared thesis is that automated overlay fixes are limited and unreliable and cannot guarantee WCAG compliance. The National Federation of the Blind passed a resolution on 10 July 2021 calling overlays "ineffective, deceptive, and a threat to the rights of blind people", and in January 2025 it publicly backed the Federal Trade Commission's order fining the maker of one such product 1 million dollars for deceptive marketing claims about its ability to make sites accessible, barring it for 20 years from claiming compliance without evidence. According to EcomBack's annual report on website ADA lawsuits, 983 lawsuits were filed in 2025 against sites with an overlay widget present, 24.90% of the 3,948 total lawsuits, up from 22.65% in 2024: US courts have consistently rejected installing an overlay as evidence of compliance.

Why it matters for decision makers

The economic case is the argument that convinces whoever signs the budget when the regulatory implications are not enough on their own. An overlay is a recurring subscription that does not reduce the underlying accessibility debt: the code stays exactly as it was, with the same technical debt piling up with every new feature shipped on top of an uncorrected base. Real remediation, touching the audit, the markup, the components and the forms, is a one-time cost against that debt, and it therefore shrinks over time instead of accumulating month after month like an installment that never finishes paying off the original problem. Anyone evaluating a vendor who proposes an overlay as the sole solution should treat it as a warning sign about that vendor's accessibility competence, not as a low-cost offer.

This entry is informational and does not constitute legal advice: for verifying conformance with the applicable technical standards, involve your legal counsel or an accessibility compliance specialist.