Why Accessibility Overlays Aren't a Complete Fix: Lessons from the FTC Order

The accessibility overlay industry had a reckoning in 2025. Unsupported claims that overlay widgets can solve legal accessibility obligations are risky, and overlays do not replace source-level accessibility remediation.

Here's what happened and what businesses should do instead.

The FTC's accessiBe order

The FTC announced a settlement with accessiBe, one of the most prominent accessibility overlay companies. The complaint and order focused on unsupported compliance claims and undisclosed endorsement relationships.

• The FTC alleged accessiBe misrepresented that its widget could make websites WCAG-compliant
• The FTC alleged accessiBe lacked support for claims that its automated product could ensure continued WCAG compliance
• The FTC challenged the way some third-party articles and reviews were presented as independent
• The final order includes a monetary payment

It is a federal warning against overclaiming what automated accessibility products can do.

Overlays do not fix the underlying product

The practical risk is not that every overlay user faces the same legal exposure. The risk is that an overlay can create a false sense of security while many underlying barriers remain in place. A site with an overlay may still have:

1. Images without meaningful alternative text
2. Forms without correctly associated labels
3. Keyboard traps or inaccessible menus
4. PDFs and embedded third-party content that the overlay cannot repair

Why overlays don't work technically

The fundamental problem is architectural. An overlay is a JavaScript widget that runs in the browser after your page loads. It can modify some visual presentation, but it cannot:

• Fix missing alt text, if an image has no alt attribute in the HTML, the overlay can attempt to generate one using AI, but these auto-generated descriptions are frequently inaccurate or meaningless
• Fix form labels, screen readers rely on proper HTML associations between labels and inputs. An overlay can't reliably create these relationships after page load
• Fix heading structure, if your page jumps from h1 to h4, the overlay can't restructure your DOM
• Handle third-party content, embedded videos, iframes, social media widgets, and third-party forms are outside the overlay's reach
• Fix PDFs, documents linked from your site are generally outside the overlay's reach

The core problem is that assistive technologies already interpret the page's underlying HTML, semantics, focus order, and accessible names. A toolbar layered over that page cannot reliably repair many broken source-level relationships.

The regulatory context

Accessibility risk is not limited to one jurisdiction:

• The European Accessibility Act requirements started applying on 28 June 2025 for covered products and services in the EU.
• The FTC's accessiBe order shows that regulators can challenge unsupported automated-compliance claims.
• Accessibility litigation remains active in markets such as the US, especially for customer-facing digital services.

The consistent lesson is to avoid claims you cannot prove and to invest in evidence-based remediation.

What to do instead

The answer isn't a widget, it's remediating the problems in your code. Here's a practical approach:

1. Scan your site, use an automated tool like ClearSite that identifies likely code-level issues. Free scans do not require signup, and scan time depends on the page.
2. Understand the issues, ClearSite's AI explains each issue in plain English and gives you platform-specific fix instructions for WordPress, Shopify, Squarespace, and Wix.
3. Fix by priority, start with critical issues that can block users (missing form labels, keyboard traps). Then move to serious issues (colour contrast, missing alt text).
4. Monitor for regression, websites change constantly. New content, plugin updates, and theme changes can introduce new issues. Automated monitoring can surface common regressions before they affect more visitors.
5. Consider a manual audit, automated checks detect a meaningful but incomplete share of issues. For a broader assessment, pair automated monitoring with a professional accessibility audit for issues that require human judgment.

The bottom line

Overlay widgets can create a shortcut mindset. The FTC's accessiBe order shows why compliance claims need evidence. The more durable path is to identify and remediate barriers in your site.

If you're currently using an overlay, treat the FTC order as a reason to reassess unsupported compliance claims and prioritise source-level remediation.

Sources: FTC final accessiBe order and AccessibleEU EAA in-force note.