For businesses

Do accessibility overlay widgets make a website compliant?

No overlay makes a site compliant, because it runs on top of the page and leaves the site's own code, which audits and courts judge, unchanged.

By GladLoop · · 7 min read

No overlay widget can make a website compliant on its own. Accessibility standards such as WCAG are met or failed by the site's own code and content, and an overlay is a script that runs on top of the page after it loads. In 2025 the US Federal Trade Commission finalised an order requiring one overlay vendor, accessiBe, to pay $1 million over claims that its product could make any website WCAG-compliant.

This is general information, not legal advice.

What is an accessibility overlay?

An overlay is a piece of third-party JavaScript added to a site, usually with one line of code. Most show a small icon that opens a toolbar with options such as larger text, higher contrast or a reading guide. Many also claim to scan the page and repair problems automatically, for example by adding missing image descriptions or labels while the page is running in the visitor's browser.

The appeal is obvious. One line of code and a monthly fee look much cheaper than a code audit and a round of fixes.

What did the FTC find?

In January 2025 the FTC announced a proposed order against accessiBe, which sells a plug-in called accessWidget. The complaint alleged that the company claimed the plug-in could make any website compliant with WCAG, and that "accessWidget did not make all user websites WCAG-compliant." It also alleged that the company formatted third-party articles and reviews so they looked independent without disclosing its connection to the reviewers.

The Commission approved the final order on April 22, 2025, by a 3-0 vote. It requires the $1 million payment and bars the company from claiming that its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has evidence to support the claim. The full case record is on the FTC's case page.

The order concerns what one company said in its marketing. It does not ban overlays, and it does not say anything about other vendors. What it does show is that a US regulator examined the claim "our widget makes your site compliant" and found it was not supported.

Do sites with overlays still get sued?

Yes. UsableNet, which tracks US digital accessibility lawsuits, publishes monthly counts of cases filed against companies that had a widget on their site. In its 2025 year-end report, those monthly figures add up to more than 1,400 cases for the year, out of more than 5,000 digital accessibility lawsuits in total. The report states that widgets "did not slow litigation in 2025."

According to the same report, a growing number of lawsuits referred to the widget directly while alleging code-level barriers that had not been fixed. A widget running on top does not remove those barriers from the underlying page, so the claim can still be made.

Why can't a script fix the problems automatically?

Some problems can be detected by software. Deciding the right fix usually takes a person who knows what the page is for.

Take image descriptions. A script can see that an image has no alternative text. It cannot know whether the image is a decorative flourish that screen readers should skip, a product photo that needs the colour and model named, or a chart whose numbers need to be written out. The same goes for link text, form instructions, heading structure and the order in which keyboard focus moves through a page.

The W3C, which publishes WCAG, puts it plainly: evaluation tools cannot determine accessibility, they can only assist, and human judgement is required. That is about finding problems, and fixing them takes more judgement again.

The Overlay Fact Sheet, a statement signed by more than a thousand accessibility practitioners, developers, lawyers and disabled users, makes the same point in stronger terms: "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard and therefore cannot eliminate legal risk."

What do disabled users and practitioners think of them?

Opinion among people who do this work is largely negative. In WebAIM's 2021 survey of web accessibility practitioners, with 758 valid responses, 67% rated overlays, plugins or widgets as not at all or not very effective. Among respondents with disabilities the figure was 72%, and only 2.4% rated them very effective.

UsableNet's report adds that widgets "may interfere with assistive technologies such as screen readers." People who rely on a screen reader or magnifier have usually set it up the way they need it, for every site they visit, and a toolbar on one site adds another layer to that setup.

What does compliance actually require?

It depends on the law, but each one looks at the site itself.

  • In the US, the ADA Title II rule for state and local governments names WCAG 2.1 Level AA, with compliance dates of April 26, 2027 and April 26, 2028 after an April 2026 extension. For private businesses under Title III, the Department of Justice says websites must be accessible and leaves the method flexible.
  • In the EU, the European Accessibility Act requires covered services, including e-commerce, to make their websites perceivable, operable, understandable and robust, and to publish information explaining how the service meets the requirements.

In each case the test is whether a disabled person can use the site. An audit checks the page's markup, keyboard behaviour, contrast, forms and content against WCAG. Those are properties of the site's code.

We already have a widget installed. What should we do?

You do not have to remove it today. The priority is finding out what the site underneath is like.

  1. Have the site audited with the widget switched off, so the report shows the barriers in your own code.
  2. Fix the blocking problems in the templates and content, starting with checkout, sign-up and contact forms.
  3. Check any accessibility statement or footer badge on your site. If it says the site is "compliant" because of the widget, rewrite it to describe the standard you are working towards and how people can report problems.
  4. Once the code fixes are in, decide whether the toolbar still earns its place. Test it with a screen reader and a keyboard before keeping it.

Questions people also ask

Are all automated accessibility tools a bad idea?

No. Automated checkers that report problems to your developers are useful and widely used, because a person then reviews each finding and fixes it in the code. The difference is that nothing is claimed to be fixed until someone has changed the site.

Will an overlay protect us from a lawsuit?

The lawsuit data points the other way. UsableNet's 2025 figures show more than 1,400 US lawsuits against companies that had a widget installed.

Did the FTC ban accessibility overlays?

No. The 2025 order applies to accessiBe and to its marketing claims. It bars the company from claiming its automated products make websites WCAG-compliant without evidence, and it requires a $1 million payment.

Do overlays help with the European Accessibility Act?

The Act sets requirements for the service itself and asks providers to explain how their service meets them. A toolbar does not change the underlying website, so the site still has to be assessed and fixed against the requirements.

Sources

Related articles