- ADA compliance
- overlays
- FTC
- WCAG
Do Accessibility Overlay Widgets Make Your Website ADA Compliant?
What accessibility overlays are, what the FTC said in its 2025 accessiBe order, and why fixing your site's actual code matters more than a widget.
On this page
If you have looked into website accessibility, you have probably seen ads for a quick fix: paste one line of code into your site, and a widget makes it accessible and compliant. For a busy small business owner, that sounds perfect.
Before you buy, it helps to know what these tools are, what they can and can't do, and what the Federal Trade Commission said about one of them in 2025.
This is not legal advice. ComplyKit is not a law firm. If you are responding to a demand letter or lawsuit, talk to an attorney before choosing any tool or vendor.
What is an accessibility overlay?
An overlay is a script added to your website, usually with a single line of code, that runs in the visitor's browser. Many show a small icon that opens a menu of options, such as larger text, higher contrast, or a dyslexia-friendly font. Some also claim to detect and repair accessibility problems automatically, sometimes using artificial intelligence.
The key point: an overlay sits on top of your website. Your site's underlying code, the part that screen readers and other assistive technologies actually read, usually stays the same.
What the FTC said about accessiBe
In April 2025, the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million. According to the FTC's announcement:
- The FTC's complaint said accessiBe claimed its product, accessWidget, "can make any website compliant with Web Content Accessibility Guidelines (WCAG)."
- The complaint alleged that "accessWidget did not make all user websites WCAG-compliant," and that the company's claims were false, misleading, or unsubstantiated.
- The complaint also alleged that accessiBe "deceptively formatted third-party articles and reviews to appear as if they were independent opinions" and failed to disclose its material connections to those reviewers.
- The order bars accessiBe from claiming that its products "can make any website WCAG-compliant or can ensure continued compliance with WCAG over time" unless it has evidence to support those claims.
That order is about one company and its marketing claims. It does not say every overlay is useless or that every overlay vendor has broken the law. But it is a clear signal that "install this and you're compliant" is a claim regulators take seriously, and one that buyers should question.
What the Justice Department says about these tools
The Justice Department's Guidance on Web Accessibility and the ADA takes a balanced view. It says automated accessibility checkers and overlays "that identify or fix problems with your website can be helpful tools," but that "they need to be used carefully."
It also warns that "a 'clean' report does not necessarily mean everything is accessible," and that "pairing a manual check of a website with the use of automated checkers can give you a better sense of the accessibility of your website."
In other words: tools can help, but no tool is a substitute for checking that real people can actually use your site.
Why code-level fixes matter
People who are blind or have low vision often use screen readers, software that reads a page's code aloud. People with motor disabilities may use only a keyboard, or voice control, or a switch device. Many of them already have their own tools configured exactly how they like them.
Those tools rely on your site's code being built correctly. For example:
- A screen reader can only describe an image if the code includes a text description (alt text). A good description depends on knowing what the image means in context, such as which product it shows or why it is on the page.
- A form field is only announced correctly if it has a real label connected to it in the code.
- A menu only works with a keyboard if it was built from elements a keyboard can reach and operate.
When these things are fixed in your actual site, they work for every visitor, with whatever assistive technology they use, whether or not a script loads. That is also why our own reports focus on showing you, or your web person, how to change the underlying code and content.
What overlays can't easily do
Some accessibility problems require human judgment that no script can supply reliably:
- Writing meaningful alt text. Whether an image is decorative or important, and what it should say, depends on your business and your page.
- Clear link text and headings. Rewriting "click here" into something meaningful requires understanding the content.
- Captions and transcripts that are accurate.
- Logical page structure, like a sensible heading order and reading order.
- Complex interactions, like booking tools, carts, and checkout flows that must work from start to finish.
The W3C, which publishes WCAG, makes the same point about testing tools in general: tools "can not determine accessibility, they can only assist in doing so," and "human judgement is required."
The honest limits of any automated tool, including ours
ComplyKit is an automated scanner, so we want to be just as clear about our own limits:
- An automated scan finds many common, detectable problems, but not all WCAG issues. WebAIM's WebAIM Million report notes that "not all conformance failures can be automatically detected."
- A good scan result does not mean your site is compliant, and it does not prevent lawsuits or demand letters.
- The value of a scan is a clear, prioritized list of real problems to fix in your code and content, plus a dated record of your progress.
What to do instead of (or alongside) a widget
- Scan your site to find common, detectable problems. Start with a free homepage scan.
- Fix the problems in your site's code and content. Our guide to the 10 most common website accessibility problems shows simple before-and-after examples.
- Get a manual review of your most important pages and flows by an accessibility professional.
- Keep monitoring as you add pages and products.
If you already have an overlay installed, you don't have to rip it out today. Just don't treat it as the finish line. Make sure the underlying problems are actually fixed.
Wondering about budget? See how much it costs to make a website ADA compliant. Want to understand the standard itself? Read WCAG 2.1 AA explained for small business owners.
Got a demand letter already?
Don't ignore it, and talk to an attorney before responding. Our step-by-step guide, Got an ADA Website Demand Letter? What Small Business Owners Should Do First, covers the first week.
ComplyKit's Demand Letter Response Kit ($199 one time) includes a full scan of up to 5 pages, a dated PDF report for your attorney, a fix guide for your web person, and 30 days of monitoring, then $29/month. Cancel anytime. It is designed to help you find and fix real problems in your code, not to paper over them.