Accessibility Overlays: What They Are, Why the FTC Fined accessiBe, and Why a Widget Doesn't Stop a Lawsuit

What an Overlay Is

The Overlay Fact Sheet, a statement endorsed by more than 1,000 accessibility professionals, people with disabilities, and staff at companies including Google, Microsoft and Apple, defines overlays as "technologies that aim to improve the accessibility of a website" by applying "third-party source code (typically JavaScript)" to modify the front-end code. In practice that is one line of script pasted into your theme or added by a plugin. When a visitor loads a page, the script loads from the vendor's servers, draws a toolbar, and starts changing what the browser shows.

accessiBe, UserWay, AudioEye's widget tier, EqualWeb and a dozen smaller products all work this way. The pricing is a subscription tied to your traffic, and the pitch is the same across all of them: install once, be compliant.

What It Does, and What It Leaves Untouched

Two things happen at once, and the sales page only describes the first.

What it does: it adds a visible toolbar (bigger text, high contrast, a dyslexia font, pause animations), and behind the scenes it tries to repair the page: guessing alt text for images with AI, adding ARIA labels to controls it can identify, restructuring what it thinks the headings are. Some of that is harmless. Some of it is the toolbar duplicating settings a disabled user already has in their operating system and screen reader, which is why so many of them turn it off.

What it leaves untouched: your site. The image in your Media Library still has no alt text. The contact form field still has a placeholder instead of a label. The button color still fails contrast. The theme's heading structure is still wrong. Every one of those is in your files and your database, and the overlay never writes to either. Switch the script off, or let the subscription lapse, and the site is exactly as inaccessible as it was the day before you installed it. The Fact Sheet's conclusion follows directly: "full compliance cannot be achieved with an overlay," and products marketed as providing compliance "should be viewed with significant skepticism."

This is the distinction the whole category turns on. A screen reader user does not experience your site through the vendor's toolbar. They experience the code, through their own software. If the code is wrong, the toolbar is decoration.

What Blind Users Say

The clearest statement is from the National Federation of the Blind, the largest organization of blind people in the United States. In June 2021 its board of directors reviewed accessiBe's practices and concluded that the company "engages in behavior harmful to the advancement of blind people in society," and revoked accessiBe's sponsorship of the NFB's national convention on June 22, 2021. The convention then passed Resolution 2021-17 on July 10, 2021, titled "Regarding accessiBe's Disrespectful and Misleading Business Practices," which says the company "overstates the effectiveness of automated testing" and "promotes the false claims of attaining Web Content Accessibility Guidelines compliance through the integration of one line of code."

The Overlay Fact Sheet collects first-hand accounts. One screen reader user: "Every time I go on a website … I know that my blocker isn't working properly, and I'm in for a hellish experience." Another, on a specific product: "focus jumps all over the place with #AccessiBe enabled. When it's disabled, it behaves itself." The pattern in those accounts is not that the overlay fails to help; it is that the overlay sits between the user and the page and interferes.

What the FTC Found

In January 2025 the Federal Trade Commission announced a complaint and proposed order against accessiBe, alleging the company misrepresented its AI-powered widget's ability to make any website WCAG-compliant. On April 22, 2025, the Commission approved the final order by a 3 to 0 vote. It requires accessiBe to pay $1 million and bars the company from representing "that its automated products can make any website WCAG-compliant or can ensure continued compliance" without evidence to support the claim.

The complaint had a second part that gets less attention. The FTC alleged that accessiBe "deceptively formatted third-party articles and reviews to appear as if they were independent opinions" without disclosing its connection to the reviewers. If you researched overlays before buying one and found a wall of glowing comparisons, that is the context for them.

A federal regulator's order is not an accessibility standard. But it is the reason no overlay vendor's page can any longer tell you, in so many words, that installing the script makes you compliant. Read the current sales copy with that in mind.

What the Lawsuit Numbers Say

UsableNet's monthly tracker reports, for July 2026, 401 new ADA web accessibility lawsuits, of which 113 defendants were using a third-party accessibility widget when they were sued. That is more than one in four. The widget did not prevent the suit. In a growing share of complaints, the widget is itself listed among the barriers, because of the interference the previous section describes.

Set that beside the 77 repeat defendants in the same month. A settlement that installs a widget and changes nothing else is the shortest route to a second letter. The ADA website lawsuit page covers what to do when one arrives.

The Privacy Problem Nobody Mentions on the Sales Page

Several overlays detect whether a visitor is using a screen reader in order to switch on their "screen reader mode." The Overlay Fact Sheet points out what that means: detecting assistive technology "exposes the fact that the person using the device … has a disability." That is sensitive personal data, collected by a third-party script, without informed consent, and the Fact Sheet flags it as a potential GDPR and CCPA problem. If your privacy policy does not mention that a vendor's script is inferring disability status from your visitors, and you have an overlay installed, your privacy policy is wrong.

What to Do Instead

1. Find out what is actually broken. Run an automated scan against WCAG 2.1 AA. It will find the mechanical failures: contrast, alt text, labels, empty links and buttons, heading order, language attribute. WCAGpatch's free tier does this on WordPress and dates the result. Run it.
2. Fix the code, not the rendering. Alt text goes in the Media Library. Labels go in the form plugin. Colors go in the theme's global styles. Each item on the checklist names the WordPress place to fix it. On Pro and up, WCAGpatch writes the alt text and label fixes into those fields for you.
3. Test with a person. Automated tools cover roughly 30 to 40 percent of WCAG criteria. Whether alt text is meaningful, whether the reading order makes sense, whether checkout can be completed by keyboard alone: those need a human with a screen reader, ideally one who uses it every day.
4. Document it. Keep the scan history and the fix log. The WCAG certification page explains what a dated certificate can and cannot prove.
5. If you already have an overlay, test the site with it off and compare. Don't count it as remediation. If you are in a dispute, log the change and tell your lawyer before you make it.

None of this makes a site "compliant" in the way the overlay sales page promised, because no tool can honestly promise that. It makes the site work for the people the law is about, and it leaves a record that you did the work. Those are the two things that matter.

Sources

1. Overlay Fact Sheet. Definition of an overlay; "full compliance cannot be achieved with an overlay"; 1,000+ signatories; screen reader user quotes; assistive-technology detection as a GDPR/CCPA concern.
2. National Federation of the Blind, 2021 Resolutions, Resolution 2021-17, passed July 10, 2021. The June 2021 board statement and the June 22, 2021 sponsorship revocation are in the NFB's press room statement, "National Convention Sponsorship Statement Regarding accessiBe."
3. FTC, "FTC Approves Final Order Requiring accessiBe to pay $1 Million," April 22, 2025. $1 million payment, barred claims, third-party review allegation, 3–0 vote. The January 2025 complaint announcement is linked from the same page.
4. UsableNet, "Web Accessibility Lawsuits Tracker". July 2026: 401 suits, 77 repeat defendants, 113 defendants using a third-party widget.
5. WCAGpatch product facts, checked 2026-09-07: fixes are written to WordPress fields, nothing runs in the visitor's browser, and the 30 to 40 percent automated-coverage disclaimer is the one in this site's footer.