28% of all digital accessibility lawsuits filed in 2025 targeted websites that had an accessibility overlay widget installed — up from 25% the year before. Given WordPress’s roughly 40% share of the web, and roughly 8,800 ADA-related lawsuits filed annually, a real share of that litigation is landing on WordPress sites specifically, and having an overlay installed doesn’t protect against it. In some documented cases, it’s actively cited as evidence against the defendant.
Why Overlays Don’t Actually Fix Accessibility
An overlay widget works by injecting a layer of JavaScript on top of an existing page — adjusting font size, contrast, or adding some keyboard-navigation patches — without touching the site’s underlying code. That’s a fundamental limitation: overlay plugins typically address only 20–30% of WCAG success criteria, meaning they leave 50+ WCAG criteria unaddressed, including structural issues like broken keyboard navigation or missing form labels that no surface-level overlay can meaningfully fix.
Why Courts Reject Overlays as a Defense
No legal precedent currently supports overlays as a defense against an accessibility lawsuit — courts have consistently dismissed the argument that installing a widget satisfies ADA or WCAG obligations. More pointedly, some plaintiff’s attorneys have specifically cited overlay usage in complaints, arguing it demonstrates the site owner was aware of accessibility requirements and chose the cheapest possible response rather than genuine remediation — which can work against the defendant rather than in their favor.
The Numbers
| Metric | Data |
|---|---|
| Digital accessibility lawsuits targeting overlay-using sites, 2025 | 28% (up from 25% in 2024) |
| WCAG success criteria overlays typically address | 20–30% |
| WCAG criteria left unaddressed by overlays | 50+ |
| Legal precedent supporting overlays as a defense | None |
What Actually Reduces Risk
- Remediate at the code and design level, not through a surface-layer widget — semantic HTML, real keyboard navigation, proper form labels, and correct color contrast built into the theme and content itself.
- If you already have an overlay installed, don’t treat it as done — given the documented pattern of overlays specifically being cited in complaints, it’s worth confirming genuine remediation work exists behind it, not just the widget.
- Run a real WCAG audit against actual success criteria, not a scan that only checks for overlay-addressable surface issues.
- Prioritize the transactional and high-traffic pages first — forms, checkout, navigation — the same pages that carry the highest legal exposure carry the highest genuine accessibility impact too.
This directly extends ADA Website Lawsuits Are Up 27% in 2026 and Color Contrast in Block Themes: A Practical WCAG Guide. Want a real WCAG audit instead of an overlay quick-fix? Get in touch.
Frequently Asked Questions
Should I remove an overlay widget if I already have one installed?
Not necessarily immediately, but it shouldn’t be treated as your accessibility solution — the real priority is genuine code and content remediation; whether the overlay stays as a supplementary tool afterward is a secondary decision.
Do overlays help with any real accessibility issues at all?
They can address some surface-level adjustments (font size, basic contrast toggles), but they only cover roughly 20–30% of WCAG success criteria and don’t touch structural issues like broken keyboard navigation or missing semantic markup.
Is a genuine WCAG remediation more expensive than an overlay?
Typically yes upfront, but given the documented lawsuit pattern specifically targeting overlay-using sites, genuine remediation is the approach that actually reduces legal exposure rather than potentially increasing it.
Featured image: original illustration.