April 25, 2025 · reala11y team

After the FTC Order: Why Overlay Widgets Don't Fix Accessibility

The FTC fined accessiBe $1M for overstated overlay claims. Here's why overlays don't fix the HTML — and what genuine WordPress remediation looks like.

On April 21, 2025, the Federal Trade Commission entered a final order against accessiBe, requiring a $1,000,000 payment and barring the company from claiming its automated overlay makes websites WCAG compliant. If you run a WordPress site and bought an accessibility widget for peace of mind, that order is worth understanding — because it confirms what accessibility practitioners have argued for years.

What an overlay widget actually does

An overlay is a script you paste into your site. At page load it injects a layer of JavaScript that sits on top of your existing markup. It typically offers a floating toolbar and attempts runtime patches — guessing at alt text, relabeling buttons, adjusting contrast on the fly.

Here is the catch: the overlay never changes the HTML your server sends. Your underlying markup — the thing assistive technology, search crawlers, and audit tools actually read — is untouched. The overlay layers behavior on top at runtime; the source stays broken.

That distinction matters because:

• Assistive tech may never see the patch. Many screen reader users disable or never trigger third-party widgets. A <button> with no accessible name is still nameless to them.
• Runtime guesses are often wrong. Machine-generated alt text applied without human review can mislabel an image more confusingly than no text at all.
• The fix evaporates on the next load. Nothing is persisted. Re-run the patch every visit and hope it guesses the same way twice.
• One script can’t cover most of WCAG. Keyboard order, meaningful link text, logical heading structure, captions — these live in your content and templates, not in a toolbar.

This is roughly why the FTC acted, and why US courts have repeatedly declined to treat overlays as a remedy.

The regulatory ground has shifted

The legal context is no longer abstract:

• WCAG 2.2 became a W3C Recommendation on October 5, 2023, succeeding WCAG 2.1 (2018). It is the current technical baseline.
• The US DOJ issued an ADA Title II rule in April 2024 setting WCAG 2.1 AA as the standard for state and local government sites.
• The European Accessibility Act became enforceable on June 28, 2025, reaching many private-sector sites selling into the EU.
• The FTC’s accessiBe order (April 21, 2025) put a price on overstated automated-compliance claims.

A pasted-in script does not meaningfully address this. Real conformance work touches the code.

What genuine remediation looks like

Genuine remediation changes the markup at the source, so the corrected page is what everyone receives. For a WordPress site that means:

• Fixing the HTML, not masking it. A missing lang attribute, a target="_blank" link without rel="noopener", a duplicate id — corrected in the output, persistently.
• Scanning honestly. A scanner flags the issues it can detect — missing alt text, low contrast, broken heading hierarchy — and tells you plainly what still needs a human.
• Keeping a human in the loop. AI can draft alt text; a person reviews and approves it before it ships. Every suggestion carries a “review for accuracy” note.
• Pairing automation with manual review. Automated tooling, including ours, typically detects 30–40% of WCAG failures by criteria. The rest — does this alt text convey the right meaning? is this link sensible out of context? — needs judgment.

reala11y is built on this model. It fixes code-level issues at the source and is explicitly not an overlay: no floating widget, no runtime mask. You can read how it works, and our WCAG 2.2 guides break down the criteria.

The honest takeaway

No plugin, ours included, makes a site “fully accessible” or removes legal risk — and anyone selling that is the reason the FTC order exists. What good tooling does is concrete: it fixes real code-level barriers, surfaces what it can detect, and is candid that automated checks catch only a portion of WCAG. reala11y helps your site move toward WCAG 2.2 AA conformance; it does not replace the manual review that genuine accessibility requires. That is a smaller promise than an overlay makes — and unlike the overlay’s, it is one honest tooling can keep.