You do not need a lawyer to sue a business for ADA violations anymore.
AI ADA lawsuits (accessibility claims filed without attorneys, powered by tools like ChatGPT) have become a routine legal risk for businesses with public-facing websites. That changed quietly over the past two years, and most business owners have no idea it happened.
People with disabilities are now using ChatGPT, Microsoft Copilot, and Google Gemini to scan websites for WCAG violations, draft federal complaints, and file them in court. The whole process takes a few hours. It used to take a $5,000 legal retainer and weeks of back-and-forth with an attorney.
The results are showing up in the data. Federal pro se ADA Title III lawsuit filings surged 40% in 2025, according to Seyfarth Shaw’s ADA Title III tracking. Total ADA digital accessibility lawsuits hit 8,667 in 2025. And 2026 is trending higher.
If your website has accessibility barriers, someone with a smartphone and a free AI subscription can find them and sue you from their living room.
This post explains how that works, what AI is looking for on your website, who is being targeted, and what you can actually do about it.
Key Takeaways
- Pro se ADA lawsuits (filed by individuals without attorneys) surged 40% in 2025, largely driven by AI tools like ChatGPT and Microsoft Copilot.
- 8,667 ADA lawsuits were filed in 2025. Digital accessibility cases are on track to exceed 6,000 in 2026, a record high.
- Ecommerce and retail account for 69% to 77% of all website ADA lawsuits.
- The six WCAG failures that appear in almost every lawsuit are: missing alt text, low contrast text, unlabeled forms, empty links, inaccessible keyboard navigation, and missing document language.
- Accessibility overlays do not help. 22.6% of 2025 lawsuits targeted sites that had an overlay widget installed.
- The National Federation of the Blind sued the DOJ in May 2026 over delayed ADA Title II deadlines, pushing for faster enforcement.
- The only reliable protection is fixing the actual code. A professional WCAG 2.2 accessibility audit shows you exactly what needs fixing and in what order.
What Is a Pro Se ADA Lawsuit?
“Pro se” is a Latin term meaning “for oneself.” A pro se plaintiff is someone who files a lawsuit without hiring a lawyer. In most areas of law, this is rare because the legal drafting alone is complex enough to discourage it.
ADA website cases changed that equation.
The legal theory in an ADA Title III website case is relatively straightforward: a public accommodation (a business that serves the public) has a website, the website has barriers that prevent someone with a disability from using it equally, and that is a violation of the ADA. The key facts are technical, not legal: the specific WCAG criterion violated, how it caused the barrier, and what the plaintiff experienced.
That technical part is exactly what AI tools do well.
A blind plaintiff can describe what happened when they tried to use a website with their screen reader. They can paste the page source or a WCAG audit result into ChatGPT. The AI identifies the specific WCAG success criteria that were violated, explains the legal theory in plain language, and drafts a complaint. The plaintiff reviews it, corrects anything that does not match their experience, and files.
Courts have seen a sharp increase in this pattern. Seyfarth Shaw’s ADA Title III litigation blog noted that federal pro se ADA Title III and FHA filings are up significantly and that AI is the likely driver. Some plaintiffs are filing dozens of cases at a time.
This is not a loophole. People with disabilities have a legal right to sue under the ADA. AI has simply removed the financial barrier to exercising that right.
How Big Is the ADA Lawsuit Problem in 2026?
The numbers from 2025 make clear this is not a niche legal issue.
UsableNet’s 2025 lawsuit data shows 5,000+ digital accessibility lawsuits targeting websites and apps in 2025 alone, a 37% increase over 2024. Total ADA lawsuits across all types reached 8,667. And 2026 data through mid-year shows the trajectory heading higher, with digital accessibility cases on pace to break 6,000 for the year.
Ecommerce is the primary target. TestParty’s analysis found that ecommerce and retail websites accounted for 69% to 77% of all filings. Among the top 500 US ecommerce retailers, 35.8% received at least one ADA accessibility lawsuit.
The largest settlement in 2025 was Fashion Nova’s $5.15 million class action resolution, the highest web accessibility settlement on record. That case covered blind shoppers who could not independently use the site’s navigation, product images, and checkout. The average lawsuit, even one that settles quickly, still costs $60,000 to $200,000 when you add defense fees and remediation costs.
By geography, New York accounts for 31.6% of filings, Florida for 24.2%, and California for 18.9%. Illinois saw a 746% increase in 2025, jumping from 28 cases in 2024 to 237.
What Is AI Looking for on Your Website?
This is the part most businesses do not think about.
When a pro se plaintiff uses an AI tool to evaluate a website, the AI is not just running a general scan. It is being told to look for specific, legally actionable WCAG failures. And it is good at finding them because most websites have them on every page.
The six violations that appear in the vast majority of ADA website lawsuits are:
1. Missing alt text on images (WCAG 1.1.1) Screen readers read alt text aloud to blind users. If a product image, banner, or icon has no alt text or has a filename like “img_7234.jpg,” a screen reader user gets either silence or a string of characters that means nothing. In ecommerce, this means a blind shopper cannot know what they are looking at.
2. Low contrast text (WCAG 1.4.3) 79.1% of websites fail the minimum contrast requirement. Gray text on a white background, light text on a light image, and faded placeholder text in form fields all fail. Users with low vision cannot read them. WCAG requires a 4.5:1 contrast ratio for normal text and 3:1 for large text.
3. Unlabeled form fields (WCAG 1.3.1, 3.3.2) Missing form labels appear in 48.2% of sites. When a form field has no programmatic label, a screen reader user lands on a text box with no indication of what belongs there. They cannot complete signup forms, checkout forms, or contact forms independently.
4. Empty links (WCAG 2.4.4) 45.4% of websites have links that say “click here,” “read more,” or have no visible text at all. Screen reader users navigate by pulling up a list of all links on a page. A list of “click here” links is useless. They cannot tell which link goes where without reading the surrounding paragraph every time.
5. Keyboard navigation failures (WCAG 2.1.1) People who cannot use a mouse rely entirely on keyboard navigation. Tab through your website. If you cannot reach every interactive element, activate it, and move past it using only the keyboard, keyboard-only users are locked out. Modal dialogs that trap keyboard focus and carousels with no keyboard controls are extremely common lawsuit targets.
6. Missing document language (WCAG 3.1.1) 15.8% of pages fail to declare their language in the HTML. Screen readers use the declared language to select the correct voice and pronunciation. Without it, a page in English may be read aloud using a French or Spanish voice model, making it incomprehensible.
These are not edge cases. According to 2026 web accessibility statistics, 94.8% of home pages still fail at least one WCAG 2.2 Level A or AA checkpoint.
An AI tool given a URL can identify most of these failures in minutes.
How AI Files ADA Lawsuits Faster Than You Expect
Here is what the process looks like in practice, based on reporting from Deque’s analysis of AI-powered pro se lawsuits and Accessibility.Works.
A plaintiff or their advocate visits your website with a screen reader. They encounter a barrier: a product image with no description, a checkout button that is unreachable by keyboard, or a form that announces nothing when submitted. They note the URL and the specific interaction that failed.
They then take one of two approaches. They paste your website’s source code or an automated scan output into ChatGPT and ask it to identify WCAG violations. Or they describe the experience and ask ChatGPT to map it to the relevant WCAG success criteria and ADA requirements. In either case, the AI returns a structured list of violations with the specific criterion number, the technical explanation, and the legal impact.
That output goes into a complaint draft. The AI produces a legally structured document naming the business, describing each barrier, citing the WCAG criteria and ADA sections, and requesting injunctive relief and damages.
The plaintiff files it in federal court, often in a jurisdiction they know is favorable.
You receive a summons.
The entire process from visit to filing can take one business day.
What Are the Real Regulatory Stakes in 2026?
Beyond private lawsuits, federal regulators are tightening the rules, and advocacy groups are pushing back on any delays.
In April 2026, the DOJ issued an interim final rule extending ADA Title II WCAG 2.1 AA deadlines for state and local governments. Phase 1 (larger entities) moved from April 24, 2026 to April 26, 2027. Phase 2 (smaller entities) moved to April 26, 2028. Full Federal Register details are here.
The National Federation of the Blind did not accept this quietly. On May 21, 2026, NFB sued the DOJ and HHS in the US District Court for the District of Maryland, challenging the deadline extensions as violations of the Administrative Procedure Act. NFB argues the agencies issued the interim rules without required public notice and comment, and that the delays cause concrete harm to people with disabilities who depend on accessible government services.
HHS’s Section 504 WCAG 2.1 AA deadline for healthcare organizations with 15 or more employees receiving federal funding also moved to May 11, 2027 under the same rule.
For private businesses, ADA Title III continues to apply without the deadline extensions, which only cover government entities. Private ecommerce sites, SaaS products, and consumer-facing apps remain exposed to litigation today under existing Title III standards.
Does an Overlay Protect You?
No. This comes up constantly and the answer is still no.
22.6% of all ADA website lawsuits in 2025 targeted websites that had an accessibility overlay widget installed. These are the tools that promise to make your site compliant via a JavaScript snippet. Over 800 businesses with an overlay active were still sued and lost.
The Federal Trade Commission made this even clearer in April 2025, fining an accessibility overlay company $1 million for falsely claiming their product could make websites ADA compliant. The FTC’s ruling was explicit: overlays do not fix underlying code barriers.
Screen readers interact with your HTML directly. They do not see or process an overlay’s modifications the same way a sighted user clicking the overlay widget does. If the barrier is in your source code, it is there for assistive technology users whether the overlay is running or not.
We have tested sites with JAWS and NVDA while overlays were active. The barriers are in the code every time.
We covered this in depth in our post Do Accessibility Overlays Protect You From ADA Lawsuits?, including the FTC ruling and the specific technical reasons overlays fail screen reader users.
Real protection comes from one thing: fixing the actual code against WCAG 2.2 Level AA. Our accessibility remediation service does exactly this, delivering verified pull requests tied to specific audit findings.
Who Is Most at Risk Right Now?
Based on 2025 and 2026 litigation patterns, the highest-risk profiles are:
Ecommerce and retail businesses. Product images with missing alt text, inaccessible checkout flows, and filter/sorting widgets that do not work with a keyboard are the most common targets. If you run an online store, this applies to you. See our ecommerce accessibility services for what we typically find and fix.
SaaS and web applications. Complex UI components like data tables, dropdown menus, and drag-and-drop interfaces have a high failure rate for keyboard navigation and screen reader compatibility. Our SaaS accessibility practice covers VPAT documentation for enterprise procurement alongside the audit work.
Healthcare organizations. Patient portals, appointment booking systems, and telehealth platforms are legally required to be accessible under Section 504 (federal funding recipients) and are increasingly targeted by pro se plaintiffs. Our healthcare accessibility services address both WCAG 2.1 AA and the HHS Section 504 requirements.
Any business that installed an accessibility overlay and stopped there. These businesses have a false sense of compliance and are actively being targeted.
Businesses in New York, Florida, California, and Illinois. These four states account for the vast majority of US ADA website lawsuits by volume.
You can explore our ADA and WCAG compliance services or contact us for guidance specific to your situation.
What Happens After You Receive an ADA Demand Letter
Most businesses first learn about their accessibility exposure not from a lawsuit filing but from a demand letter. An attorney or advocacy organization sends a letter stating that your website violates the ADA, that you have a specific number of days to respond, and that failure to respond will result in litigation.
The letter arrives before the lawsuit. ADA demand letters typically precede lawsuit filings by 10 to 30 days. They name specific WCAG failures, often pulled directly from an automated scan or a screen reader test session. Some plaintiff’s attorneys send hundreds of letters at a time, particularly in New York, Florida, and California. Many of these letters are now generated with AI assistance. The same AI tools that identify WCAG violations can draft demand letters at scale.
You have limited time to respond. Most letters give a response window of 30 days or fewer. If you acknowledge the issues, express a commitment to remediate, and provide a documented timeline, many demand letters resolve without formal litigation. Courts and opposing plaintiffs respond better to businesses that demonstrate genuine good-faith effort than to those who deny or ignore the claim.
Settlement is the most common outcome. The vast majority of ADA website cases settle before trial. Settlement amounts typically range from $5,000 for smaller businesses to over $200,000 for larger companies with multiple violations across many pages. Attorneys’ fees can double those figures on top of any settlement. The financial calculus almost always favors proactive remediation over litigation costs.
Overlay installation is not a defense. A common mistake businesses make after receiving a demand letter is to immediately install an accessibility overlay, hoping to resolve the claim quickly. Courts have consistently found that overlays do not constitute adequate remediation. Multiple plaintiffs have returned with renewed AI ADA lawsuits after a business installed an overlay in response to a prior demand.
What actually helps: A professionally conducted WCAG 2.2 audit, a documented remediation plan with milestones, and rapid deployment of fixes, particularly to the pages cited in the demand letter. Our accessibility audit services include a fast-track option specifically for businesses responding to a demand letter or active litigation.
How to Actually Reduce Your Risk
There is no legal strategy that fully replaces genuine accessibility. Businesses that try to argue around the ADA in court spend more money than businesses that fix their websites.
Here is what actually reduces risk:
1. Get a professional WCAG 2.2 AA audit. Not an automated scan. Automated tools catch roughly 30% to 40% of WCAG issues. The failures that generate the most lawsuits (missing alt text on complex images, keyboard traps in custom components, broken screen reader announcements) require manual testing with real assistive technology. Our accessibility audit services use JAWS, NVDA, and VoiceOver, and every finding includes a developer-ready fix.
2. Fix the code. Audit findings are only useful if they get remediated. Prioritize the six failures listed earlier in this post first. They account for the most lawsuits and are typically the fastest to fix.
3. Publish an accessibility statement. A clear, accurate accessibility statement with a contact mechanism for reporting barriers signals good faith. Courts and plaintiffs both notice whether a business is making a genuine effort.
4. Produce a VPAT or ACR if you serve enterprise or government clients. If you sell to companies that require a Voluntary Product Accessibility Template, your VPAT needs to be accurate. Inaccurate VPATs have led to their own legal exposure. Our VPAT and ACR documentation service produces VPATs after real assistive technology testing. See how we delivered a procurement-ready VPAT for Happeo in 7 days.
5. Treat accessibility as ongoing, not a one-time project. Every new feature, redesign, and third-party integration can introduce new barriers. Embedding accessibility into your development process (design reviews, code review, QA) is what prevents violations from accumulating. Our accessibility monitoring and governance service handles this with scheduled scans, manual sampling, and regression alerts after launch.
The Bottom Line
AI did not create the ADA. It did not create the accessibility requirements that have applied to websites for over a decade. What AI did was remove the financial and logistical barriers that kept people with disabilities from exercising their legal rights.
That is not a flaw in the system. It is the system working. People who encounter an inaccessible website now have a real way to hold businesses accountable.
For businesses, the practical reality is this: AI can find your WCAG violations before you fix them, and it can file a federal complaint the same day. The websites that are not getting sued are the ones that made accessibility a genuine priority, not an afterthought.
If you are not sure where your website stands, the best starting point is a professional WCAG 2.2 accessibility audit. It shows you exactly what needs fixing, mapped to the WCAG criteria that courts and plaintiffs cite, so you can prioritize the work that matters most.
Contact us to get a preliminary assessment and find out what your website looks like to someone using a screen reader.
