Do accessibility overlays make a website ADA compliant?

No. An overlay runs on top of your site and cannot reliably fix problems in your theme code, forms or content. There is no regulation or court standard that treats installing an overlay as compliance.

What did the FTC do about accessiBe?

In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million. The FTC had alleged the company's claims that its widget could make any website WCAG compliant were false, misleading or unsubstantiated.

Should I remove the accessibility widget from my website?

In most cases, yes, once you have a plan to fix the real issues. Removing it is usually low risk, it can remove conflicts with visitors' own assistive technology, and it takes a third-party script off every page.

Are all accessibility plugins overlays?

No. Plugins that fix specific code problems, such as adding skip links or correcting focus styles in your theme, are different from overlays that try to repair the page in the browser after it loads.

Why Accessibility Overlays Don't Make Your Website ADA Compliant

Accessibility overlays are widgets you add with one line of JavaScript. They put an accessibility icon on your site and claim to fix problems automatically. They do not make a website compliant with the Americans with Disabilities Act (ADA) or with the Web Content Accessibility Guidelines (WCAG), because most accessibility problems live in your site’s code and content, and a script running on top cannot reliably fix them. In 2025, the Federal Trade Commission ordered one of the best-known overlay vendors to pay $1 million over its compliance claims.

This article is general information, not legal advice.

What an accessibility overlay is

An overlay is a third-party script that loads after your page. It usually does two things:

Adds a toolbar. Visitors click an icon and get buttons to enlarge text, change contrast, stop animations, or switch fonts.
Tries automated repairs. The script scans the page and changes the code in the browser. It might guess alternative text for images, add ARIA attributes, or try to label form fields.

Overlays are sold with phrases like “compliance in 48 hours” or “one line of code.” On a WordPress site, they are usually added through a plugin or a script in the header. They are attractive because they are fast and cheap compared with fixing a theme. That is exactly the problem.

Why overlays can’t make you compliant

The problems are in your code and content

WCAG tests whether people can actually use your site. Most failures we find on WordPress sites come from the theme, the page builder, form setup and content. For example:

A dropdown menu that only opens on mouse hover.
A modal popup that traps keyboard focus or does not return focus when closed.
Form errors that are only shown in red text and not announced to screen readers.
A product image whose alternative text needs to say what makes this product different.
A video with no captions.
A PDF menu or price list that is a scanned image.

An overlay cannot know what your images mean, cannot caption your videos, cannot fix your PDFs, and cannot reliably rewrite custom JavaScript components it did not build. When it guesses, it can guess wrong, and a wrong label can be worse than no label because it sounds confident.

Disabled users already have their own tools

People who rely on assistive technology already have it: screen readers such as NVDA, JAWS and VoiceOver, screen magnifiers, browser zoom, high-contrast modes and speech input. They set these up for their own needs and use them on every site.

An overlay toolbar duplicates these tools for one website only. The changes it makes to the page can also conflict with a user’s screen reader or settings. A blind person does not need a “screen reader mode” button that they would have to find with a screen reader in the first place. What they need is a page that is coded correctly.

Automated testing has known limits

Automated checks are useful, and we run them on every audit. But the World Wide Web Consortium (W3C), which publishes WCAG, says that tools cannot check all accessibility aspects automatically and that human judgment is required. If automated tools cannot fully test a page, an automated script cannot fully fix one either.

There is no legal safe harbor for overlays

The U.S. Department of Justice (DOJ) does not have a rule for private business websites that names a specific technical standard, and nothing in its guidance on web accessibility and the ADA says that installing a widget meets the law. The DOJ’s 2024 rule for state and local governments requires web content to meet WCAG 2.1 Level AA. Meeting a WCAG standard is about what users actually get, not which tools you installed. We cover the legal background in our ADA compliance guide for WordPress.

What the FTC found

The Federal Trade Commission (FTC) took action against accessiBe, an overlay vendor that marketed a product called accessWidget. According to the FTC’s April 2025 announcement:

