WordPress Accessibility Overlays: Why They Attract Lawsuits (2026)

In 2025, 456 of the 2,014 accessibility lawsuits filed in the United States targeted websites that already had an accessibility overlay installed. That is roughly one in four. These were not sites that had ignored accessibility; they were sites that had paid for a product marketed as the solution.

In some of those cases the overlay was used against the defendant, as evidence the company knew it had an accessibility problem and chose a shortcut rather than fixing it. Separately, accessiBe settled with the Federal Trade Commission for $1 million over claims that its AI could make websites WCAG compliant automatically, with the settlement explicitly noting that automated tools cannot deliver full compliance. This article explains what overlays do, why the evidence has turned against them, and what to do instead.

Verified August 2026. If you need the compliance requirements themselves, our European Accessibility Act guide covers the standard and the deadlines.

What an overlay actually does

An overlay is a JavaScript file you add to your site. When a page loads, it runs in the visitor’s browser and modifies the rendered output: adding ARIA attributes, guessing at alternative text, adjusting contrast, and presenting a toolbar where users can pick adjustments like larger text or a dyslexia-friendly font.

Two properties follow from that design and explain most of the criticism. The underlying page is unchanged, so the accessibility problems remain in your source and reappear the moment the script fails, is blocked, or is removed. And the fixes are guesses made by a machine with no knowledge of intent, which is why an overlay can label a photograph confidently and wrongly.

The deeper issue is that many screen reader users already have their own configuration, and a script that manipulates the accessibility tree at runtime can conflict with it. Overlays are frequently reported by disabled users as making sites harder to use rather than easier, which is a poor outcome for a product bought in their name.

What the evidence says

The FTC settlement. accessiBe paid $1 million to settle claims about representing its tool as delivering automatic WCAG compliance. The settlement recorded explicitly that automated tools cannot achieve full compliance, which removes the central marketing claim of the category.
The lawsuit data. 456 of 2,014 US accessibility lawsuits in 2025 targeted sites that already had overlays. Installing one demonstrably does not prevent litigation.
Courts are unpersuaded. Rulings in multiple ADA cases have held that overlay plugins do not provide sufficient accessibility and that sites using them remain liable. Courts have rejected automated overlays as proof of accessibility, treating testing and human judgement as necessary.
The technical ceiling. Accessibility auditors including UsableNet put automated detection at roughly 30% of WCAG issues. The rest requires judgement about image intent, content clarity, heading logic, and visual design, none of which a runtime script can supply.
Awareness cuts both ways. Some cases have used the presence of an overlay as evidence the operator knew of accessibility barriers, which turns a purchase intended as protection into an admission.

The 5 options compared

1. accessiBe

The most heavily marketed product in the category and the one with the clearest regulatory history. Its accessWidget prices by monthly website traffic, running roughly $49 to $199 per site per month, and each subdomain requires its own subscription, which multiplies the cost for organisations with several properties.

The $1 million FTC settlement is the material fact. It is not a claim by a competitor or a complaint from a critic; it is a regulator concluding the compliance claims were not supportable, and recording that automated tooling cannot deliver full conformance. Whatever the product does technically, buying it as your compliance answer means relying on a representation the FTC has already addressed. If you want a runtime toolbar because some of your users find it helpful, that is a real and separate reason.

Pricing: Roughly $49 to $199 per site per month, by traffic; per subdomain
Compliance value: Does not deliver conformance
Legitimate use: A user-facing preferences toolbar
Watch out for: $1 million FTC settlement over compliance claims

2. UserWay

The other large overlay vendor, priced from around $49 a month, with a Pro plan at roughly $490 a year covering 100,000 monthly page views, rising toward $199 a month per site at higher traffic. It installs faster and costs less than the alternatives, which is genuinely its main advantage.

Everything in the evidence section applies equally here; nothing about the mechanism differs meaningfully between vendors. The relevant question is not which overlay is better but whether an overlay addresses your problem, and for legal exposure the answer is no. Where UserWay is worth considering is the narrower case of offering visitors a preferences panel, at a lower price than its competitors, with no illusion that it constitutes conformance.

Pricing: From around $49 a month; Pro around $490 a year for 100K page views
Compliance value: Does not deliver conformance
Legitimate use: Cheapest route to a preferences toolbar
Watch out for: Same litigation exposure as the category

3. AudioEye

Genuinely different from the two above, and it deserves to be assessed on its own terms. AudioEye pairs automated scanning with IAAP-certified human specialists who write custom fixes for issues automation cannot handle, which directly addresses the 70% gap rather than pretending it does not exist.

Pricing spans a wide range, from around $45 a month at the low end to $15,000 and above annually for managed engagements, with entry service tiers commonly cited near $199 a month. The human component is what you are buying, and it is the component that matters. The caveat is that it still delivers fixes through a runtime layer rather than repairing your source, so your underlying site remains unfixed and you remain dependent on the service continuing. Treat it as managed remediation-as-a-service rather than as an overlay, and price it against hiring an auditor.

Pricing: From around $45 a month to $15,000 plus annually
Compliance value: Human specialists address what automation cannot
Legitimate use: Managed remediation where you have no internal capacity
Watch out for: Fixes live in a runtime layer, not your source

4. Equalize Digital Accessibility Checker

