If you use an accessibility widget on your site, or you’re thinking about adding one, you need to know about this. In April 2025, the Federal Trade Commission approved a final order against an accessibility overlay provider, requiring the company to pay $1 million for making false claims about what its product could do. The order has real implications for anyone in the accessibility space, including how to evaluate the tools you trust with your site.
Here is what actually happened, in plain language.
What the FTC Found
The company told customers its AI-powered plug-in could make any website compliant with the Web Content Accessibility Guidelines (WCAG), automatically, and within 48 hours. According to the FTC’s final order, those claims were false, misleading, and unsubstantiated.
The FTC’s complaint noted something important: accessibility overlays are not designed to permanently alter a website’s code. They make temporary modifications to how a page appears and behaves in the visitor’s browser, things like contrast, text size, and animated elements. That is genuinely useful. But it is a different thing entirely from making a website WCAG-conformant at the source-code level.
The FTC also found the company formatted third-party articles and reviews to look like independent opinions while failing to disclose that those reviewers had material connections to the company. In other words, paid content was dressed up as organic praise.
The final order bars the company from claiming its automated products can make any website WCAG compliant, or that they can ensure continued compliance over time, unless the company has the actual evidence to back those claims.
The Claims That Crossed the Line
This matters beyond one company and one fine. It establishes what the FTC considers a deceptive claim in the accessibility widget space. Based on the order, the phrases that got the company into trouble fall into a clear pattern:
- Claiming a tool can make any website “WCAG compliant” automatically.
- Promising compliance within a specific timeframe without evidence.
- Stating or implying the tool provides ongoing compliance with no additional work required.
- Formatting paid reviews and articles as if they were independent assessments.
None of those things are true of any browser-side accessibility widget. An overlay addresses the user-facing layer. It cannot rewrite heading structure, fix broken ARIA attributes, or repair keyboard navigation in your source code. That work requires a developer. A tool that tells you otherwise is not being straight with you.
What to Look For in an Honest Accessibility Tool
The FTC order is a useful filter. When you’re evaluating any accessibility widget, the language the provider uses tells you a lot. Watch for:
- “Fully compliant” or “achieves compliance”, these are red flags if they appear without significant qualification.
- “Compliant in X hours or days”, no overlay can make that promise in good faith.
Reviews and case studies that don’t disclose any relationship to the provider.
Compare that to what an honest tool should say: it adds user-facing accessibility features, it supports your compliance efforts, and it does not replace the source-code remediation required for full WCAG conformance.
That is exactly how AccessPro describes what it does. We are careful about our claims because overclaiming does not help you, it just creates legal exposure for your business and ours. If you want to understand in detail what an overlay actually does and does not do, we published a full breakdown at What Accessibility Overlays Can and Cannot Do, which covers the honest line between what a widget handles and what needs developer work.
What This Means for Your Site
If you are a site owner, the practical takeaway is straightforward. An accessibility widget is a real and valuable tool. It gives your visitors controls they would not otherwise have — contrast, text size, text-to-speech, dyslexia-friendly fonts, and more. It demonstrates a genuine commitment to inclusion. For many visitors, it makes a real difference.
What it is not is a legal shield on its own. The FTC order makes clear that the gap between “adds user-facing accessibility features” and “makes your site WCAG compliant” is the exact gap where legal exposure lives. A tool that honestly describes what it does gives you something to stand on. A tool that overclaims its abilities gives you false confidence and the same legal exposure you were trying to avoid.
If you are unsure what your site actually needs, whether that is a widget, source-code remediation, or both, get in touch and we can walk you through it.