Why Accessibility Overlay Widgets Will Cost You the Contract

The Sales Pitch

You have probably seen the ads. Install one line of JavaScript. An AI-powered widget scans your site, fixes accessibility issues automatically, and keeps you WCAG compliant around the clock. Some vendors even promise lawsuit protection. For a few hundred dollars a month, the entire problem goes away.

If you are a municipal contractor under pressure to demonstrate ADA compliance before the April 2026 deadline, that pitch sounds compelling. It should not be. The data from 2025 makes the case clearly: overlay widgets do not protect you from lawsuits, they do not achieve WCAG compliance, and they are increasingly likely to disqualify you from the very bids you are trying to win.

The FTC Settled the Debate

On January 3, 2025, the Federal Trade Commission announced a $1 million settlement with accessiBe, one of the largest accessibility overlay vendors in the market. The FTC's complaint alleged that accessiBe had falsely marketed its widget as capable of making any website WCAG compliant within 48 hours and ensuring ongoing compliance through automated rescanning.

The FTC found that the widget failed to make basic and essential website components accessible — including navigation menus, form fields, headings, tables, and image descriptions. These are not edge cases. These are the fundamental elements that screen reader users depend on to navigate a website at all.

The settlement bars accessiBe from claiming its automated products can make any website WCAG compliant unless it has evidence to support such claims. The FTC also found that the company had disguised paid endorsements as independent third-party reviews, adding a layer of deceptive marketing on top of a product that did not deliver what it promised.

The FTC's own blog post about the case put it plainly: before you claim your product can perform a certain task, you need evidence it will work as promised.

The Lawsuit Numbers Are Damning

The FTC action did not happen in a vacuum. The litigation data from 2025 tells a story that overlay vendors cannot explain away.

According to EcomBack's Mid-Year ADA Website Accessibility Lawsuit Report, 456 lawsuits in the first half of 2025 alone targeted websites that had accessibility widgets installed. That represents 22.6% of all ADA digital accessibility filings during that period. These were not sites that lacked any accessibility effort — they had paid for a product specifically marketed to prevent this exact outcome.

The numbers got worse month over month. Lawsuits against widget-equipped sites in May and June 2025 nearly doubled compared to the same months in 2024. The trend line does not suggest a problem that is resolving itself.

UsableNet's midyear report confirmed the pattern, documenting that accessibility widgets have not slowed the rise in lawsuits and noting that many overlay tools create new barriers for screen reader users by adding control panels and interface modifications that interrupt assistive technology navigation.

Why Overlays Fail Technically

Understanding why overlays cannot deliver on their promises requires understanding what they actually do — and what WCAG compliance actually requires.

An overlay is a third-party JavaScript layer that sits on top of your existing website code. It does not change the source code. It attempts to modify the user experience in the browser at runtime. This creates several fundamental problems.

They cannot detect most issues. Automated scanning tools — even good ones — can only identify approximately 30 to 40 percent of WCAG violations. The remaining 60 to 70 percent require human judgment: whether alt text is actually meaningful, whether a reading order makes logical sense, whether a form provides adequate error messages, whether interactive elements behave predictably for keyboard users. An overlay that scans and "fixes" is working from an incomplete picture of the problem.

They cannot fix structural issues. If your HTML is semantically incorrect — missing heading hierarchy, unlabeled form fields, missing landmark regions, improperly associated table headers — an overlay cannot restructure the underlying document. It can only attempt cosmetic patches that may or may not be interpreted correctly by assistive technology.

They can make things worse. The Overlay Fact Sheet, a community-driven statement endorsed by over 600 accessibility professionals including contributors to the WCAG specification itself, documents how overlay widgets frequently interfere with the assistive technologies that users with disabilities already rely on. Screen reader users have reported that overlays break navigation patterns, introduce unexpected focus changes, and generate confusing duplicate content.

