WCAG & Testing
Does an Accessibility Overlay Make Your Website ADA Compliant?
An accessibility overlay is a line of JavaScript that promises to fix a website's accessibility automatically. In January 2025 the Federal Trade Commission acted against one of the best-known vendors over exactly that promise. A widget cannot repair markup it did not write, and no honest test result comes out of one.
Sources
Key takeaways
- The FTC acted on the marketing, not the category: the case was about claims a tool could make any site WCAG compliant in 48 hours.
- What the FTC said was still broken: navigation menus, form fields and image descriptions.
- Overlays do not remove the obligation: the standard applies to your web content, whatever script is layered on top of it.
- A toolbar is not a test: changing contrast or font size for a visitor tells you nothing about whether the page conforms.
What did the FTC actually find about an accessibility overlay?
On January 3, 2025 the Federal Trade Commission announced a proposed settlement with accessiBe under which the company would pay $1 million. The FTC alleged the company marketed its AI-powered plug-in as able to make any website conform to WCAG within 48 hours, while navigation menus, form fields and image descriptions were still not accessible. The FTC also alleged the company ran paid advertisements formatted to look like independent third-party reviews without disclosing the payments.
In detail
Read the action for what it is. The FTC did not rule that overlays are unlawful or that every overlay vendor makes false claims. It acted against specific advertising claims it said were deceptive. The useful lesson for a public entity is narrower and more practical: a vendor's conformance promise is a marketing statement until somebody independent measures the pages and publishes the result.
Why can a script not fix accessibility after the fact?
Because most of WCAG is about meaning, and meaning is not recoverable from the outside. Whether alternative text describes the right thing, whether a heading structure reflects the actual outline of a page, whether a link's text makes sense away from its sentence, whether a form error explains what to do next: each takes a judgement about intent. The W3C, which writes WCAG, is explicit that automated tools cannot evaluate every requirement.
In detail
There is a second-order problem too. An overlay that guesses wrong does not leave the page as it was; it can announce an incorrect description confidently to somebody who has no way to check it. Our guide on automated scans versus human review sets out which checks genuinely belong to a machine and which need a person.
Is a usability widget ever worth having?
It can be, as long as nobody mistakes it for conformance. A toolbar that lets a visitor raise contrast or enlarge text is a convenience some people like. What it is not is evidence. If a widget is on your site, keep it in the convenience column of your own records, and keep your WCAG 2.1 AA testing entirely separate from it.
What does an entity put in its file instead?
Measurements with dates on them. A written baseline against WCAG 2.1 Level AA, findings tied to specific URLs and success criteria, a person verifying each one, and a repeat scan that shows what changed. That is the record that answers a question from a board, a resident or a regulator, and it is what the initial assessment and monthly monitoring are built to produce.
ADA Site Monitor sells no overlay, no widget and no certificate. Monitoring is the only thing we sell, which is why a finding costs us nothing to report.