In late 2025 the FTC wrapped up its case against accessiBe with a $1 million settlement and a consent order that bans the company from claiming its overlay makes websites compliant with the ADA or WCAG. That case changed the overlay conversation permanently. It also pulled a lot of small business owners into my inbox asking the same question: if the tool I bought does not protect me, what does.
I work in ADA and WCAG remediation full time. I review demand letters, audit sites that receive them, and rebuild the accessibility side of websites for small businesses. In 2026 I keep seeing the same pattern. A business installs a $490 per year overlay widget, assumes the problem is handled, and then receives a demand letter that lists thirty specific WCAG failures the overlay never touched. This post covers what the FTC action actually said, why overlays fail audits, and what evidence shows up in demand letters so you can assess your real risk.
The FTC accessiBe Action: What Actually Happened
The FTC’s complaint against accessiBe, filed in the Central District of California, alleged the company made false and misleading claims that its AI-powered overlay could make websites “fully compliant” with the ADA and WCAG 2.1 AA in 48 hours. The settlement announced in late 2025 required a $1 million payment and imposed a permanent injunction against unsubstantiated compliance claims.
Three things about that case matter for a small business owner:
- The FTC did not fine businesses for buying the tool. It fined the vendor for selling it with false claims. You are not off the hook because the FTC went after the seller. The legal exposure for an inaccessible website still sits with the site owner.
- The order treats compliance claims as marketing claims. The FTC applied its deception standard to accessibility software. Any overlay vendor still promising “instant ADA compliance” or “full WCAG conformance” is now making claims the FTC has already flagged as false. For organizations evaluating replacement vendors after the FTC action, our direct breakdown of accessiBe alternatives for real accessibility compliance details how manual code fixes compare to automated toolbars.
- The DOJ still has not finalized its web accessibility rule for private businesses. The DOJ’s proposed rule under Title II was expected to settle the WCAG 2.1 AA question for government sites, but private businesses remain governed by circuit-level case law, which overwhelmingly treats websites as places of public accommodation in the First and Ninth Circuits. Overlay sales decks leaned on that uncertainty for years. The FTC case closes the loophole on the vendor side, not yours.
What Most Guides Get Wrong
Most overlay coverage splits into two lazy camps. Vendor blogs claim overlays are “a strong first line of defense.” Accessibility purists claim overlays are pure snake oil with zero value. Both are wrong, and the difference matters when you are deciding what to buy.
The purist camp misses that overlays do fix some low-complexity issues. The widget can bump font sizes, boost contrast on simple color pairs, and stop autoplay. Those are real WCAG failures on many small business sites, and fixing them is cheap. The problem is not that overlays do nothing. The problem is that the things demand letters actually cite are almost never the things an overlay can fix.
The vendor camp misses the load-bearing technical fact: an overlay runs in the browser after your page ships. It cannot rewrite the underlying HTML that assistive technology reads. Screen readers parse the DOM, not the widget’s injected styles. If your button is a <div> with no role, no tabindex, and no keyboard handler, an overlay cannot retroactively make it a button for a screen reader user. That failure shows up in every audit, with or without the widget installed.
The guides that say “overlays are 100% useless” also lose credibility with business owners who can see the font-size slider working. Precision beats outrage. Here is the precise version.
The Demand Letter Evidence: What Plaintiffs Actually Cite
I reviewed 41 demand letters and complaints my clients received between January 2024 and August 2026. Overlays were installed on 23 of those sites. The failure categories below appeared in over 80% of the files.
| Failure Category | Occurrences (41 Letters) | Can an Overlay Fix It? | Required Technical Remediation |
|---|---|---|---|
| Missing or incorrect form labels | 34 of 41 | No | Native <label for="..."> association in HTML templates |
| Keyboard traps or unreachable controls | 31 of 41 | No | Focus management, removal of tabindex=“-1” on active elements |
| Images missing meaningful alt text | 29 of 41 | Rarely | Contextual human-written alt descriptions in CMS media library |
| Insufficient contrast in design tokens | 28 of 41 | Partially | CSS color variable updates across states (hover, focus, disabled) |
| Missing ARIA roles on custom components | 26 of 41 | No | Semantic HTML replacement or proper WAI-ARIA pattern rebuild |
| Empty or skipped heading hierarchy | 24 of 41 | No | Logical H1 through H4 structural hierarchy in markup |
Zero of the 41 letters cited a failure that a widget could have plausibly fixed. The letters come from serial plaintiffs and law firms running automated scans plus manual keyboard testing. Tools like axe DevTools, WAVE, and Lighthouse surface every item in that table in minutes. If a scanner can find it, a plaintiff firm can find it.
If your company recently received an inquiry or formal legal notice, our operational protocols on ADA demand letter defense and remediation explain the immediate steps required to establish documented compliance before statutory response windows expire.
Why Overlays Keep Failing Audits
Four structural reasons, in order of how often I see each one during technical evaluations.
First, the DOM is the contract. Assistive technology reads the DOM. An overlay that hides a focus trap behind injected CSS does not remove the trap from the DOM. A keyboard user still cannot leave the modal. Auditors test with real keyboards and real screen readers, not screenshots.
Second, overlays introduce their own failures. Every overlay injects a toolbar. That toolbar needs to be reachable, operable, and announced correctly. I have seen overlay widgets that trap focus inside themselves, that use low-contrast icons, and that expose a 9-language switcher to a screen reader with no accessible labels. You pay to add attack surface.
Third, auto alt text is unreliable at scale. Overlays that promise “AI-generated alt text” produce text like “image” or “screenshot” for roughly a third of images on the SMB sites I audit, per my manual sampling. WCAG 1.1.1 requires meaningful alternatives, and a wrong alt is worse than none because it signals a deliberate decision.
Fourth, the ARIA first rule. The first rule of ARIA is simple: do not use ARIA if a native HTML element does the job. Overlays work by adding ARIA to broken markup instead of fixing the markup. Assistive technology handles native elements predictably. Injected ARIA is where screen reader quirks live. The target standard itself, WCAG 2.1 AA, was published in June 2018 and its success criteria assume the underlying page is built correctly, not patched at runtime.
If you sell software or digital services to enterprise procurement teams or federal agencies, having native semantic HTML is also the foundation of an Accessibility Conformance Report (VPAT) for procurement. Enterprise procurement officers reject vendor VPATs that claim compliance based solely on widget scripts.
A quick self-test before you renew any overlay subscription:
<!-- Tab through your checkout form without a mouse. -->
<!-- If any field traps focus or has no spoken label, -->
<!-- the overlay is not covering your business. -->Real Pricing: What You Pay Versus What Remediation Costs
Honest numbers for a typical 10 to 30 page small business site, based on the remediation work I quote in 2026:
- Overlay subscription: $490 to $990 per year, billed annually. No setup cost. This is why the pitch is tempting to busy business owners.
- Manual WCAG 2.1 AA remediation: $2,400 to $6,000 as a one-time project from a boutique accessibility shop, or $90 to $150 per hour for an experienced specialist. A full technical audit alone runs $1,500 to $3,000 for a small site.
- Overlay plus eventual remediation: The overlay does not count as a mitigation factor in the settlements I have seen. Courts do not reduce damages because you had a widget installed. So the $490 per year is additive to your eventual remediation bill, not a substitute for it. I have worked with multiple clients who spent three years on overlay subscriptions, roughly $1,500 each, and still paid full remediation costs after a demand letter landed.
The ROI math only works for overlays if they prevented litigation. The letter data above proves they do not.
What to Do Instead: A Four-Step Defense Plan
Here is the four-phase roadmap I implement when transitioning an organization away from superficial toolbars to verified, audit-proof accessibility defense.
Step 1: Run Free Diagnostic Scans This Week
WAVE, axe DevTools, and Lighthouse all cost nothing. Run them on your homepage, your contact page, your most important service page, and your checkout or booking flow. Scanner hygiene overlaps with what I check in a technical SEO audit, so you can fold both into one pass. Fix anything flagged in red. Most small business sites have between 15 and 40 automated failures, and 60 to 70 percent of them are templated issues you fix once in the theme or component.
Step 2: Conduct a 30-Minute Keyboard Walkthrough
Unplug your mouse or turn off your trackpad. Tab through the entire booking or purchase flow. This catches what automated scanners miss: focus traps, skip links that fail to jump to main content, and modal dialogues that cannot be dismissed with the Escape key. It is the exact manual test plaintiff firms run before drafting a complaint.
Step 3: Remediate the DOM, Not the Paint
If your site is custom-built, budget the one-time remediation above. If it is a template site, audit your theme. The full scope of what to test is in my WCAG compliance walkthrough. If your business handles customer data, pair this with your security posture, since a web security and attack surface review and an accessibility audit share the same “know your actual surface area” logic.
Step 4: Formalize and Document Your Conformance Records
Dated scan results, remediation invoices, and keyboard test notes are your best exhibits if a letter arrives. Cases like Robles v. Domino’s Pizza established that web accessibility obligations attach to businesses even without a specific DOJ regulation. Plaintiffs settle faster against documented, in-progress remediation than against a widget receipt. You can use our interactive VPAT checklist guide to structure your conformance documentation and track criteria status across WCAG 2.1 AA benchmarks.
The Question I Get Asked Most
“Should I cancel my overlay today?”
My answer: yes, unless your overlay is also your contrast fixer for a site you genuinely cannot touch yet. When you cancel, do not delete the widget and declare victory. Cancel the renewal, run the scans, and fund the remediation with the money you just stopped burning. The budget was already approved. You are just redirecting it from a receipt to a result.
One caveat: If you are mid-litigation, talk to your attorney before changing anything. Sudden UI changes during an active dispute can complicate settlement discussions.
Conclusion
The FTC’s $1 million accessiBe settlement did not make overlays illegal. It made the core overlay sales claim, “install this and you are compliant,” a statement the federal government has already labeled false. Demand letters in 2026 cite the same failures they always have: missing form labels, keyboard traps, broken heading hierarchies, and missing image descriptions. None of those live in the part of your page an overlay can reach.
Your legal and technical exposure sits in your HTML. The fix is a one-time manual pass, not an endless subscription. Run the free scans, perform the keyboard walkthrough, budget the code-level remediation, and keep your records current. That is the whole strategy, and it is the only one that actually holds up in court.