They are temporary by design. Overlays apply modifications in the browser session. They do not persist. They do not fix the underlying code. If the overlay script fails to load, the user is back to the original inaccessible experience. This is not a compliance strategy — it is a fragile band-aid that can fail silently.

The Procurement Problem

Here is where the overlay question becomes directly relevant to your ability to win municipal contracts.

Municipalities are updating their procurement language in response to the DOJ's Title II rule. The DOJ's own guidance recommends that public entities require vendors to provide detailed accessibility information before signing contracts and include warranties that deliverables comply with WCAG 2.1 AA. Procurement officers are increasingly asking for Voluntary Product Accessibility Templates (VPATs) and Accessibility Conformance Reports (ACRs) that document specific criterion-by-criterion compliance.

An overlay widget does not produce a VPAT. It does not generate an ACR. It does not provide the kind of structured, verifiable compliance documentation that procurement evaluators need to assess your bid.

Worse, including an overlay in a bid response signals something that experienced procurement officers recognize immediately: you are aware of the accessibility requirement but have chosen a surface-level solution rather than addressing the underlying issues. After the FTC settlement, that signal carries regulatory baggage. A procurement officer who approves a vendor relying on an FTC-sanctioned compliance approach is not making a defensible decision.

Some municipalities are now explicitly excluding overlay-based solutions from acceptable compliance strategies in their RFP language. This is not a theoretical risk. It is happening in procurement offices across the country as the April 2026 deadline approaches and municipalities tighten their vendor requirements.

The Litigation Backfire

Beyond procurement, there is a litigation dimension that makes overlays actively dangerous for contractors.

Plaintiff attorneys have learned to view the presence of an accessibility widget as an indicator of a productive target. The reasoning is straightforward: if you installed an overlay, you were aware of your accessibility obligations. If your site still has WCAG violations despite the overlay — and it almost certainly does, given the 60 to 70 percent detection gap — plaintiffs can argue that you knew about the problem and chose an insufficient fix over genuine remediation.

This transforms what might have been a simple failure-to-comply case into a case with evidence of knowledge and inadequate response. It undermines the "good faith effort" defense that is one of the strongest positions a contractor can hold.

For municipal contractors specifically, this risk compounds. If a municipality faces an ADA complaint because of a digital asset you delivered with an overlay instead of source-level remediation, you are not just exposed to the current dispute — you are establishing a pattern that will follow your firm into future bids and contract renewals.

What to Do Instead

The alternative to an overlay is not complicated, but it does require actual work. Source-level remediation means identifying WCAG violations through a combination of automated scanning and manual testing, then fixing the issues in the actual code — the HTML, CSS, and JavaScript that produce the user experience.

This is what compliance actually looks like:

Scan your deliverables with a real WCAG testing tool. Tools like axe-core, WAVE, or Lighthouse can identify the 30 to 40 percent of issues that automated testing catches. This is your starting point, not your finish line.

Conduct manual testing for the issues automation misses. Keyboard navigation testing, screen reader testing, logical reading order verification, and meaningful alt-text review all require human judgment. These are the issues overlays cannot address and the issues plaintiffs specifically test for.

Fix the source code. When you find a missing form label, add it to the HTML. When you find insufficient color contrast, update the CSS. When you find a missing heading hierarchy, restructure the document. These fixes are permanent. They do not depend on a third-party script loading correctly.

Document every step. An audit defense log that timestamps your scans, records the issues found, tracks remediation actions, and verifies fixes is dramatically more valuable than an overlay subscription — both for winning bids and for defending your work.

The contractors who will thrive in the post-April 2026 procurement environment are not the ones who found the cheapest shortcut. They are the ones who can demonstrate, with documentation, that they understand what WCAG compliance requires and have done the work to achieve it at the source level.

Overlay widgets are not a compliance strategy. After the FTC settlement, the lawsuit data, and the procurement shifts happening right now, they are a liability.

---

This post is for informational purposes only and does not constitute legal advice. Consult with qualified legal counsel for guidance specific to your situation.