The pitch usually arrives when you're most likely to say yes. A peer organization just got a demand letter, or a board member asked whether the website is "ADA compliant" and nobody in the room had an answer. Then an ad appears: add one line of code, pay a monthly fee, and your site is instantly accessible and lawsuit-proof.
For a small team with no developer on staff, that offer is built to be an easy purchase. It names a real fear, it prices itself below the threshold where anyone asks hard questions, and it asks nothing of your time.
We've worked only with nonprofits since 2007, and we've watched this exact purchase happen again and again. This post walks through what that monthly fee actually buys, why the answer to "do accessibility overlays work" is not what the sales page suggests, and where the same money would do more good.
What an overlay actually is
An accessibility overlay is a third-party widget you add to your site with a snippet of JavaScript. It places a toolbar on top of your pages, usually a small icon in the corner that opens a settings panel where visitors can enlarge text, change contrast, or pause animations.
That's the key detail: the overlay sits on top of your website. The code your team or your last agency built is unchanged underneath.
Now compare that to the standard your nonprofit is measured against. The Web Content Accessibility Guidelines (WCAG) are the technical standard that courts, auditors, and settlement agreements reference in Americans with Disabilities Act (ADA) cases, and we've covered what ADA compliance means for nonprofit websites in detail. WCAG doesn't ask whether your site offers a settings toolbar. It asks about the code itself: whether images have text descriptions, whether form fields have labels, whether every function works from a keyboard, whether headings follow a logical order, and whether color contrast meets minimum ratios.
An overlay can't write a meaningful description of your impact photos. It can't label the donation form fields your CRM embedded, and it can't untangle a navigation menu that traps keyboard users. Some overlay vendors claim their software repairs these problems automatically, but software that has never met your organization can only guess at what your content means, and a wrong guess about what a photo shows or what a form field collects doesn't help the visitor who depended on it being right.
What accessibility practitioners and the legal record say
We should be upfront that we sell accessibility services ourselves, so you'd be right to ask whether this is just one vendor knocking another. That's why the sources in this section matter more than our opinion does.
The Overlay Fact Sheet is an open statement signed by hundreds of accessibility practitioners, including consultants, auditors, developers of assistive technology, and daily users of it. Its position is direct: automated overlay products shouldn't be relied on as a path to compliance, because the underlying code has to be fixed.
The legal record points the same way. Accessibility-litigation reporting has documented complaints and demand letters filed against organizations whose sites were running an overlay at the time. The widget didn't make them a smaller target, and in some of those complaints the overlay itself is named as one of the barriers.
This matters because certainty about legal exposure is the main thing the subscription is sold on, and the documented cases show the product doesn't provide it. You're paying every month for protection that has not held up when tested.
The people you bought it for aren't asking for it
Overlay marketing tends to present the toolbar as a service to visitors with disabilities, but the view from those visitors is different. People who rely on assistive technology don't arrive at your site needing your toolbar, because they bring their own tools: a screen reader (software that reads a page's underlying code aloud), their own magnification, and their own contrast settings, configured over years to work the way they need on every site they visit.
For those visitors, an overlay adds a second layer of software between their tools and your content. Layered over broken code, that second layer can interfere by intercepting keystrokes the screen reader depends on, injecting markup that changes what gets announced, or overriding settings the visitor already chose. Some assistive-tech users go as far as installing browser extensions built specifically to block overlays.
So when someone asks us whether accessibility overlays work, the honest answer has two parts: the people the product is named for can find that it interferes with the tools they already use, and the widget does nothing to fix the underlying code that WCAG actually measures.
Where that line item should go instead
If you're paying monthly for an overlay, you already have an accessibility budget, which means you don't need to spend more. You need to point the same money at the code.
Start with an audit of the paths that matter most. Not every page at once. Your donation flow, your main navigation, and your contact and signup forms carry the traffic your mission depends on, so find out what's actually broken there first. Our guide to nonprofit accessibility best practices walks through what a real review covers.
Fix in priority order. Barriers that stop someone from completing a task, such as an unlabeled donation field or a menu that can't be escaped by keyboard, come before cosmetic issues. A prioritized fix list turns "accessibility" from an infinite project into a finishable one.
Then build it into the content workflow. Most accessibility debt is created one blog post at a time: an image uploaded without alt text, a heading chosen for its size instead of its place in the outline, a link that says "click here." Once your team writes those correctly by habit, the site stops drifting backward. This part costs staff attention rather than money.
There's a second return on the same work. The code-level fixes that serve assistive technology are the same fixes that make your site readable to AI assistants, which parse your raw HTML much the way a screen reader does. We've written about that overlap in Accessibility Is AI Readability. None of that benefit comes from an overlay, because the widget never changes the HTML those systems read.
Two questions that sort every vendor
You don't need to become a WCAG expert to buy accessibility work safely, because two questions do most of the sorting.
"Will this change our underlying code?" If the answer is no, and everything happens in a layer on top, you now know exactly what you're buying, whatever the sales page promises.
"Can you show WCAG conformance when the work is done?" A legitimate provider will tell you which WCAG level the work targets (2.1 AA is the common benchmark), show you what was tested, and document what was fixed and what remains. A vendor who can't produce that documentation is asking you to pay for a promise they can't verify.
Most legitimate providers can answer both questions in a sentence or two, and if a vendor hedges on either one, treat that as a reason to keep looking.
If you're paying for an overlay right now
The sensible next step is to find out what your current widget actually covers before you renew it. The product was engineered to be an easy purchase for organizations in exactly your situation, but that monthly fee deserves to buy something real.
Whether a demand letter has you shopping or you simply want a straight answer about your current setup, bring it to a free accessibility consultation. We'll tell you honestly what it's covering, what it isn't, and what to fix first.
