9 Accessibility Overlay Problems, Documented With Sources [2026]

Last updated: September 25, 2026

Nine problems with accessibility overlays are documented in court records, a federal enforcement action, practitioner statements, and disability-organization resolutions — not only in competitor opinion. This page inventories each: what it is, the evidence behind it, and who it affects. It is a reference rather than an argument; where a problem deserves fuller treatment, the deeper article is linked inline.

Key numbers: The Overlay Fact Sheet, an open letter recommending against overlays as a compliance strategy, carried more than 1,000 accessibility practitioner and organization signatures as of September 2026. Based on TestParty's analysis of Court Listener public records, 1,000+ businesses with overlay widgets installed were named in digital accessibility lawsuits in 2024. Federal website accessibility lawsuits rose 27% in 2025 to 3,117 filings, per Seyfarth Shaw's ADA Title III tracking. In April 2025 the FTC approved a final order requiring accessiBe — specifically — to pay $1 million under a 20-year consent order.

TestParty competes in this market. This article uses public information and cited sources; evaluate all options against your own requirements.

1. The source code stays exactly as it was

An overlay modifies a page in the visitor's browser after it loads. The HTML your server sends, the theme templates your team maintains, and the app code in between are unchanged — by design, not by defect.

This is the root the other eight grow out of. Conformance under WCAG 2.2 is evaluated against the page as delivered, and the Overlay Fact Sheet states plainly that "full compliance cannot be achieved with an overlay." A session the script fails to run in — blocked request, dead CDN, earlier JavaScript error — silently gets the original document. Our mechanism-level teardown of what overlays patch and cannot reach covers the architecture.

Who it affects: merchants whose accessibility evidence must survive an external audit, a procurement questionnaire, or an opposing expert.

2. Businesses with widgets installed keep getting sued

Installing an overlay has not removed businesses from the defendant pool. Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with overlay widgets installed were named in digital accessibility lawsuits in 2024 — roughly a quarter of that year's filings.

The volume has not eased either — 3,117 federal filings in 2025, up 27%, per Seyfarth Shaw. One caveat the data requires — these filings show widgets did not prevent suits, not that they caused them, since overlay sites tend to be sites that already had problems. Full counts and limits are in our court-record analysis of overlay lawsuit filings.

Who it affects: any business treating a widget subscription as its legal exposure strategy.

3. Accessibility practitioners have signed against it, by name

The Overlay Fact Sheet has drawn more than 1,000 signatures from accessibility practitioners and organizations as of September 2026 — people who publish their names alongside a recommendation against overlays as a compliance approach.

Its central claim is narrower than the shorthand usually reported: "these products' documented inability to repair all possible issues means that they cannot bring a website into compliance." That is a statement about scope, not a claim that overlays do nothing. The list is professional consensus, not a controlled study — but unusually broad consensus, and it has held for years.

Who it affects: teams whose auditor, consultant, or accessibility specialist will eventually be asked to put a signature on a conformance statement.

4. Disabled users reject overlays, and some actively block them

The National Federation of the Blind's 2021 resolutions demanded that "overlay providers stop making misleading, unproven, and unethical claims which falsely inflate the value and effectiveness of their technology."

Rejection has gone past position statements into tooling. The Overlay Fact Sheet documents that "overlays themselves may have accessibility problems significant enough for users to take steps to actively block overlays," and community-maintained blockers exist for that purpose — AccessiByeBye and a published Chrome overlay-blocking extension among them. These are volunteer projects, not surveys: evidence of a real constituency, not a measured share of users. Still, the intended beneficiaries built the countermeasure.

Who it affects: the assistive technology users the widget is sold as serving.

5. The marketing claims outran what the product delivered

In April 2025 the Federal Trade Commission approved a final order requiring accessiBe — that company specifically — to pay $1 million under a 20-year consent order, over its marketing claims for the accessWidget product.

Scope matters more than the headline here, and it is routinely overstated. The order addressed one vendor's advertising. It did not rule on other vendors' products, did not find overlay technology unlawful, and did not establish that installing a widget violates any law. It does establish that claims in this category have drawn federal advertising enforcement at least once — reason enough to re-read your own vendor's written claims. For how courts and regulators treat the category, see the legal status of accessibility overlays.

Who it affects: buyers who purchased on a promise of full compliance on a short timeline.

6. Overlays can override assistive technology the user already configured

The American Foundation for the Blind has written that accessibility overlays "often override the settings of users' existing assistive technology software, which makes things more difficult and complicated for the user," and calls it a serious barrier.

Public user reports describe the pattern concretely: focus that moves unpredictably with a widget enabled and settles when it is disabled, and users adding vendor script domains to host files to regain access to an account. These reports are specific to particular products, versions, and configurations — not a uniform property of every widget. But they run in one direction, and they come from daily screen reader users, not vendors.

Who it affects: screen reader, magnifier, and speech-input users who have already tuned their own stack.

7. Script weight and disability-data collection are real costs

