Why Accessibility Overlay Widgets Won't Make Your Government Website Compliant (And What Actually Works)

If you're a city clerk or IT manager scrambling to meet the ADA Title II deadline, you've probably seen ads for accessibility "overlay" widgets promising instant compliance. Install one line of code, and your website is accessible. Sounds perfect, right?

Don't do it. The FTC has already fined the largest overlay company $1 million for making exactly those claims. And overlay users are getting sued at increasing rates — in May 2025 alone, 119 defendants were sued while using a third-party accessibility widget.

This article explains what overlays are, why they don't work, what the government and disability community say about them, and what you should do instead.

What is an accessibility overlay?

An overlay is a JavaScript widget that gets added to a website. When activated, it applies cosmetic changes to the page — adjusting colors, font sizes, spacing, or cursor appearance. Some overlays also attempt to add missing alt text using AI or modify the page structure for screen readers.

Common overlay products include AccessiBe (accessWidget), UserWay, AudioEye, and EqualWeb. They typically cost $50–$500/month and promise rapid WCAG compliance.

The pitch sounds compelling: instead of auditing your website, fixing the code, and retraining your staff, just add one script tag and you're done. For a municipality with a tight budget and an approaching deadline, this is an attractive promise.

It's also false.

The FTC took action: AccessiBe fined $1 million

On January 3, 2025, the Federal Trade Commission announced that AccessiBe would pay a $1 million penalty for deceptive advertising. The FTC found that AccessiBe had falsely claimed its AI-powered widget could make any website WCAG-compliant within 48 hours.

The FTC's findings were specific and damning. According to the complaint, AccessiBe's widget failed to make basic website components accessible — including navigation menus, form fields, tables, and image descriptions. In some cases, the widget actually generated incorrect alt text: one example cited a photo of a filet mignon that the AI described as "brown bread on white ceramic plate."

The FTC's order bars AccessiBe from claiming its automated products can make any website WCAG-compliant without evidence to support such claims.

This wasn't an isolated action. The disability and accessibility community had been raising alarms about overlays for years before the FTC stepped in. The Overlay Fact Sheet, signed by hundreds of accessibility professionals, documents the technical and practical failures of overlay products.

Why overlays don't actually work

They don't fix the source code

This is the fundamental problem. An overlay adds a JavaScript layer on top of your website. The underlying HTML — with its missing alt text, broken heading structure, unlabeled forms, and inaccessible PDFs — remains exactly the same.

When a screen reader encounters your website, it reads the actual DOM (Document Object Model). An overlay might attempt to modify the DOM in real-time, but this creates fragile, unreliable behavior that breaks in countless edge cases. The actual source code of your website is what needs to be fixed.

AI-generated alt text is unreliable

Overlays that use AI to generate image descriptions frequently produce inaccurate or meaningless text. A photo of your city council might be described as "group of people sitting in room." A map of your utility service area might get described as "colorful image." These descriptions fail to convey the actual meaning of the content — which is the whole point of alt text.

For a government website where accuracy matters (think: emergency information, legal documents, public notices), unreliable AI descriptions aren't just unhelpful — they can be harmful.

They can create new accessibility barriers

Ironically, several studies and user reports have shown that overlay widgets can make websites less accessible. Common problems include:

• The overlay's own interface isn't keyboard-accessible
• The widget conflicts with users' existing assistive technology settings
• Screen reader users get bombarded with extra announcements from the overlay
• The widget's modifications break page functionality

Disabled users have created browser extensions specifically to block overlay widgets because they interfere with their existing accessibility tools.

They don't cover all content types

Overlays work (to the limited extent they do) on HTML content in a web browser. They cannot fix:

• PDF documents — Government websites are full of PDFs (meeting agendas, budgets, permits, forms). Overlays don't touch these.
• Mobile apps — The ADA Title II rule covers mobile applications too. Overlays don't apply.
• Third-party embedded content — Payment portals, form builders, maps, and other embedded tools aren't affected by an overlay on your main site.
• Videos without captions — An overlay can't generate accurate captions for your city council meeting recordings.

For a government website, these exclusions alone mean an overlay can never achieve full compliance.

Overlays and lawsuits: the numbers

Using an overlay doesn't protect you from lawsuits — it may actually increase your risk.

According to UsableNet's data, 119 defendants were sued in a single month (May 2025) while actively using an accessibility widget. The presence of an overlay has never been accepted as a legal defense in an ADA lawsuit.

