An overlay is a third-party script you add to a site, sold on a subscription, that shows an accessibility toolbar and tries to repair the page automatically as it loads. It does repair some things. The field's own reference document on overlays says a non-trivial array of accessibility problems can be fixed this way, and pretending otherwise is both wrong and easy to disprove. What it cannot do is repair enough of them to reach conformance, and the categories it handles worst are the ones that decide whether a site is usable at all. Text alternatives, form labels and error handling, and keyboard access. The record around the marketing is separate and harder. The Federal Trade Commission approved a final consent order in April 2025 requiring one major vendor to pay $1 million that may be used to provide refunds to consumers. That settled a deception case. The order also bars the vendor from claiming its automated products can make any website conform, or keep it conforming, without evidence to back that up. Half of that order is about something else entirely, which is disguised reviews presented as independent opinion.
In practice
Separate the two products sold under one name, because they fail differently. The toolbar offers bigger text, higher contrast and adjusted spacing, and the argument against it is not that those do not work. It is that the people it claims to serve already have them, built into their operating system or in the software they use for everything else. Somebody who needs magnification needs it on every site, not only on yours. The repair script is the other half. That is where the claims outrun what software can do. The category is older than the compliance pitch, too. Add-ons that read a page aloud have been sold since the late 1990s, and those made no claims about conformance at all.
The limits on automatic repair are specific rather than general. Applying text alternatives to images is not reliable, because the right alt text depends on what the image is doing on that page. Repairing form labels, error handling and focus control is not reliable. Repairing keyboard access is not reliable. Modern component-based interfaces change state underneath the overlay, so React, Angular and Vue applications can move on without it. And the repairs themselves can slow the page down or cause unexpected changes for the people using assistive technology. Some formats are close to out of reach, and PDF and media files are the clearest cases, because the repair script never gets inside the file. Canvas and SVG are a softer version of the same problem. Script can change what an SVG reports and can add a fallback or controls to a canvas, so the barrier is not the format. It is that doing it correctly needs to know what the drawing was for.
The strongest sentence available on any of this came from a regulator rather than from the accessibility field. In its complaint the FTC stated that no automated testing tool alone can determine if a website meets accessibility standards, and that manual human testing is required instead. That is the agency's position in a pleading rather than a court's finding, and it is a federal regulator saying the thing overlay vendors sell against. Blind people's own organisations reached the same place from a different direction. The National Federation of the Blind condemned the practices of overlay providers in convention, demanding they stop making misleading and unproven claims. In the same breath it set out what an overlay would have to let somebody do to be worth having. Know it is there, know when it is running, switch it on and off, configure it with controls that are themselves accessible, and be able to contact whoever made it. That is a condemnation of how the category is sold rather than of the idea that software can help, and it is a distinction a vendor's lawyer will draw if we do not.
There is a compliance risk running the other way, and it is the one owners tend to care about. An overlay that detects a running screen reader and switches settings on is inferring something about the person at the keyboard, and an inference about somebody's health is exactly the kind of thing data protection law treats carefully. Whether a particular product does that, what it stores and where it sends it are questions to answer by inspecting the product rather than by assuming. Some have been reported to persist a setting across sites in a cookie nobody opted into. If any of that is happening on your site, the duties do not sit neatly with one party. You chose to install it and the vendor decides what it collects, and data protection law has separate roles for exactly that split.
Why it matters
The protection claim is the one to test, because protection is what these are sold on. More than 5,000 digital accessibility lawsuits were filed in the United States in 2025, and the firm that compiles that dataset reads the filings the same way every year. Widgets do not materially reduce legal risk, because courts and plaintiffs keep expecting substantive repair instead. Practitioners rate them accordingly, and in WebAIM's survey of 758 accessibility practitioners 67% called them not at all or not very effective, rising to 72% among respondents who have disabilities themselves. It is worth naming the other end of the same result, since 31% rated them somewhat or very effective, and quoting only the first number would be the selective citation we criticise vendors for. One caution in both directions. The judicial record is thinner than either side wants it to be. Overlays have turned up as evidence inside accessibility cases, and we have not found a decision that rules on whether one is adequate. So anybody quoting a case at you as a verdict, in either direction, is asking it to carry more than it does. Read the record before you buy the script.
What the vendor is barred from saying
The final order stops accessiBe from representing that its automated products can make any website conform to the guidelines, or keep it conforming over time, unless it holds evidence for the claim. It also stops the company presenting third-party reviews and articles as independent opinion, and it requires disclosure of any unexpected material connection to an endorser. It runs for 20 years and asks for a single compliance report, at one year. That second prohibition is the one worth remembering before you trust any vendor's review page.
Where this shows up on the site
Related terms
- RemediationRemediation is the work of fixing the accessibility problems an audit found, in the code, the content and the design, until the failures are gone.
- Accessibility auditAn accessibility audit is a structured evaluation of a website against WCAG, ending in a documented pass or fail for every applicable rule with the evidence attached.
- Automated testingAutomated testing is software that checks a page's code for the accessibility failures a machine can prove.
- Accessibility statementAn accessibility statement is a public page saying how accessible your site actually is.
Knowing the word is the easy part.
Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.