Web accessibility lawsuits hit a record in 2025 — more than 5,000 federal digital accessibility cases filed, a roughly 40% increase year over year. Now, heading into April 2026, a major federal deadline is about to land for state and local government websites. If you run a WordPress site and haven’t taken accessibility seriously, the legal and reputational stakes have never been higher.
The Numbers You Need to Know
The growth in ADA website litigation isn’t a blip — it’s a sustained trend. ADA Title III web lawsuits have climbed sharply for several consecutive years. The reasons aren’t complicated: more disabled users are online, more plaintiffs’ attorneys have refined their processes, and — critically — AI tools are now helping self-represented individuals draft and file their own complaints without legal representation.
That last point matters. Historically, web accessibility lawsuits were concentrated among a small number of serial litigants and law firms. The barrier to entry is now lower, which means the geographic and industry spread of cases is widening. While New York, Florida, and California still account for the majority of filings, Illinois, Missouri, and Minnesota all saw significant increases in 2025. E-commerce sites remain the primary target (nearly 70% of cases), but food service, healthcare, and nonprofit sectors are all seeing more activity.
The April 2026 Government Deadline
On top of the private litigation landscape, a federal compliance deadline lands this spring. The U.S. Department of Justice finalized a rule under Title II of the ADA requiring all U.S. state and local governments — including school districts, public universities, and special districts — to bring their websites and mobile apps into conformance with WCAG 2.1 Level AA.
The deadlines break down by population:
- April 24, 2026 — Public entities serving populations of 50,000 or more
- April 26, 2027 — Smaller jurisdictions and special district governments
If your WordPress site serves a government agency, a public institution, or a contractor that delivers digital services on behalf of one, this deadline may apply directly to you. But even for entirely private sites, this moment matters: federal enforcement activity tends to raise the baseline expectations courts and regulators apply more broadly. When government agencies are being held to WCAG 2.1 AA, arguing that a commercial or nonprofit site shouldn’t be is a harder position to defend.
Why Courts Are Rejecting the Widget Defense
One of the most significant legal developments of the past year is the collapse of the “we have an overlay” defense. Research found that in 2025, an increasing number of lawsuits explicitly referenced accessibility widgets — those floating toolbar overlays that promise instant compliance — while still alleging unresolved barriers. Courts are not treating the presence of an overlay as a meaningful defense.
This isn’t surprising to anyone who has done real accessibility testing. Overlays can adjust font sizes, toggle high-contrast modes, and add skip links — cosmetic changes applied on top of the existing DOM. What they cannot do is fix missing image alt text baked into your theme, correct invalid ARIA markup in your plugins, resolve broken heading structures, or make a form whose labels are never properly associated with their inputs suddenly understandable to a screen reader.
The legal risk is compounding: a site owner pays for an overlay subscription, believes they’re covered, skips actual remediation work, and then faces a lawsuit where the plaintiff’s expert demonstrates that code-level barriers remain. The overlay becomes evidence of negligence rather than a shield against it.
What Real Remediation Actually Looks Like
Genuine accessibility work for a WordPress site means identifying and correcting issues at the source code level. That means:
- Auditing your theme’s HTML for missing landmark regions, broken heading hierarchy, and improper ARIA usage
- Checking every form for properly associated labels, clear error messages, and focus management
- Verifying that all images have meaningful (or appropriately empty) alt attributes
- Testing keyboard navigation throughout your site, including modals, dropdowns, and carousels
- Ensuring color contrast ratios meet WCAG AA minimums (4.5:1 for normal text, 3:1 for large text)
- Testing with actual screen readers — NVDA, JAWS, and VoiceOver behave differently and all three matter
No tool — automated scanner included — can catch every issue. Automated tools reliably surface somewhere between 30% and 50% of WCAG failures. Manual testing and user testing with disabled people fill the gaps. The goal isn’t a perfect automated score; it’s a site that real people with disabilities can actually use.
That said, starting with an automated scan is the right first step. You can’t fix what you haven’t found, and a good scanner will surface the most common, highest-impact issues quickly so you can triage and prioritize.
Five Things WordPress Site Owners Should Do Right Now
- Run a baseline scan. Use an automated WCAG scanner to get a clear picture of where you stand. Don’t guess at your exposure level.
- Fix structural issues in your theme first. Heading hierarchy, landmark regions, and skip links are foundational. Theme-level problems repeat across every page.
- Audit your contact forms and checkout flows. Forms are disproportionately represented in accessibility complaints. Label every field. Provide clear, programmatically associated error messages.
- Add an accessibility statement. Documenting your efforts, known limitations, and a contact method for users who encounter barriers demonstrates good faith — and that can matter if a complaint is filed.
- Set up ongoing scanning. Accessibility isn’t a one-time project. New content, plugin updates, and theme changes can all introduce new issues. Treat it as infrastructure maintenance, not a checkbox.
The April 2026 deadline for government sites is a signal, not an isolated event. Private businesses and nonprofits are watching the same enforcement environment evolve. Organizations that will be best positioned — legally and reputationally — are the ones treating accessibility as a continuous practice rather than something they fixed once and forgot.
Take Action
LEWCA gives WordPress site owners the tools to find and fix real accessibility issues — not cosmetic overlays, but actual code-level problems identified by the LEWCA scanner (which ships alongside an admin-controlled visitor toolbar). The free plan covers baseline scanning and the visitor accessibility toolbar. LEWCA Pro adds AI-powered fix suggestions, scheduled scans, and compliance reporting, so you’re not just finding issues once but staying on top of them as your site evolves. See what’s included at our pricing page, or download LEWCA and run your first scan today.