Why accessibility overlays don't protect you from the EAA

EAA Comply · Updated July 2026 · 6 min read

If you run an online shop in the EU, someone has probably offered you a one-line fix for the European Accessibility Act: paste a snippet, a widget appears, your site is "compliant". It costs €50–100 a month and it takes five minutes.

It also doesn't work. Not "works imperfectly" — it fails at the one job you're paying for: keeping you legally safe. Here's the evidence.

The track record: fined vendors and sued customers

• In January 2025 the US Federal Trade Commission ordered accessiBe — the largest overlay vendor — to pay $1 million for misrepresenting that its widget makes websites compliant with accessibility standards, and its consent order permanently bans the company from making unsubstantiated compliance and legal-protection claims.
• Year after year, hundreds of companies with an overlay installed get sued anyway — plaintiffs' firms actually screen for overlays, because the widget signals "this site knows it has a problem and took a shortcut". Litigation trackers following overlay-installed sites found roughly 20–25% of US web accessibility lawsuits in recent years targeted sites that already had one running, with one tracker counting 119 such defendants in a single month of 2025 alone.
• Over 900 accessibility practitioners and disabled users have signed the Overlay Fact Sheet, stating overlays make sites harder to use with screen readers, not easier.

Why a widget can't fix your code

The EAA (Directive (EU) 2019/882) points to the EN 301 549 standard, which points to WCAG. Those requirements live in your HTML: form fields need real labels, buttons need accessible names, checkout flows must work with a keyboard, images need meaningful alternatives, contrast must be built into the design.

An overlay is JavaScript injected on top of broken code. It can change font sizes and colours cosmetically, but it cannot reliably rewrite your DOM, relabel your forms, fix your focus order or repair your checkout. Screen reader users usually disable overlays because the widget fights the assistive technology they already use.

What the EAA actually requires

Since 28 June 2025, most businesses selling products or services to EU consumers (micro-enterprises excepted) must make their e-commerce accessible and publish an accessibility statement. Member state market surveillance authorities can require corrective action and impose penalties — Spain's framework allows fines up to six figures for serious cases, and enforcement activity is growing across the EU.

Compliance means three concrete things: your site actually conforms to WCAG 2.1 AA in its code, you publish an honest accessibility statement, and you keep both true as the site evolves.

What to do instead (and what it costs)

• Audit the real code — automated scanning plus manual keyboard and screen-reader testing of your key user journeys. See our fixed audit prices (from €390, no quotes). One-off.
• Fix by severity — a good audit gives your developer an ordered fix plan; most shops resolve the critical issues in days, not months.
• Publish your statement — the legally required document, written from real audit results (€290, done for you).
• Monitor monthly — accessibility breaks with every theme update. €49–99/month keeps you compliant, which is still less than most overlay subscriptions.

Real compliance is not more expensive than the fake kind — it's just front-loaded. And unlike a widget, it ends: once your code is fixed, you own the result.

Are you a web agency whose clients are asking about all this? We run a white-label accessibility audit programme for agencies — wholesale prices, your brand on the report.

• Sources:
• FTC, "Order Requires Online Marketer to Pay $1 Million for Deceptive Claims" (2025)
• Law Office of Lainey Feingold, coverage of the FTC/accessiBe settlement
• WCAGsafe, "ADA Lawsuit Statistics 2025–2026"
• TestParty, "Why 800+ Businesses with AccessiBe Were Still Sued"
• Deque, coverage of the French Carrefour court decision (June 2026)