Imagine someone with no legal background, a WCAG checklist, and a chatbot drafting an ADA accessibility complaint against your website in under an hour — without ever hiring a lawyer. In 2025, that scenario played out more than 1,200 times in U.S. federal courts. Pro se ADA Title III filings (cases where the plaintiff represents themselves) jumped 40% compared to 2024, with researchers pointing to AI tools like ChatGPT and Copilot as the accelerant. For small and mid-size business WordPress sites that have been quietly hoping to stay under the radar, this trend changes the risk calculation significantly.
The Numbers Behind the Shift
Federal web accessibility lawsuit filings hit 3,117 in 2025 — a 27% increase over 2024’s 2,452 cases. When state-court filings are included, total digital accessibility lawsuits topped 5,000 for the year. New York and California state courts alone accounted for nearly 2,000 cases between them.
But the more telling development is who is filing. Historically, most ADA Title III website lawsuits came from a small number of plaintiff law firms running systematic, volume-driven campaigns. They targeted businesses with high web traffic and the financial capacity to settle. Small business owners sometimes felt — not unreasonably — that they weren’t worth a firm’s time.
AI has changed that math. With a large language model, a motivated individual can research WCAG requirements, test a site using a free automated tool, identify violations, and draft a complaint that meets federal filing standards. The attorney is optional.
Why Small WordPress Sites Can No Longer Assume They’re Safe
The traditional accessibility lawsuit model was largely driven by economics. A plaintiff firm running campaigns needed cases where the expected settlement justified the cost of identifying barriers, writing demand letters, and managing litigation. Larger e-commerce sites offered more predictable returns.
Pro se plaintiffs operate under different incentives. Many are people with disabilities who genuinely encountered real barriers — an unlabeled form field that stumped their screen reader, a checkout flow that couldn’t be completed by keyboard, a video with no captions. The complaint is a response to an actual experience, not a business calculation. That means no business is too small to be noticed.
E-commerce sites remain the primary target, accounting for nearly 70% of all ADA web lawsuits. Food and service businesses represent around 21%. But the common denominator isn’t size or traffic — it’s the presence of identifiable WCAG failures that real users actually encounter.
Why Having an Accessibility Widget Still Isn’t Enough
One of the most consistent findings in recent accessibility litigation data is that overlays and widgets offer very limited legal protection. Courts continue to expect substantive remediation — actual fixes to the underlying code — not a JavaScript layer that attempts to patch problems at render time.
A separate study of 2025 cases found that 38% of businesses that received demand letters or were sued had already installed some form of accessibility tool. The widget gave them a false sense of security. The plaintiff’s automated scan found issues the overlay hadn’t resolved.
This is a structural limitation of overlays: they modify what users see by intercepting the rendered page, but they can’t reliably fix every underlying barrier. Screen reader users in particular have reported that some overlays actively interfere with their assistive technology by injecting competing ARIA attributes or hijacking keyboard focus.
What Automated Scans — and Plaintiffs — Are Looking For
Free accessibility testing tools can detect many common WCAG failures in minutes, which means a prospective plaintiff using the same tools can too. The issues that appear most frequently in ADA web complaints include:
- Images missing descriptive alt text
- Form inputs without visible labels or programmatic associations
- Videos without captions or transcripts
- Interactive elements that can’t be reached or activated by keyboard alone
- Color contrast ratios below WCAG 2.1 AA minimums (4.5:1 for normal text, 3:1 for large text)
- Custom components with broken or missing ARIA attributes
- Pages that don’t declare a language in the HTML tag
None of these are obscure edge cases. They’re the first things any automated WCAG scanner checks, and they show up on the majority of sites that haven’t been through a structured accessibility audit.
What Substantive Remediation Actually Looks Like
Reducing your legal exposure means fixing the underlying code, not installing something that attempts to mask the problems. That doesn’t have to be overwhelming — most sites have a concentrated set of issues that, once resolved, eliminate the majority of their barrier risk.
- Run a code-level accessibility scan — one that flags actual WCAG failures in your HTML markup, not just widget installation status. You need to know what’s broken and where.
- Prioritize high-frequency issues — alt text, form labels, keyboard navigation, and color contrast together account for a large share of complaints.
- Start with your most-visited pages — home, product or service pages, contact forms, and checkout flows are where users spend the most time and where barriers are most likely to be encountered.
- Post an accessibility statement — describe your current conformance level and give users a way to report barriers. Courts look more favorably on businesses that are visibly engaged with accessibility.
- Treat it as ongoing maintenance — new content, plugin updates, and theme changes can introduce new issues. A one-time audit doesn’t stay accurate indefinitely.
The Broader Context: Deadlines Are Still Shifting
The Department of Justice recently extended its ADA Title II web accessibility deadline for larger public entities from April 2026 to April 2027, with a public comment period open through June 22, 2026. For private businesses covered by ADA Title III — the law that applies to most commercial websites — no formal compliance deadline has ever been set. That’s exactly why private-sector enforcement has historically happened through litigation rather than regulatory action. The absence of a deadline doesn’t mean the absence of legal risk; it means the risk is distributed unpredictably through individual lawsuits.
The 40% rise in pro se filings is a signal that the plaintiff pool is no longer constrained to what law firms choose to pursue. It’s expanding to include anyone who encounters a barrier and has access to a search engine, a free scanner, and an AI writing assistant — which in 2026 is an increasingly large number of people.
Take Action
LEWCA’s free plan includes a WCAG scanner that audits your WordPress site’s actual HTML for real code-level failures — the same category of issues that appear in ADA complaints. It’s not an overlay; it’s a structural analysis that tells you what needs to be fixed and where. The Pro plan adds AI-powered fix suggestions and scheduled scans, so new issues introduced by content updates or plugin changes get caught before they become someone else’s legal argument. Download LEWCA for free at /download/ or compare plans at /pricing/.