Accessibility overlays explained: what they do, what critics say and what to do instead

What an overlay is

An accessibility overlay (also called a widget) is a third-party script you add to your site. It typically shows an icon that opens a menu for changing font size, contrast or spacing, and may try to detect and automatically patch problems in the page as it loads, sometimes using AI.

What critics say

• Problems in the underlying code, such as unlabeled controls or keyboard traps, are often not fixed or are patched incompletely, so people using assistive technology still hit them.
• People who rely on a screen reader or keyboard already have their own tools and settings, and an overlay can interfere with them.
• Overlays do not fix content decisions such as meaningless alt text, confusing forms or inaccessible PDFs.
• Marketing sometimes implies that installing one makes a site compliant, which no tool can do.

A group of accessibility professionals published the Overlay Fact Sheet setting out these objections and has collected signatures from practitioners. Vendors dispute some of these points, and some offer user-preference toolbars alongside other services.

What the FTC and DOJ have said

• In January 2025 the Federal Trade Commission announced a $1 million settlement with accessiBe over allegations that it misrepresented the ability of its AI tool to make any website meet WCAG, and over undisclosed paid reviews. In April 2025 the Commission approved the final order, which bars the company from claiming its automated products can make any website meet WCAG, or keep it that way over time, unless it has evidence to support the claim. The action concerns that company's claims. It is not a ruling on every overlay. Read the FTC announcement and the final order announcement.
• DOJ's web accessibility guidance says automated tools can be helpful but need to be used carefully, and that a clean automated report does not mean a site is accessible. Read the guidance.

Overlay versus fixing the code

How overlays are sold, and why the pitch is persuasive

The appeal is easy to understand. A small business owner is told that accessibility is complicated, that a legal risk exists and that adding a line of code can solve the problem for a monthly fee. When someone is busy and worried, that is an attractive offer.

The difficulty is that web accessibility is mostly about how a page is built, and a script that runs afterwards has to guess. Some problems can be improved by guessing; many cannot. Because the product sits on top of the page, it cannot fix what is wrong in the checkout code, the form behind the contact page or the video without captions.

What overlay products tend to offer

• A toolbar that lets visitors enlarge text, change contrast, pause animations or highlight links.
• Automatic attempts to add missing alternative text, labels or roles by guessing.
• A statement, a badge or a report that says the site is monitored or supported.

Display controls can be useful to some people, but most people who need larger text or higher contrast already set this in their browser or device, and those settings work on every site. Many screen reader users report that overlays interfere with the tools they already use.

Where the evidence points

Several sources have raised concerns. The Federal Trade Commission took action against one overlay provider in 2025 over claims about what its product could do, as described in the sources below. Many accessibility professionals signed a public statement calling for overlay marketing to stop. Some sites that used overlays have still received legal letters, because the underlying problems remained.

That does not mean every visitor-facing tool is useless, or that every vendor acts in bad faith. It means a tool added on top is not a substitute for repairing the page, and any claim that it makes a site legally safe should be treated skeptically.

A cost-benefit view

If you already have an overlay

1. Do not panic and do not remove it before you have a plan. Some visitors may use its controls.
2. Run a scan and a keyboard test with the overlay on and off, and write down the difference.
3. Fix the underlying problems in order of impact, starting with checkout and forms.
4. Review the contract. Check what the vendor promises and whether you can cancel.
5. Remove or reduce any badge or statement that claims more than you can support, such as a line saying every visitor can use every page.
6. When the underlying fixes are done, decide whether the overlay adds anything you need.

Free options that cost nothing and help more

Before paying anyone, use the tools your visitors already have. Browsers can zoom, change text size and switch to dark or high-contrast modes. Operating systems include screen readers, voice control and magnifiers. Testing your site with these shows you what your visitors experience, and fixing what you find helps them directly. See how to check if a website is accessible.

Questions to ask before buying any accessibility product

1. Does it change my pages, or only how they appear for some visitors?
2. What happens to my site if the vendor's script is unavailable?
3. What evidence does the vendor offer for its claims, and who checked the evidence?
4. Do people who use assistive technology recommend it?
5. What does the contract say about legal claims? Does the vendor take responsibility, or does it only promise to try?
6. Can I leave easily, and what remains when I do?

What disabled users say

A recurring theme in discussions among screen reader users and other assistive technology users is that overlay controls duplicate features they already have and that automatic fixes can conflict with their own tools. Their preference is for sites that are built well in the first place. When you plan an accessibility project, consider asking disabled customers for feedback. Many are generous with their time when they see that a business is making a sincere effort.

Legal and regulatory context

No law says a website must carry an overlay, and none treats one as proof of accessibility. In the United States the ADA requires equal access, and courts and agencies look at whether people can use the services in practice. In the European Union the accessibility requirements refer to standards for the service, not to add-on tools. In both cases, repairing the site is what addresses the requirement. See ADA website compliance checklist.

A realistic order of operations

If an overlay is part of your plan, it should be the last item, a possible addition for visitors who find its controls helpful, and not a replacement for the first five steps.

A short history of the debate

Overlay products became popular as legal letters about websites increased, because they promised a fast and affordable answer. Accessibility professionals and disabled users soon raised concerns, in articles, open letters and conference talks. Reviews and court filings added examples of sites with overlays that still had barriers. Regulators then began to look at the claims made in advertising. The debate has not ended, but the main points of agreement are clear: an overlay changes the appearance of a page for some visitors, and it does not replace building the page well.

Frequently asked practical questions

• Will removing an overlay break my site? It should not, but test first. Keep a record of how the site looked and behaved before and after.
• Should I tell my customers I removed it? You do not have to, but an updated accessibility statement explaining what you are doing is a good idea.
• Can a toolbar ever be useful? Some visitors may find display controls convenient. If you offer them, label them honestly and make sure they work with a keyboard.
• What if my agency installed it? Ask them what they promised and what evidence they have. Then agree a plan to fix the underlying problems.

What good communication with customers looks like

Whatever tools you use, tell customers the truth about your site. If your store has barriers you have not fixed, say so and offer another way to buy. If you have made improvements, describe them plainly. Visitors forgive imperfection much more readily than overstatement. A short note such as "We are improving our site's accessibility and welcome your feedback" is honest, brief and open to people who need help. It also helps your support team, who will know what to say when someone writes in.

Avoid wording on the site that suggests a product has made the site compliant, approved or protected. These claims are hard to support and have been the subject of regulatory action.

Talking to a vendor who sells an overlay

Sales conversations can be reassuring and vague. Ask direct questions and write down the answers. What exactly does the product change on my pages? Which problems does it not fix? Will you put in writing what happens if I receive a legal claim? Can you show independent test results, with the method? Which of your customers can I speak to? A vendor confident in the product will answer clearly. If the answers are evasive, treat that as information.

Remember that no vendor can make a promise on behalf of a court. The most that any provider can honestly say is that their product may help with some issues.

If you remember one thing from this section, remember this: whatever you choose to add to your site, keep testing it with real use, and keep fixing the pages themselves. That is the work that lasts.

A practical alternative

1. Scan the pages that matter and list the findings.
2. Fix the code-level problems with the fix guides: contrast, labels, names, focus and alt text.
3. Test by hand for keyboard and zoom issues.
4. Recheck after each change and publish an accessibility statement.

Clir leaves your site untouched and shows your team what to fix in the pages themselves. It tests pages and gives you the findings and the fixes to make in your own code.