For years, accessibility overlay companies marketed their products with a simple promise: install our widget, and your website is compliant. Federal regulators are now pushing back. Reports indicate the Federal Trade Commission reached a settlement with a prominent accessibility overlay provider over misleading marketing claims — a development that should cause every WordPress site owner relying on a widget to stop and reassess their strategy immediately.
What the FTC Action Signals
The FTC’s core concern is straightforward: overlay providers were claiming their AI-powered tools would bring websites into ADA compliance when the technology cannot deliver on that promise. A widget that sits on top of your website’s existing code and applies cosmetic adjustments is not the same as actually fixing the underlying HTML. Regulators are now treating that distinction as a consumer protection issue — and that has implications for the entire overlay industry.
For WordPress site owners, this isn’t just a story about an overlay company getting fined. It’s a signal that the “buy a widget, check the compliance box” era of web accessibility may be closing — not just in the courts, but in federal regulatory enforcement. The message from regulators: if a product can’t do what it claims, selling it as a compliance solution is deceptive.
The Litigation Data That Raised Red Flags
Before regulators acted, the lawsuit data had already told a troubling story. According to the AudioEye 2026 Web Accessibility Litigation Report, the relationship between overlays and legal exposure is the opposite of what vendors promise:
- 22.6% of all federal ADA web accessibility lawsuits filed in the first half of 2025 targeted websites that already had an overlay tool installed
- Nearly 40% of businesses sued for web accessibility violations in 2025 had some form of accessibility tool in place at the time of filing
- 8,667 ADA Title III federal lawsuits were filed in 2025, with thousands more filed in state courts — and that number continues to rise
Let those numbers sink in. Installing an overlay doesn’t just fail to provide legal protection — it may actually make your site a more attractive target for plaintiffs’ attorneys. Having an overlay demonstrates awareness of accessibility requirements. When a disabled user still cannot access your site despite that awareness, the overlay can become evidence of willful non-compliance rather than a good-faith effort.
Settlement costs tell the rest of the story. Out-of-court resolutions average $30,000; court judgments average $85,000; and legal fees run $30,000–$175,000 on top of any settlement amount. A few hundred dollars per year for an overlay subscription is not a hedge against those numbers.
Why Courts Keep Rejecting Overlay Defenses
Courts have been consistent on this point: overlays do not satisfy ADA requirements. This isn’t a gray area of interpretation — multiple court decisions have established that a tool modifying the user-facing interface without fixing the site’s actual code does not make a website accessible to people with disabilities.
Here’s the technical reality behind those rulings:
- Coverage gap: Automated overlay tools can detect and address roughly 30% of accessibility issues, leaving the remaining 70% intact in your underlying code
- Screen reader interaction: Assistive technology reads your site’s actual HTML — not the overlay’s cosmetic layer — so users relying on screen readers still encounter unlabeled images, broken form fields, and missing ARIA attributes
- Keyboard navigation: Keyboard-only users depend on proper tab order and focus management baked into your site structure — overlays rarely fix these structural problems
- Load timing: The overlay activates after JavaScript loads, leaving a window where the inaccessible version of your site is what users first encounter
- Real user testimony: Courts have admitted testimony from disabled users demonstrating that overlays fail in practice, regardless of vendor marketing claims
The FTC’s scrutiny of overlay providers for misleading marketing aligns precisely with what courts have been ruling for years: these tools don’t do what they say they do.
What This Means If You Have an Overlay Installed Right Now
If you currently run an accessibility overlay on your WordPress site, here is the practical situation:
- The overlay is not your legal shield. The data shows overlay installation correlates with — not against — lawsuit exposure.
- Regulatory risk now runs two directions. Not only can you be sued for having an inaccessible site, but the overlay tools you relied on are now under FTC scrutiny for claims they cannot back up.
- The overlay may signal non-compliance rather than a compliance effort. Courts look at whether organizations made good-faith remediation efforts. An overlay that demonstrably fails real users does not meet that bar.
None of this means you need to panic. It means you need to shift your strategy from surface-level fixes to actual remediation — and the sooner the better, given where enforcement trends are heading.
What a Real Accessibility Compliance Program Looks Like
The approach that holds up in court — and actually serves your users — looks like this:
- Scan for real code-level issues. Run a WCAG 2.2 Level AA audit that identifies actual violations in your HTML: missing alt attributes, unlabeled form fields, insufficient color contrast ratios, keyboard traps, and missing focus indicators.
- Fix the underlying code. Remediation means changing your theme, templates, or plugin output — not applying a JavaScript layer on top of broken markup.
- Document your work. Courts look more favorably on organizations that can demonstrate an ongoing, documented compliance program than those that installed a widget and called it done.
- Scan on a schedule. Accessibility issues get introduced with every theme update, plugin change, and new content addition. A one-time audit is not enough.
- Publish an accessibility statement. Communicating your commitment and providing a contact method for users to report issues demonstrates ongoing good faith to both regulators and courts.
This is more work than installing an overlay. It’s also the only approach that actually reduces your legal risk — and more importantly, ensures your site works for the estimated 1.3 billion people worldwide who live with some form of disability.
Take Action
LEWCA is a WordPress accessibility plugin built on the principle that real accessibility requires fixing real code. Its WCAG scanner identifies actual code-level violations — not surface symptoms — across your pages, posts, and templates. LEWCA Pro adds AI-powered fix suggestions, scheduled scanning, and compliance reports you can document and share. Unlike overlays, LEWCA works with your site’s actual markup, so improvements hold up for real users with assistive technology — and hold up when it matters legally. Download LEWCA free to run your first scan, or view pricing to see what Pro adds to your compliance program.