BLOG · EAA

Accessibility Overlays & the EAA:
Why "One Line of Code" Is Not Compliance

Overlay widgets like accessiBe, UserWay, and AudioEye market instant accessibility for $49/month. Here is what the FTC found, what the lawsuit data shows, what the European Commission says, and what actually works for client sites.

Updated August 2026 · Reading time: 8 minutes

what-overlays-promise

An accessibility overlay is a third-party JavaScript widget you add to a website with a single script tag. It promises to make the site accessible automatically: enlarging text, adding alt text with AI, forcing keyboard focus, adjusting contrast. Vendors sell it as instant WCAG compliance — often with an "accessibility shield" badge to display in the footer.

The pitch lands well with small agencies and their clients: no developer time, no redesign, $49/month instead of a five-figure audit. The problem is not that overlays do nothing. It is that what they do does not match what they claim — and in 2026 both regulators and courts have said so.

🤖 AI-powered auto-fixes

Overlays claim to detect and fix accessibility issues at page load. Automated detection catches only a fraction of WCAG failures, and many "fixes" (auto-generated alt text, DOM rewrites) break screen reader behaviour.

🛡️ Compliance badges

Vendors let sites display a certification-style badge implying legal protection. No badge confers compliance — only conformance with EN 301 549 / WCAG 2.1 AA does.

💸 Recurring cost

A typical agency pays $49–$149 per month per site. Over three years that is more than a one-off professional remediation of most small business sites.

ftc-action

In January 2025, the US Federal Trade Commission charged accessiBe — the largest overlay vendor — with misrepresenting that its widget could make websites compliant with accessibility standards. In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million and barring it from claiming its automated products make any site WCAG-compliant unless it has evidence to support the claim.

Think about what this means: the company selling "guaranteed compliance" was itself sanctioned for deceptive advertising. If your pitch to clients includes an overlay's compliance claims, you are repeating marketing language a competition authority has already ruled misleading.

lawsuit-data

The United States is where overlay failure is best documented, because ADA website lawsuits are filed there by the thousand. In 2025, 3,948 ADA web accessibility lawsuits were filed — up nearly 24% over 2024. Roughly 20-25% of these targeted websites that had an accessibility overlay installed at the time.

Plaintiffs' firms actively screen for overlays: the widget signals that a company knew about accessibility and chose a shortcut. Installing an overlay does not reduce litigation exposure — industry reporting suggests it can mark a site as a better target.

More than 900 accessibility practitioners and disabled users have signed the Overlay Fact Sheet stating that overlays frequently make sites harder to use with assistive technology, not easier. The people who rely on screen readers are the ones who pay for broken auto-fixes.

eaa-position

For agencies working in the EU, the relevant law since 28 June 2025 is the European Accessibility Act. It requires e-commerce, banking, transport, and other covered services to conform with EN 301 549 — which incorporates WCAG 2.1 AA — and to publish an accessibility statement. Market surveillance authorities can require corrective action; member state penalty frameworks include fines up to €3 million in some countries.

The European Commission has stated that overlays alone do not achieve EAA compliance, and consumer organisations including the European Disability Forum have issued statements against marketing them as such. An overlay cannot fix the structural issues the EAA targets: missing keyboard support in checkout flows, inaccessible documents, unlabeled form fields in booking systems. Those require code changes.

The practical position for a small agency is simple: an overlay installed on top of a non-conformant site leaves the site non-conformant. The money is spent, the statement cannot honestly be published, and the underlying risk remains.

what-works

None of this means automated tools are useless. It means they belong in the right place: detection, not remediation. Run a scanner to find issues, then fix them in the code. That workflow costs nothing extra and produces a site that actually conforms.

A realistic plan for a small agency portfolio:

• Scan every client site for the common automated-detectable failures (missing alt text, unlabeled inputs, contrast, heading structure). • Fix those in templates and components once — every page on the theme benefits. • Test keyboard navigation and one screen reader pass on critical flows (checkout, contact, signup). • Publish an honest accessibility statement per site. • Re-scan after content updates or new plugins.

This takes hours per site, not months — and unlike a widget subscription, it ends. When you can show a clean scan and a documented process, you can also price it as a service line instead of paying for a badge.

🔍 Scan first

Our free scanner checks 15+ WCAG rules on any URL — WordPress, Shopify, Webflow, or hand-written HTML. No install, no account.

🧩 Fix at template level

Most errors repeat across pages because they live in the theme. One component fix removes hundreds of findings.

📝 Document honestly

An accessibility statement based on real scan results protects you far more than an overlay badge ever did.

Going Deeper

Real compliance comes from fixing your site, not from a widget. Our EAA checklist walks through 10 practical checks that take minutes each — start there.

Run the Free WCAG Scanner → →    Read the EAA Checklist → →

Frequently Asked Questions

Do accessibility overlays work at all?

They change some surface-level properties (text size, contrast, some focus behaviour) but cannot reliably fix the issues that matter most: semantic HTML, keyboard traps, screen reader compatibility, and accessible workflows. Automated tools detect far less than manual testing finds, and overlays sometimes break assistive technology further. The consensus of practitioners, disabled users, and now the FTC is that they do not deliver compliance.

Is installing an overlay illegal?

No. Buying and installing an overlay is legal. What is problematic is relying on it for compliance: under the EAA the site itself must conform to EN 301 549 regardless of what scripts run, and vendors may no longer legally claim their product guarantees WCAG compliance without evidence.

What happened with accessiBe and the FTC?

In January 2025 the FTC charged accessiBe with misrepresenting its product's capabilities, including through fake reviews. The April 2025 final order imposed a $1 million payment and prohibits claims that its products make websites WCAG-compliant without reliable evidence.

Should I remove an overlay a client already has installed?

Evaluate it like any dependency: scan the site with and without it enabled. If the overlay introduces errors or blocks real fixes, recommend removal and put the budget toward template-level remediation — which is usually cheaper over three years anyway. Never remove anything during active enforcement correspondence without documenting the decision.

Does the EAA ban overlays?

No, but the European Commission has made clear overlays alone do not satisfy EAA requirements, and consumer and disability organisations have formally opposed them being marketed as compliance solutions. Conformance is measured against EN 301 549 / WCAG 2.1 AA, not against whether a widget is present.

What is the cheapest path to real EAA compliance for a small site?

Automated scanning (free), template-level fixes for the errors it finds, a keyboard and screen-reader check of critical flows, and an honest accessibility statement. For most small business sites this is days of work, not months — and it produces something an overlay never can: a site that genuinely works with assistive technology.

Run the Free WCAG Scanner → →    Read the EAA Checklist → →