Why? Because plaintiffs' attorneys know that overlays don't fix the underlying code. They can easily demonstrate that the website remains inaccessible by testing with actual assistive technology. The overlay becomes evidence that you took a shortcut rather than making genuine accessibility improvements.

For a government entity subject to ADA Title II, the risk calculation is clear: an overlay gives you a false sense of security while the actual accessibility barriers remain — and those barriers are what trigger complaints and lawsuits.

What the accessibility community says

The opposition to overlays is remarkably unified across the accessibility community:

The Overlay Fact Sheet (overlayfactsheet.com), signed by over 700 accessibility professionals, developers, and organizations, states that overlays do not achieve compliance and should not be used as a substitute for genuine remediation.

The National Federation of the Blind has called on websites to remove overlay products and invest in actual accessibility improvements.

The DOJ, through its enforcement actions and settlement agreements, has consistently required actual code remediation — never an overlay installation — as the solution for inaccessible websites.

Disability rights attorneys regularly cite the presence of overlays as evidence that an organization chose a cheap shortcut over genuine accessibility.

What actually works

Real accessibility compliance requires fixing the actual code of your website. Here's the good news: for most government websites, this is more manageable than you think.

Step 1: Scan your website

Use an automated scanning tool to identify your current accessibility issues. Automated tools use the same engine (axe-core) that Deque and other professional auditing firms use. They catch about 30–40% of WCAG issues — but they catch the most common and impactful ones.

Step 2: Fix issues in the source code

For each issue found, make the actual change in your website's code or content:

• Missing alt text? Add it to the <img> tag in your CMS.
• Low color contrast? Update the CSS values.
• Unlabeled form field? Add a <label> element.
• Broken heading hierarchy? Restructure the HTML.

These are real fixes that permanently solve the problem. No JavaScript widget needed. For a complete step-by-step walkthrough, see our ADA Title II compliance guide for local governments.

Step 3: Monitor for regressions

Every time someone adds content to your website — a new page, a blog post, a PDF upload — new accessibility issues can be introduced. Set up monthly scanning to catch regressions early. GovAccess does this automatically and alerts you when new issues appear.

Step 4: Document your compliance efforts

Generate a proof-of-effort report showing your scan results, the issues you've fixed, and your ongoing monitoring. This documentation demonstrates good faith effort — which courts and enforcement agencies value far more than an overlay installation.

Cost comparison: Overlay vs. real compliance

The price is comparable. The outcomes are not.

FAQ

Q: My CMS vendor recommends an overlay. Should I listen?

Be cautious. Some CMS vendors resell overlay products as an add-on because it's easy revenue. Ask your vendor instead about their platform's native WCAG conformance and what support they offer for actual code-level remediation.

Q: We already installed an overlay. Should we remove it?

Yes. Remove the overlay and invest that monthly cost into actual remediation. Keep records showing that you transitioned from an overlay to genuine code fixes — this demonstrates that you're taking compliance seriously.

Q: Aren't overlays at least "better than nothing"?

This is the most common argument, and it's wrong. An overlay gives decision-makers a false sense of compliance while the real barriers remain. It delays genuine remediation. And it can actively make the experience worse for disabled users. Doing nothing but starting a real compliance plan is actually a stronger legal position than installing an overlay, because it shows intent to address the root cause.

Q: What about "hybrid" approaches that combine overlays with manual fixes?

If you're doing manual fixes, you don't need the overlay. The overlay adds no value on top of actual code remediation. Spend that money on developer time or scanning tools instead.

Bottom line

Accessibility overlays are not a compliance solution. The FTC has confirmed it. The disability community has confirmed it. The courts have confirmed it. And the data shows that overlay users are still getting sued.

For local governments facing the ADA Title II deadline, the path to compliance runs through your actual source code — not through a JavaScript widget.

The good news: most government websites have fixable issues that existing staff can address with the right guidance. You don't need a $50,000 enterprise platform. You need a clear list of what's broken and plain-English instructions on how to fix it.

For a complete accessibility audit of your full website with prioritized fix instructions and a proof-of-effort PDF report, start a free 14-day trial of GovAccess — built specifically for local governments at a price that fits your budget.

Disclaimer: This article is for informational purposes only and does not constitute legal advice. Consult with your municipality's legal counsel for guidance specific to your situation.