The Honest Truth About Accessibility Overlays

What Is an Accessibility Overlay?

An accessibility overlay (also called an accessibility widget, toolbar, or plug-in) is a third-party JavaScript snippet you add to your site that claims to improve accessibility automatically. Common overlay vendors include AccessiBe, UserWay, EqualWeb, and AudioEye. Once installed, the overlay adds a floating button — usually a blue person icon — that opens a menu of settings: larger font, higher contrast, reduced motion, keyboard navigation helpers, and similar options.

The pitch is compelling: install one script, flip your site from “not compliant” to “compliant.” The reality is more complicated, and the FTC in 2025 found parts of the pitch outright deceptive.

The Short Version: Overlays Don’t Deliver

Overlays can make a small set of cosmetic issues user-adjustable (font size, contrast themes). They cannot fix the underlying accessibility failures that make websites unusable for blind, deaf, motor-impaired, and cognitively disabled users — because those fixes require changes to the site’s actual HTML, JavaScript, and design decisions.

Real accessibility comes from building accessible markup, semantic HTML, meaningful alt text, proper focus management, keyboard operability, and thoughtful content — not from a script injected at runtime. An overlay sits on top of an inaccessible site; the inaccessible site underneath is still inaccessible to the assistive technologies that matter.

How Overlays Actually Work (and Why That’s the Problem)

Overlays use automated scanners to try to identify accessibility issues, then inject runtime fixes — rewriting ARIA attributes, adding generated alt text, remapping keyboard behavior. This has several fundamental limitations:

• Automated tools catch at most 30-50% of WCAG issues. The rest (meaningful alt text for complex images, logical tab order, accessible form validation, usable error messages) requires human judgment that overlays cannot provide.
• AI-generated alt text is often wrong. An overlay might label a product photo as “product” or a chart as “image” — technically alt text, functionally useless to a screen-reader user.
• Overlays break assistive technologies. Screen-reader users have reported that overlay scripts interfere with their own configured assistive tech, making the overlay-enhanced site harder to use than the original. In 2021 a consortium of blind and low-vision users signed the Overlay Fact Sheet, a community statement now co-signed by 700+ accessibility professionals opposing overlays as an accessibility solution.
• The user has to find and enable the widget before getting any benefit. Users who rely on assistive technology already have it configured system-wide; being asked to re-configure on every site defeats the purpose.
• Overlays do not fix the underlying code. If the overlay is ever removed — cancellation, vendor going out of business, script failure — the site reverts to its pre-overlay inaccessible state. Real accessibility lives in your HTML.

Top Reasons Not to Use Overlays

1. They don’t make you WCAG-compliant. Despite marketing claims, overlays do not achieve WCAG compliance. The FTC confirmed this in its 2025 AccessiBe order.
2. They can make accessibility worse. Screen-reader users frequently report that overlays interfere with their existing assistive tools, producing a worse experience than the un-enhanced site.
3. They don’t protect you from lawsuits. Overlay-using sites have been sued for ADA violations, and plaintiffs’ attorneys now specifically target sites that appear to rely on overlays as a quick fix.
4. They cost more than they look. Most overlay plans run $490–$4,900+ per year per domain. Over three years that is between $1,500 and $15,000, often more than remediating the site properly once.
5. They create a false sense of compliance. Business owners install an overlay, see the accessibility widget appear, and assume the job is done — shipping real accessibility problems to production untouched.

The Legal Picture in 2026

Three major regulatory developments since this article was first written have reshaped the overlay conversation:

FTC v. AccessiBe (January 2025)

The FTC ordered overlay vendor AccessiBe to pay $1 million to settle allegations that it falsely advertised its accessWidget product could make any website WCAG-compliant. The order (finalized April 2025) specifically bars AccessiBe from claiming its automated AI can ensure WCAG compliance unless it has evidence to prove that claim — which, according to the FTC complaint, it does not. The order also addressed deceptive use of fake “independent” reviews planted to promote the product.