accessiBe claimed accessWidget could make any website WCAG compliant.
The FTC’s January 2025 complaint alleged that the widget did not make all user websites WCAG compliant, and that these claims were false, misleading or unsubstantiated.
The complaint also alleged the company formatted third-party articles and reviews to look like independent opinions without disclosing its connections to the reviewers.
The final order, approved on April 22, 2025, requires accessiBe to pay $1 million and bars it from claiming its automated products can make websites WCAG compliant, or keep them compliant over time, unless it has evidence to support those claims.

The FTC case was about advertising claims, not about the ADA directly. But it is a clear signal: a federal agency looked at the “one line of code makes you compliant” promise and found it was not backed up.

Signs you are looking at an overlay pitch

You do not need to know vendor names to spot an overlay. Watch for these claims:

Claim	Why it should worry you
“Compliance in 48 hours” or “instant compliance”	Real fixes take time because they change code and content.
“Just one line of code”	One script cannot rewrite every template and component on your site.
“AI fixes your site automatically”	Automated repair is limited by the same gaps as automated testing.
“Includes litigation support” or a compliance certificate	No government agency certifies websites as ADA compliant.
A floating accessibility icon as the main deliverable	A toolbar is a feature, not a fix.

Overlays versus accessibility plugins

Not every WordPress accessibility plugin is an overlay. The difference is what it changes and where.

Overlays load a third-party script that tries to repair the page in the visitor’s browser after it loads.
Code-level plugins and theme fixes change the HTML and CSS your server sends, such as adding a skip link, removing title attributes that repeat link text, or restoring visible focus outlines.

Code-level fixes can help, especially for small, known issues. But even good plugins cannot fix your content, your page builder’s layouts or your custom forms. They are tools in a remediation plan, not a replacement for one.

What to do instead

1. Get a real audit

Start by finding out what is actually wrong. A useful audit tests your main templates and forms with automated tools, a keyboard and a screen reader, and gives you a list ranked by impact. Our guide on how to audit WordPress accessibility explains how we do it.

2. Fix issues where they live

Fix theme templates, menus, modals and form markup at the source. Train editors to write good alternative text and use headings correctly. A theme-level fix often clears the same problem on hundreds of pages at once.

3. Target WCAG 2.2 Level AA

WCAG 2.2 is the current version, and the W3C states that meeting it also meets WCAG 2.1. Our overview of WCAG 2.2 changes for WordPress covers the newer requirements, such as target size and accessible login.

4. Remove the overlay when you are ready

Once you have a plan, removing the overlay is usually low risk. It also removes a third-party script from every page, which is good for speed. Third-party scripts are a common cause of slow interactions; see our guide to Core Web Vitals for WordPress.

5. Keep testing

Add automated accessibility checks to your update process and repeat manual checks on new templates. Accessibility is like any other kind of technical debt: it builds up quietly unless you measure it.

Get real accessibility fixes for your WordPress site

If you have an overlay installed and want to know where your site really stands, our ADA compliance service audits your site against WCAG 2.2 Level AA and fixes issues in your theme, forms and content. Contact us and we will look at what you have today.

Frequently asked questions

Do accessibility overlays make a website ADA compliant?: No. An overlay runs on top of your site and cannot reliably fix problems in your theme code, forms or content. There is no regulation or court standard that treats installing an overlay as compliance.
What did the FTC do about accessiBe?: In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million. The FTC had alleged the company's claims that its widget could make any website WCAG compliant were false, misleading or unsubstantiated.
Should I remove the accessibility widget from my website?: In most cases, yes, once you have a plan to fix the real issues. Removing it is usually low risk, it can remove conflicts with visitors' own assistive technology, and it takes a third-party script off every page.
Are all accessibility plugins overlays?: No. Plugins that fix specific code problems, such as adding skip links or correcting focus styles in your theme, are different from overlays that try to repair the page in the browser after it loads.