Nearly four in ten businesses sued for web accessibility violations in 2025 already had an accessibility tool installed when the lawsuit was filed. That number — 38.5%, according to AudioEye’s 2026 Web Accessibility Litigation Report — should stop any WordPress site owner cold. If you’re relying on an overlay widget or a simple accessibility plugin to keep you out of legal trouble, the data suggests it may not be doing what you think.
The 2025 Lawsuit Numbers Are Sobering
Last year was a record-setter for web accessibility litigation. Plaintiffs filed 3,117 website accessibility lawsuits in U.S. federal court — a 27% jump over 2024’s 2,452 cases. Factor in state court filings and total digital accessibility lawsuits topped 5,000 for the year. E-commerce and retail sites absorbed roughly 70% of the caseload, food and beverage came in at 21%, and a rapidly growing healthcare segment is now under added scrutiny following new federal accessibility rules that took effect this spring.
For WordPress site owners, the practical takeaway is this: if your site has WCAG violations, the likelihood that someone finds them — and does something about it — is higher than it has ever been. And two structural changes in how these lawsuits are filed are making the environment even more dangerous.
AI Is Making Accessibility Lawsuits Easier to File
The traditional model of accessibility litigation involved a plaintiff, a specialized attorney, and a labor-intensive manual audit. That model is changing. A growing share of 2025 lawsuits were filed by plaintiffs without lawyers — individuals using AI tools to scan websites for accessibility failures, identify specific WCAG violations, and generate legally coherent complaints without hiring counsel.
At the same time, cases are migrating from federal court to state courts, where filing is cheaper, proceedings are faster, and in many jurisdictions the legal theories available to plaintiffs are broader than federal ADA claims. The combination of AI-assisted scanning and lower-cost state court venues has dramatically lowered the barrier to initiating accessibility litigation.
The practical implication: your site is more likely to be scanned automatically, and any violations found are more likely to result in a demand letter or lawsuit than they would have been two or three years ago. Serial accessibility plaintiff activity, which was already a documented concern, is now significantly easier to scale.
Why Having an Accessibility Tool Installed Isn’t Enough
Back to that 38.5% figure. Most accessibility tools available to WordPress site owners today are overlays — JavaScript widgets that layer on top of your existing site and attempt to fix issues dynamically. They might adjust contrast ratios on the fly, inject ARIA labels onto images, or offer a screen reader mode toggle in the corner of the page.
The core problem is that these tools don’t modify your site’s actual code. They mask symptoms. And the legal standard for ADA compliance is genuine WCAG conformance — not the appearance of effort. Courts, plaintiff attorneys, and the DOJ’s own guidance have been consistent on this point: a tool that sits on top of your site without fixing the underlying markup does not constitute compliance.
Common issues that overlays routinely miss or handle poorly include:
- Complex interactive components — custom dropdowns, date pickers, modal dialogs, and carousels
- PDFs and downloadable documents linked from your WordPress media library
- Third-party embedded content such as maps, video players, and social media widgets
- Dynamic content loaded by JavaScript after the initial page render
- Keyboard focus management in multi-step interactions
- Logical reading order in complex page layouts
If a plaintiff’s automated scanner or an actual screen reader user finds these issues — and they will — the fact that you had a widget installed provides little legal protection. In some cases it can work against you: it may indicate that you were aware of accessibility concerns and chose a surface-level patch rather than a substantive fix.
What Actually Reduces Your Risk
No tool or process eliminates lawsuit risk entirely — be skeptical of anyone who claims otherwise. But there are concrete steps that meaningfully reduce your exposure and, critically, put you in a much stronger position if you do receive a demand letter.
Fix actual code, not just the display layer
Remediating real code-level issues is the only durable solution. Missing alt text should be corrected in your content and theme. Form labels should be properly associated in the HTML. Color contrast failures should be resolved at the CSS level. Focus management should be implemented in your JavaScript. These fixes persist across every user, every assistive technology, and every automated scanner — including the ones plaintiffs use.
Scan on a schedule, not just once
WordPress sites are not static. Plugins update, themes change, content editors add new pages and images. A one-time accessibility audit becomes stale within weeks. Recurring automated scans give you visibility into regressions before an external scanner finds them first — and give you a timestamped record of ongoing remediation effort.
Publish an honest accessibility statement
An accessibility statement tells users what standards you’re working toward, what known limitations currently exist, and how to contact you if they encounter a barrier. This is required for sites serving EU users under the European Accessibility Act, and it signals good faith to anyone scrutinizing your site. Keep it honest — don’t claim full WCAG 2.1 AA conformance if you haven’t verified it through thorough testing.
Document your remediation process
If you receive a demand letter, the most valuable thing you can have is documented evidence of a good-faith, ongoing remediation program. Timestamped scan reports, a log of issues identified and fixed, and a clear record of what you’ve done — and what you’re working on — are concrete assets in any settlement negotiation or legal proceeding. Courts respond differently to defendants who can demonstrate genuine effort versus those who have nothing to show.
Take Action
LEWCA is a WordPress accessibility plugin built around fixing the actual code, not masking it. Its WCAG scanner identifies real code-level issues in your WordPress installation, and the Pro plan adds AI-powered fix suggestions, scheduled scanning, and compliance reports you can use to document your remediation program over time. If you’ve been relying on an overlay, or haven’t audited your site at all, now is the time to change your approach. Review the LEWCA pricing plans or download the free version and run your first scan today.