This is the first federal enforcement action against an overlay vendor specifically for the compliance claims at the heart of the overlay business model. If you still see overlay marketing promising “WCAG compliance in 48 hours” or “fully ADA-compliant overnight,” that language is exactly what the FTC found deceptive.

DOJ ADA Title II Web Rule (April 2024)

The U.S. Department of Justice finalized a rule under ADA Title II requiring state and local governments to make their websites and mobile apps conform to WCAG 2.1 Level AA. Compliance deadlines are based on population size, with the earliest deadlines hitting April 2026 for jurisdictions with 50,000+ residents. Overlays do not satisfy this rule.

European Accessibility Act (June 2025)

The European Accessibility Act (EAA) came into force across the EU on June 28, 2025. It applies to any business with ≥10 employees and €2M+ turnover that sells covered products or services to EU consumers — including non-EU companies serving EU markets. For websites and mobile apps, the standard is WCAG 2.1 AA via the EN 301 549 technical spec (being updated to include WCAG 2.2). Overlays alone do not meet EN 301 549.

What the Accessibility Community Actually Recommends

If you have a site that needs to be accessible — and in 2026 that effectively means every public-facing site, depending on your market — the path forward does not include an overlay:

• Start with a real audit. Manual accessibility testing by qualified experts, combined with automated tools like axe DevTools, WAVE, Lighthouse, and Dyno Mapper’s accessibility testing. Expect a written report of issues ranked by severity.
• Fix the underlying code. Remediation work in your HTML, CSS, JavaScript, and content — with explicit attention to keyboard operability, focus order, semantic markup, color contrast, and accessible forms. This is where the money goes that would otherwise be spent on an overlay subscription.
• Involve disabled users in testing. No amount of automated testing substitutes for real users operating the site with screen readers, voice control, and switch access. User testing catches issues automated tools do not.
• Build accessibility into every new feature. Retrofitting is expensive; shipping accessible components from the start is barely more work than shipping inaccessible ones.
• Maintain it. Accessibility regresses as sites change. Automated tests in CI, periodic manual audits, and an internal accessibility champion are the difference between a site that stays accessible and one that drifts.

Frequently Asked Questions

Are all accessibility overlays bad?

They are all bad at the job they claim to do — making a site WCAG-compliant. Some overlay-style widgets offer useful user-preference features (adjustable font, contrast themes) that can complement a genuinely accessible site. The problem is never the widget itself; it is the marketing claim that an overlay substitutes for real accessibility work.

Can an overlay help me defend against an ADA lawsuit?

No. Courts have consistently held that having an overlay installed does not prove a site is accessible, and overlay-using sites continue to lose accessibility lawsuits. Plaintiffs’ attorneys now treat overlay presence as a signal that a site has not done real remediation.

What about overlay vendors that also offer audits and remediation services?

Some overlay vendors have pivoted to bundle human remediation services with their widget product. Judge the remediation services on their own merits — a qualified accessibility audit and remediation engagement can be valuable. The widget itself still does not make a site compliant.

Does the FTC AccessiBe ruling apply to other overlay companies?

The order legally binds AccessiBe. But the underlying finding — that claims of automated WCAG compliance are deceptive — applies to the entire product category. Other overlay vendors making the same claims are exposed to the same legal theory, and FTC follow-on actions are possible.

Bottom Line

Accessibility overlays sell a fantasy: compliance without effort. The FTC’s $1M AccessiBe order made official what the accessibility community has said for years — automated overlays cannot make a website WCAG-compliant, and marketing that claims otherwise is deceptive. Between the FTC action, the DOJ’s ADA Title II web rule, and the European Accessibility Act now in force, 2026 is a year where real accessibility work is cheaper than fake accessibility services, and the legal exposure for cutting corners is rising. Skip the overlay. Fix the site. See Dyno Mapper’s accessibility testing for where to start.