If you manage a nonprofit website, you have likely received aggressive sales emails from companies promising "instant, 100% automated ADA and WCAG compliance" by pasting a single line of JavaScript onto your website. These products—known as accessibility overlays or widgets—usually place a small blue wheelchair icon in the bottom corner of your screen.
To a busy executive director, an overlay sounds like an easy, affordable fix for a complex legal and technical challenge. But in reality, accessibility overlays are a dangerous illusion that actually harms disabled visitors and paints a target on your organization for digital accessibility lawsuits.
"You cannot automate civil rights compliance with a JavaScript widget. True accessibility requires respect for constituent dignity written directly into the source code."
Why the Disability Community Rejects Overlays
More than 800 independent accessibility advocates, blind professionals, and assistive technology experts signed the Overlay Fact Sheet (an open letter documenting why overlays fail). Here is why:
- They Interfere with Screen Readers: Blind visitors already have specialized screen-reading software (JAWS, NVDA, VoiceOver) configured to their exact preferences. Overlays often override these settings, creating jarring disorientations.
- They Cannot Fix Underlying Code Flaws: An overlay cannot add meaningful, context-aware alt text to photos of your community programs, nor can it fix broken keyboard navigation traps inside donation modals.
- They Demand Extra Effort from Disabled Users: Overlays force disabled constituents to click into a third-party toolbar just to read text or adjust contrast—violating the principle of equal, unsegregated access.
The Legal Truth: Overlays Do Not Protect You
In federal and state courts across the United States, hundreds of ADA Title III lawsuits have been filed against websites that had active overlay widgets installed. Legal analysts note that plaintiff attorneys specifically search for overlay scripts in web source code because their presence proves:
- The organization knows that digital accessibility is a legal obligation.
- The organization has not actually remediated its underlying digital infrastructure.
The Ethical MSW Approach: Root-Level Remediation
At Nonprofit Web Developer, we build accessibility directly into the HTML foundation:
- Native Semantic HTML5: Clean landmarks (`
`, ` `, ` - WCAG 2.2 AA Color Contrast: Hand-tested typography ratios that ensure readability without clunky toolbar toggles.
- Keyboard-First Forms: Donation, volunteer, and contact forms designed from the ground up to operate via keyboard alone.
Have an overlay widget on your site?
Let's perform a true WCAG 2.2 AA source code audit and fix accessibility issues at the root level.
Request a Source Code Accessibility Audit