That Accessibility Widget on Your Municipal Website Isn't Protecting You — It's a Liability
If you're a municipal administrator in New Jersey and someone sold you an accessibility overlay — one of those toolbar widgets that sits in the corner of your website promising to make it ADA compliant — we need to have an honest conversation. Because that widget isn't doing what you were told it does, it isn't going to protect you from a lawsuit, and there's a growing body of evidence that it may actually be making your website less accessible for the people it's supposed to help.
This isn't a niche opinion held by a handful of accessibility purists. The Department of Justice has weighed in. The National Federation of the Blind has taken a formal position. Hundreds of accessibility professionals have signed a public letter opposing overlays. And the companies selling these products have been on the receiving end of lawsuits, FTC complaints, and public backlash from the disability community for years.
If your municipality is relying on an overlay to meet the April 2027 WCAG 2.1 AA compliance deadline, you need to understand what you actually bought and what it can't do — before someone else points it out for you in a legal filing.
What Is an Accessibility Overlay?
An accessibility overlay is a piece of third-party JavaScript code that gets added to your website. When it loads, it typically places a small icon — often a wheelchair symbol or a person-shaped silhouette — in the corner of every page. Clicking that icon opens a toolbar that offers users a set of options: increase font size, change contrast, highlight links, stop animations, enable a screen reader mode, and other adjustments.
The most well-known overlay companies include accessiBe, UserWay, AudioEye, and EqualWeb, though there are dozens of others. Their marketing is remarkably consistent: install one line of code, become ADA compliant, avoid lawsuits, and protect your organization — all for a few hundred dollars a month or a modest annual subscription.
For a small municipality with a limited budget and no in-house accessibility expertise, that pitch is incredibly appealing. It sounds like a simple, affordable solution to a complicated, expensive problem. And that's exactly why so many municipalities have fallen for it.
What Overlays Claim to Do
The sales pitch varies by company, but the core promises generally include automated detection and repair of accessibility issues on your site, a user-facing toolbar that lets visitors customize their experience, compliance with WCAG 2.1 AA and ADA requirements, legal protection against accessibility-related lawsuits, and AI-powered remediation that improves over time without any manual work.
Some overlay companies go further, offering compliance certifications, accessibility statements you can post on your site, and indemnification clauses that promise to cover your legal costs if you're sued while using their product.
On the surface, it sounds comprehensive. Underneath, almost none of it holds up.
Why Overlays Don't Work
The fundamental problem with accessibility overlays is that they attempt to fix the presentation of your website without fixing the underlying structure. That distinction matters enormously, because the vast majority of accessibility barriers are structural — they exist in the HTML, the code, the architecture of how your site is built — and no amount of cosmetic adjustment on top of that broken foundation is going to make it work for someone who relies on assistive technology.
They Can't Fix What Actually Matters
Consider some of the most common accessibility failures on municipal websites. Images without meaningful alt text. Form fields without proper labels. Navigation menus that can't be operated with a keyboard. PDFs that are scanned images with no underlying text. Heading structures that skip levels or don't exist at all. Tables without proper header markup. Interactive elements that don't communicate their state to screen readers.
An overlay can't fix any of these things. It can try to guess what an image contains and generate alt text automatically, but the results are frequently wrong — and wrong alt text is arguably worse than no alt text, because it actively misleads a screen reader user about what's on the page. It can try to add labels to form fields, but if the underlying code doesn't associate those labels correctly, a screen reader still can't parse them. It can claim to enable keyboard navigation, but if the site's interactive elements weren't built to receive keyboard focus, the overlay's attempt to force it often creates bizarre behavior — focus jumping to unexpected places, elements activating out of order, users getting trapped in sections they can't escape.
The overlay sits on top of your website like a coat of paint on a building with structural damage. The building still isn't safe. It just looks different from the outside.
They Interfere With Real Assistive Technology
This is perhaps the most damaging criticism, and it comes directly from the people overlays are supposed to help.
People who are blind or have low vision don't need your overlay to read them your website. They already have screen readers — sophisticated, highly configurable software like JAWS, NVDA, and VoiceOver that they use for every website they visit, every document they read, every application they interact with. They've spent years learning how these tools work. They've customized the settings. They have workflows and shortcuts that let them navigate the web efficiently.
When an overlay activates its "screen reader mode" or "accessibility profile," it often changes the way the page is structured and presented in ways that conflict with what the user's actual assistive technology is trying to do. Elements get rearranged. ARIA attributes get injected incorrectly. Focus order changes unexpectedly. The result is that the user's carefully configured tools stop working the way they expect — not because of anything the user did, but because the overlay decided it knew better.
Multiple surveys and public statements from blind and low-vision users have described overlays as making websites harder to use, not easier. The National Federation of the Blind — the largest organization of blind people in the United States — has been vocal in its criticism of overlay products and the companies that sell them.
They Don't Cover Documents
Municipal websites are heavily dependent on documents — PDFs of meeting minutes, agendas, ordinances, budget reports, permit applications, public notices, newsletters. These documents are explicitly covered by the DOJ's Title II rule. They need to be accessible.
An overlay does nothing for your documents. It can't reach inside a PDF and add a tag structure. It can't make a scanned image of meeting minutes readable by a screen reader. It can't fix the reading order of a budget spreadsheet that was exported to PDF without any accessibility tagging. Your documents are completely outside the overlay's reach, and for many municipal sites, the documents are where the most critical accessibility failures live.
Their AI Isn't as Smart as They Say
Several overlay companies market their products as using artificial intelligence to automatically detect and fix accessibility issues. The implication is that the AI gets smarter over time, continuously improving the accessibility of your site without any human intervention.
In practice, the AI is doing relatively simple pattern matching — looking at page elements and making guesses about what they are and how they should be labeled. Those guesses are often wrong, especially on complex pages with dynamic content, custom layouts, or non-standard coding patterns. When the AI gets it wrong, it introduces new accessibility barriers that wouldn't have existed otherwise. And because the overlay runs automatically without human review, those errors can persist for weeks or months before anyone notices — if they're noticed at all.
Genuine accessibility remediation requires human judgment. It requires someone who understands the content of the page, the intent behind each element, and the way real users with real disabilities will interact with it. AI can assist with certain parts of that process, but it cannot replace it, and any product that claims otherwise is overselling its capabilities.
The Legal Reality
Let's set aside the technical arguments for a moment and talk about what municipalities actually care about most: legal exposure.
The overlay companies' most powerful sales pitch isn't about accessibility — it's about lawsuit protection. They tell you that installing their widget will make you ADA compliant, and that compliance means you can't be sued. Some offer indemnification clauses or warranty language that promises to cover your legal costs if a claim is filed.
Here's what they don't tell you.
The DOJ Does Not Recognize Overlays as a Compliance Solution
The Department of Justice has not endorsed any overlay product as a means of achieving WCAG 2.1 AA compliance. In fact, the DOJ has filed statements of interest in ADA cases explicitly noting that overlays do not bring websites into compliance with accessibility standards. When the federal agency responsible for enforcing the law tells you that your chosen solution doesn't satisfy the law, that's a problem no sales pitch can fix.
Overlay Users Get Sued More, Not Less
This is the statistic that should make every municipal administrator sit up straight. Research and legal tracking data have consistently shown that websites using accessibility overlays are sued at the same rate as — or higher than — websites without them. A widely cited analysis by accessibility consultant Adrian Roselli found that the presence of an overlay on a website had no meaningful protective effect against litigation and in some cases made the site a more attractive target, because the overlay's presence signaled that the site owner was aware of accessibility obligations but chose a superficial fix rather than genuine remediation.
Plaintiffs' attorneys who specialize in ADA website cases are very familiar with overlay products. The presence of an overlay on your site doesn't deter them. If anything, it tells them that the underlying site hasn't been properly remediated, because organizations that invest in real accessibility work don't need an overlay.
Indemnification Clauses Have Limits
Some overlay contracts include language that promises to defend or indemnify the customer if they're sued over accessibility while using the product. Read the fine print carefully. These clauses are typically narrow and conditional — they may not cover lawsuits brought under state law (only federal ADA claims), they may not cover complaints filed with the DOJ or the Office for Civil Rights, they may require you to have the overlay active and properly configured at the time of the complaint, and they may cap the company's liability at a fraction of your actual legal costs.
No overlay company is going to write you a blank check for legal defense. If a lawsuit costs your municipality $30,000 in legal fees and $50,000 in remediation under a consent decree, your overlay provider's indemnification may cover a small fraction of that — or none of it, depending on the circumstances.
Overlays Have Been Sued Themselves
In a particularly telling development, several overlay companies have themselves been the target of legal action. AccessiBe has faced a complaint from the FTC and multiple lawsuits alleging deceptive business practices. Users and advocacy organizations have filed complaints against overlay companies for misrepresenting the effectiveness of their products. When the companies selling the solution are getting sued over the solution, that should tell you everything you need to know about its reliability.
What the Disability Community Actually Says
If the legal and technical arguments aren't enough, consider what the people these tools are supposed to serve actually think about them.
The Overlay Fact Sheet — a website created and maintained by accessibility professionals — has collected hundreds of signatures from practitioners, developers, and people with disabilities opposing the use of overlays. Their position is blunt: overlays do not provide adequate accessibility, they create a false sense of compliance, and they harm the users they claim to help.
The National Federation of the Blind has passed resolutions opposing overlay products and has publicly called on organizations to invest in genuine accessibility remediation instead. Multiple other disability advocacy organizations have taken similar positions.
When blind users encounter an overlay on a website, many of them immediately disable it — because they've learned from experience that the overlay will make their screen reader work less reliably, not more. Some overlay companies have responded to this by making the widget difficult to dismiss, which creates yet another accessibility barrier: a user who can't easily close a tool they don't want is a user whose autonomy has been undermined by the very product that was supposed to serve them.
Why Municipalities Keep Buying Them Anyway
If overlays don't work, don't provide legal protection, and are actively opposed by the disability community, why are municipalities still buying them?
Because the sales pitch is perfectly designed for the people making the purchasing decision — municipal administrators and elected officials who aren't accessibility experts, don't have big technology budgets, and are being told there's a deadline approaching that they're not prepared for. An overlay vendor walks into that conversation and says "we can fix this for $2,000 a year, no technical work required, install in five minutes." Compared to the alternative — a $5,000 to $10,000 audit, months of remediation work, possible website redesign — the overlay sounds like a miracle.
It's not. It's a shortcut that skips the actual work, and it leaves your municipality exposed on every front — legally, ethically, and practically.
There's also a knowledge gap at the vendor level. Some municipal web designers and IT consultants recommend overlays to their government clients not out of bad faith but because they don't have deep accessibility expertise themselves. They see the overlay as an easy add-on that checks a perceived box, without understanding the technical and legal reality. If your web vendor recommended an overlay, it might be worth asking them what their own WCAG 2.1 AA testing process looks like — because a vendor who understands accessibility would never recommend one.
What to Do If Your Municipality Has an Overlay Right Now
If your municipal website currently has an overlay installed, here's what we'd recommend.
Don't panic, but don't be complacent either. The overlay isn't making things worse in a catastrophic way — but it's also not making them meaningfully better, and it's giving you a false sense of security that could delay the actual work you need to do.
Get a real audit. Have your site evaluated against WCAG 2.1 AA by someone who does manual testing with assistive technology. The audit will show you what the overlay is and isn't addressing, and it will give you a clear picture of the actual barriers on your site. The findings may be uncomfortable, but they're the foundation for a real remediation plan.
Talk to your overlay vendor about what their product actually covers. Ask them for a detailed VPAT or conformance report that maps their product's capabilities against each of the 50 WCAG 2.1 A and AA success criteria. Ask which criteria their product fully addresses, which it partially addresses, and which it doesn't address at all. If they can't or won't provide this, that tells you something important.
Build a remediation plan that addresses the underlying issues. Fix the code. Fix the content. Fix the documents. Train your staff on accessible content creation. This is the work that actually moves you toward compliance — and no product can substitute for it.
Consider removing the overlay. Once you've begun genuine remediation, the overlay becomes unnecessary at best and counterproductive at worst. A properly built, properly maintained accessible website doesn't need a toolbar widget — just as a properly constructed building doesn't need a handwritten sign explaining how to use the stairs.
The Bottom Line
Accessibility overlays exist because the market created a demand for easy, cheap, fast solutions to a problem that doesn't have one. The real work of making a website accessible is exactly that — work. It requires understanding the standards, auditing against them, remediating the failures, and maintaining compliance over time. There are no shortcuts that are worth taking.
For municipalities in New Jersey — and especially those in Gloucester County, where we've seen at least one site that appears to be using an overlay-based approach — the April 2027 deadline is real and approaching fast. Every month spent relying on an overlay instead of doing genuine remediation is a month wasted.
Your residents with disabilities deserve a website that actually works for them. Not a widget. Not a Band-Aid. A website that was built and maintained with their needs as a real priority — not an afterthought addressed by a toolbar.
Ritner Digital helps New Jersey municipalities move past overlays and toward genuine WCAG 2.1 AA compliance. If you need an honest assessment of where your site stands and a real plan to get it right, let's talk.
Frequently Asked Questions
What's the Difference Between an Overlay and a Genuine Accessibility Fix?
An overlay is a layer of code that sits on top of your existing website and attempts to modify how content is presented to users. It doesn't change your actual website code, structure, or content. A genuine accessibility fix addresses the root cause — rewriting code to include proper form labels, adding meaningful alt text to images, restructuring headings, remediating PDF documents, ensuring keyboard navigability is built into the site's architecture. The difference is like treating a symptom versus curing the disease. One masks the problem temporarily; the other eliminates it.
Our Overlay Vendor Gave Us a Compliance Certification. Doesn't That Count?
No. A compliance certification issued by an overlay vendor is a document created by the company selling you the product — it's not an independent, third-party evaluation of your site's accessibility. The DOJ does not recognize vendor-issued certifications as proof of WCAG compliance. Neither do courts. A certification from your overlay vendor carries approximately the same legal weight as a note you wrote yourself. If you need documentation of your accessibility posture, what you need is a third-party audit report from a qualified accessibility evaluator — not a certificate generated by the tool you're paying for.
Are All Overlay Companies Equally Bad?
The products vary in their approach and their capabilities, but the fundamental limitation applies across the board: no overlay product can fully remediate the underlying accessibility issues in a website's code, content, and documents. Some companies are more transparent about these limitations than others. AudioEye, for example, has positioned itself more as a monitoring and remediation assistance platform than a one-click fix, though opinions in the accessibility community vary on how effective that approach is in practice. The safest position is to treat any overlay as a supplement at best — never as a substitute for genuine remediation work.
Can We Get Our Money Back From the Overlay Vendor?
Review your contract. Many overlay subscriptions are annual and may include auto-renewal clauses. Some municipalities have successfully negotiated early termination by documenting that the product was misrepresented as a compliance solution. If your vendor made specific claims about ADA compliance or legal protection that influenced your purchase decision and those claims are demonstrably false, you may have grounds for a refund or contract termination. Consult your municipal attorney if you believe you were materially misled.
How Do We Explain to Council That the Overlay We Paid For Isn't Working?
Be direct. The overlay was purchased in good faith based on representations that it would address the municipality's accessibility obligations. The technical and legal reality — supported by the DOJ's position, independent research, and the disability community's documented experience — is that overlays do not achieve WCAG 2.1 AA compliance and do not provide meaningful legal protection. The municipality needs to transition to a genuine remediation approach to meet the April 2027 deadline. Frame it as a corrective step, not a mistake — the information landscape around overlays has become much clearer in recent years, and many organizations that initially adopted them are now moving away from them for the same reasons.
If We Remove the Overlay, Won't Our Site Become Less Accessible?
In most cases, removing an overlay has minimal negative impact on accessibility — and in some cases it actually improves the experience for assistive technology users by eliminating the conflicts and interference the overlay was causing. Your site's baseline accessibility (its actual code-level accessibility without the overlay) is what you need to focus on, because that's what it was all along. The overlay was masking the reality of your site's accessibility, not changing it. Removing it and beginning real remediation work is a net positive, even if it feels uncomfortable in the short term.