An overlay adds a third-party JavaScript bundle every visitor downloads and executes on every page — and some products persist a visitor's selected accessibility profile across sites, turning an accommodation into a stored attribute.

The Overlay Fact Sheet frames the second half sharply: with cross-site profiles, "the user never opted in to be tracked," and "disability is sensitive personal information. It is not data that should be collected without the informed consent of the person it belongs to." Behavior varies by vendor and configuration — a question for your contract, not a blanket finding. Performance is the quieter cost: a vendor CDN fetched on every page view is a dependency your Core Web Vitals and uptime now inherit.

Who it affects: merchants with GDPR, CIPA, or consent-management obligations, and the users whose disability status is inferred.

8. The widget becomes the plan, and remediation stops

The most expensive problem here is not technical. In TestParty's onboarding audits of Shopify storefronts arriving with a widget installed, the pattern we see most often is a widget that replaced the remediation roadmap rather than bridging to it.

The baseline underneath is usually substantial: Shopify's theme store requirements cover roughly 16–22% of WCAG criteria, a stock Dawn install typically shows 30–100 violations out of the box and premium themes 100–350, and third-party apps are not reviewed for accessibility at all. None of that shrinks while a script runs on top of it. Outcomes show the contrast — when Dorai Home, a Shopify brand we work with, faced a $74,999 demand, it resolved at a $2,000 settlement because there were documented code-level fixes to point to. This is our observed onboarding pattern, not a study.

Who it affects: owners who believe the problem is handled and have stopped budgeting for it.

9. Dynamic, third-party, and checkout content stays out of reach

A cross-origin iframe cannot be read or modified by a script on the parent page — the browser's same-origin policy prevents it. That boundary covers hosted payment fields, embedded reviews, chat widgets, booking modules, and most video players.

On an ecommerce site that is not an edge case; it is the revenue path. WCAG conformance also applies to complete processes, so a checkout that fails partway through fails as a whole regardless of how the product page scores. Seyfarth Shaw puts ecommerce at 69–77% of digital accessibility suits — roughly where these gaps sit.

Who it affects: any store whose cart, checkout, or review content is served by a third party — most of them.

What problem-aware merchants do next

Three moves, in order. None require canceling anything this week.

Measure what the widget is actually covering. Scan one revenue template twice — once with the vendor's script domain blocked in DevTools, once with it active and every profile enabled. The delta is your widget's measured reach on your site. Then tab through a purchase with a screen reader, because a wrong-but-present label still passes an automated check.

Put the remaining work on a schedule. Baseline against WCAG 2.2 AA, prioritize revenue-carrying templates over raw violation counts, and fix in theme and app code through reviewable pull requests. That is TestParty's model: 14 days to initial remediation, daily scans plus monthly expert manual audits, date-stamped reports, and 15–30 minutes of customer PR review a month. As of August 2026 we have remediated 35 million-plus issues across 100+ brands, and in the history of the company, fewer than 1% of customers have been named in accessibility lawsuits while on the platform.

Be honest about the hybrid. Keeping a widget as an optional preference toolbar on top of a remediated site is defensible — text resizing, contrast themes, and reading masks are real features for the people who use them. The failure mode is the widget standing in for the plan. Our assessment of the overlay evidence for merchants and comparison of overlay alternatives cover the decision.

Frequently Asked Questions

Which of these problems apply to every overlay, regardless of vendor? Problems 1 and 9 are architectural: any tool running in the browser after page load leaves source code untouched and cannot reach cross-origin iframes. Problem 2 is category-wide in the filing data. The rest vary by vendor and configuration — problem 5 was scoped to one company's advertising.

Is there documented harm to users, or only professional disagreement? Both. The disagreement is in the Overlay Fact Sheet's 1,000-plus signatures. User-side evidence is narrower but concrete: the NFB's 2021 resolutions, the American Foundation for the Blind's statement on overridden assistive technology settings, and community-built blocking tools. None of it is a controlled study, and we would not present it as one.

How do I find out which of these nine affect my own site? Run the blocked-versus-active scan described above, then test a full checkout by keyboard and screen reader. That surfaces problems 1, 6, and 9 directly. Problem 8 is a calendar question, not a tooling one: is there a funded remediation date, or is the widget the whole program?

Do these problems land differently on Shopify? Somewhat. Theme store requirements cover roughly 16–22% of WCAG criteria, so the baseline is weaker than merchants assume, and third-party apps — reviews, subscriptions, upsells — often render in frames a parent-page script cannot touch. That makes problems 1 and 9 more pronounced.

If I can only address one problem this quarter, which matters most? Problem 8, in our assessment. The technical gaps are fixable on a schedule; the false sense of coverage is what prevents the schedule from existing. Confirming in writing what your widget does and does not cover turns the other eight into a scoped backlog.

TestParty practices a cyborg approach to content: AI assists with research and drafting, our accessibility experts validate every claim. This article represents our editorial perspective based on public data as of the publication date. We compete in the digital accessibility space — which means we have informed opinions, but also a vested interest. All sources are cited so you can draw your own conclusions.