The constructive alternative, and the reason this article is not simply a warning. Rather than modifying pages at runtime, it scans your content inside the WordPress editor, reports issues against WCAG criteria across more than 40 checks, and lets you fix them in the source where they belong.

There is a free version, and paid plans start at $190 a year with unlimited page scanning and no per-page or API fees. Set that against $588 to $2,388 a year for an overlay subscription and the comparison is uncomfortable: the cheaper product is the one that improves your site, and the expensive one is the one appearing in a quarter of lawsuits. Fixes made here persist whether or not you keep paying, because they are in your content rather than in a script.

Pricing: Free version; paid from $190 a year, unlimited pages
Compliance value: Finds real issues you then genuinely fix
Legitimate use: The core of an actual accessibility programme
Watch out for: Still bounded by the roughly 30% automation ceiling

5. Manual audit with free tooling

The approach courts actually credit, and the one every serious accessibility practitioner recommends. Free tools including axe DevTools, WAVE, Lighthouse, and Pa11y find the machine-detectable issues at no cost, and a human tests the journeys that matter with a keyboard and a screen reader.

A professional audit of your key journeys is not free, and it is the spend that produces defensible conformance. Compared honestly: a year of an overlay subscription at the middle of its range buys a meaningful chunk of a real audit, and the audit leaves you with a fixed site and documentation of what you did. Courts have consistently treated testing and human judgement as essential, which makes this the option that supports the legal position the overlay was purchased to secure.

Pricing: Free tools; audit cost varies by scope
Compliance value: The only route to defensible conformance
Legitimate use: Every site with real legal exposure
Watch out for: Requires committing to fix what the audit finds

Comparison table

Option	Annual cost	Fixes your source	Human judgement	Litigation record
accessiBe	$588 to $2,388 per site	No	No	$1M FTC settlement
UserWay	From around $490	No	No	Overlay sites still sued
AudioEye	~$540 to $15,000 plus	No	Yes, certified staff	Overlay delivery layer
Equalize Digital	Free, or $190	Yes	You supply it	Not an overlay
Manual audit plus free tools	Free tools; audit varies	Yes	Yes	What courts credit

What to do instead, in order

Run a free scanner on your five most important pages. WAVE or axe, ten minutes, no cost. You will find contrast failures, missing alt text, and form label problems immediately.
Fix those in the source. They are usually straightforward, and fixing them removes the majority of machine-detectable failures.
Test with a keyboard. Unplug the mouse and complete your most important journey. If you cannot, neither can a large group of your users, and no scanner told you that.
Install an in-editor checker. Stopping new issues appearing is cheaper than periodically clearing them out.
Commission a manual audit of key journeys. This is the spend that produces conformance and documentation, and it is what a court will look at.
Publish an honest accessibility statement. State your level, name known gaps and target dates, and give people a way to report problems. Honest beats perfect-sounding.

If you already have an overlay installed, removing it is not automatically the right move, because a site with genuine barriers and no remediation plan is exposed either way. The sequence that works is to start the remediation programme, then retire the overlay once the underlying issues are addressed.

Related guides

Frequently asked questions

Are overlays completely useless?

No. A preferences toolbar letting visitors adjust text size or contrast has real value for some users. What they do not do is deliver WCAG conformance or reduce legal exposure, which is what they are usually sold for and why the FTC became involved.

Should I remove the overlay I already have?

Not as a first step. Start remediating the underlying issues, then retire it. Removing it while the barriers remain changes nothing about your exposure and removes whatever benefit some users were getting.

Why do overlay vendors offer legal guarantees?

Some offer support or indemnity of various kinds. Read the terms carefully, since coverage is typically narrower than the marketing implies, and note that a quarter of 2025 US accessibility suits landed on sites that had already bought one.

Is AudioEye the same as the others?

Not quite. Its use of IAAP-certified humans addresses the gap automation cannot, which is a real difference. It still delivers through a runtime layer rather than fixing your source, so assess it as managed remediation and compare its cost against an audit.

How much does a real audit cost?

It varies with scope, but a focused audit of your main journeys is comparable to a year or two of overlay subscription at the middle of its range. The difference is that you finish with a fixed site and a record of the work.

What if I genuinely cannot afford remediation?

Free tools plus your own keyboard testing will remove a substantial share of barriers at no cost beyond time. Prioritise your highest-traffic pages and your checkout. Doing that honestly puts you in a better position than buying a widget you cannot afford either.

The verdict

Do not buy an overlay as your compliance answer. The FTC settlement addressed that claim directly, courts have rejected overlays as proof of accessibility, and a quarter of 2025 US accessibility lawsuits hit sites that already had one installed.

Spend the money on finding and fixing real issues instead: Equalize Digital at $190 a year for unlimited scanning, plus free browser tools. That is less than four months of a typical overlay subscription and it changes your site rather than decorating it.

If you have no internal capacity at all: AudioEye is the one option here that puts certified humans on the problem, which is a genuine service. Price it against hiring an auditor and choose deliberately.

And budget for a manual audit of your key journeys. Automated detection reaches roughly 30% of WCAG issues; the rest is judgement. That is the part courts credit, and it is the part no runtime script has ever provided.

ThemeAlley

Search

Recent Posts

Categories

Tag Cloud