Accessibility overlays are a category of JavaScript widgets marketed as an ADA compliance solution. You install a snippet on your site. The widget adds a button. Users click it and get a menu of options like larger text, higher contrast, or a simplified layout. The vendor claims the product makes your site accessible and compliant.
The short answer to the title of this article. No. Overlays do not make a website ADA compliant. The Federal Trade Commission, the accessibility research community, and the plaintiff's bar all agree on this specific point, which is unusual.
This article walks through why.
What overlays claim
The marketing from overlay vendors varies by product but generally claims some combination of the following:
- Automated detection and remediation of accessibility issues
- WCAG 2.1 AA conformance via artificial intelligence
- Protection from ADA lawsuits
- Compliance with ADA requirements by adding the widget
These claims have been the subject of regulatory action. In 2025 the Federal Trade Commission took enforcement action against accessiBe, one of the largest overlay vendors, for making false or misleading claims of exactly this type. The FTC order required refunds to customers and substantiation of future claims.
Why the technology does not do what the marketing says
There are two levels of critique. The technical one and the legal one.
Technical. Overlays work by injecting JavaScript at page load and attempting to identify and modify accessibility-relevant elements of the page after it has been rendered. A few things about this approach limit its effectiveness.
The widget cannot correctly identify content intent. An image without alt text could be decorative or could be conveying information. A button that says "Submit" could be submitting a form to buy a product or to delete an account. Automated systems cannot reliably decide what a human wrote. Some overlays use machine learning for image recognition, which has improved, but the gap between automated alt-text generation and accurate alt-text is still substantial.
The widget modifies the DOM at runtime, which can conflict with other JavaScript on the page. Frameworks that re-render components can undo the overlay's modifications. Keyboard users and screen reader users often experience the modifications as additional confusion rather than accessibility.
The widget is itself an assistive-technology-adjacent tool that adds an interface users must learn. Screen reader users have their own assistive technology. They do not need an overlay to adjust font size; they use the accessibility features already in their operating system or reader. A widget that claims to provide accessibility features a user already has is adding friction rather than removing it.
A 2024 WebAIM survey of screen reader users found that the majority reported overlays made their experience worse. Users interviewed cited interface confusion, conflicts with their primary assistive technology, and a perception that the overlay was a substitute for real accessibility work.
Legal. Overlays are not a defense under Title III. This has been true throughout the existence of the overlay industry and has been tested in court.
Federal district courts have declined to accept overlay installation as a defense to a Title III claim. A typical ruling notes that the presence of an overlay does not modify the underlying site code. If the underlying site fails WCAG success criteria, the claim proceeds regardless of the overlay.
Plaintiff's firms have gone further and cited overlay presence in complaints as evidence of awareness of accessibility issues without actual remediation. The argument is that the defendant purchased a product marketed as an ADA solution, which establishes the defendant knew the obligation existed, while the underlying accessibility failures remain present.
The FTC action against accessiBe
The 2025 FTC action deserves its own section because it is the clearest regulatory statement on the overlay category. See our full breakdown of the accessiBe settlement for the specific order terms and what they mean for your business.
The FTC complaint alleged that accessiBe had made unsubstantiated claims including:
- That its product made websites fully ADA compliant
- That its artificial intelligence could identify and remediate all accessibility issues
- That businesses using its product were protected from ADA lawsuits
The settlement order required accessiBe to refund consumers, to substantiate future compliance claims, and to stop making statements that the product provides full ADA compliance without corroborating evidence.
The action does not prohibit accessibility overlay products generally. It addresses specific marketing claims by one vendor. But the implications for the category are substantial. Other vendors have revised their marketing language. Courts citing the action in Title III cases have treated it as a data point suggesting overlays are not a reliable compliance path.
What overlays can legitimately do
The category is not zero. Overlays can provide some real, if limited, functionality.
Stylistic adjustments. Larger text, higher contrast, simplified color palettes. These features exist in browsers and operating systems already, but an in-page button that toggles them can reduce friction for users who do not know where the browser controls are.
Color blind filters and reading guides. Some overlay products offer color transformations or reading guides that can be useful for specific conditions.
Quick contrast fixes. A site with low-contrast text can have its contrast elevated by an overlay's stylesheet injection, which is a real improvement for users who activate the feature.
These benefits are real and modest. They do not add up to ADA compliance. A site with overlay-provided contrast toggles and no alt text on its images still fails WCAG. A site with an overlay and no keyboard operability still fails WCAG.
Why overlays are still sold
A few reasons.
The market demand is real. Small business owners want a button they can push to solve an unfamiliar legal exposure. An overlay is a button.
The pricing is low compared to remediation work. A monthly subscription at tens of dollars per month feels less burdensome than a multi-thousand-dollar audit and remediation engagement. The total cost of the subscription plus a settled demand letter usually exceeds the cost of actual remediation, but that is not apparent at the point of purchase.
Some vendors offer indemnification or litigation insurance as part of the package. The insurance component can be genuine. A vendor that agrees to pay the first fifty thousand dollars of a settlement is providing a real financial product, even if the overlay itself is not a legal defense. Small businesses that have bought overlay products with indemnification attached have sometimes had settlements covered.
The indemnification does not change the underlying accessibility of the site. Users still cannot use the site. The lawsuit still gets filed. The defendant still has to remediate as part of the settlement. The indemnification just changes who writes the check.
What to do if you already have an overlay installed
Three options.
Remove the overlay and do real remediation. The cleanest approach. Audit the site with axe DevTools, WAVE, or a paid tool. Fix findings. Publish an accessibility statement — use our template that does not overpromise — that reflects your actual work.
Keep the overlay and do real remediation. Less clean but sometimes preferred by business owners who have already paid for the annual subscription. The overlay's presence is a minor negative in a legal defense but not fatal if the underlying site has been remediated and documented.
Keep the overlay and do nothing else. The worst option. The overlay does not fix your site. The demand letters that arrive are stronger because plaintiff's firms can cite the overlay as evidence of awareness.
The bottom line
Overlays are not ADA compliance. They are a product that is marketed as ADA compliance. The FTC has said so. Courts have said so. The research community has said so.
If you have a website, either remediate it, or do not. Overlays are not a third option that lets you skip the work. Start with the WCAG 2.1 AA requirements to understand what real compliance looks like.
This is not legal advice. For specific legal questions about your site or an active claim, consult a licensed attorney.