Website accessibility lawsuits: what actually decides whether your classifieds site gets sued
Almost every legal risk covered on this blog exists because of what a classifieds directory publishes. This one does not. A law firm that tracks these cases every year counted 3,117 federal lawsuits filed in 2025 alleging that a website could not be used by someone who is blind, low vision, or unable to use a mouse, up 27% from 2,452 the year before. The firms filing them pick targets by scanning for keyboard traps, missing form labels, and unlabeled photos, not by reading what the business sells.
The pattern usually starts with a demand letter, sometimes with a complaint filed directly. It alleges that a visitor using a screen reader or a keyboard alone could not get past some part of the site: the search filters, an age or location interstitial, a contact form. Whether that visitor ever tried to place an order or message an advertiser is often beside the point in the courts most willing to hear these cases; encountering the barrier while browsing is treated as enough of an injury to sue over.
What follows is what the 2025 numbers actually say, why the state a plaintiff files in decides more than the code does, what specifically gets flagged on a listings heavy site, and what a Missouri law taking effect this year reveals about who is filing these cases and why a fast response works even where that law does not reach.
How big this actually got in 2025
The 3,117 federal filings in 2025 were not a one-off spike. They made up 36% of every ADA Title III lawsuit filed in federal court that year (3,117 of 8,667 total), up from 28% the year before, and they landed close to 2022's prior high of 3,255 after two years of decline. Read as a five year line, 2025 is a return to a level the country had already lived through once, not a new phenomenon business owners can wait out.
Where those suits landed varied enormously by state. New York federal courts led with 1,021. Florida was a close second at 961, nearly double its 2024 total. Illinois followed with 585. Missouri, Massachusetts, Wisconsin, and Indiana each saw filings in the dozens to high hundreds. California's federal courts saw four.
That last number is not a typo, and it is the key to understanding the whole picture: geography, not the content of the site, is doing almost all the work in deciding who gets sued.
One more mechanic matters before any of that: a private plaintiff suing under Title III of the ADA cannot recover money damages for themselves. The remedy the law provides is an order requiring the business to fix the problem, plus the plaintiff's attorney's fees and costs if the case succeeds or settles in their favor. There is no payout to the person who sued. That single rule explains why these cases are priced and negotiated the way they are: the entire economic value of a claim runs through legal fees, which means the cost climbs with every week a business waits to respond, and the cheapest moment to resolve one is always the moment it arrives, not the moment a complaint gets filed.
Why the map matters more than the code
The legal idea behind that state by state gap traces back to Robles v. Domino's Pizza, a 2018 Ninth Circuit ruling the Supreme Court later declined to review. The court held that Domino's website and app were covered by the ADA because of their connection, commonly called a nexus, to the company's physical restaurants: customers used the site to order food they would eat at a real, physical place of business the ADA already covered.
Some courts took that nexus idea and ran it the other direction. If a website has no connection to any physical location open to the public, several California appellate rulings and its federal courts have held, then it is not a place of public accommodation at all, and Title III simply does not reach it. That is the exact reasoning behind California's four filings in a year when the rest of the country saw thousands: an online only business with no storefront anywhere is close to untouchable there.
New York's federal courts went the other way. Most judges there have held that Title III covers a commercial website whether or not it connects to any physical address, and that reading is a large part of why 1,021 of 2025's filings landed in New York alone. It is not unanimous or settled for good: a Southern District of New York chief judge broke from that position in 2025, so the consensus behind New York's numbers has started to crack rather than harden into permanent law.
A classifieds directory is close to the textbook case the nexus question was written for: an online only marketplace with no physical premises a visitor could ever walk into. Where the company is incorporated, or where its servers sit, changes nothing about this; what decides exposure is which state's courts a plaintiff's firm picks, and firms pick based on which circuit's case law favors them, not where the defendant happens to be based. A firm representing a New York resident can sue a directory with no New York office at all and, under the reading most federal judges there have applied, still argue successfully that the site is covered. Unlike the mainstream infrastructure that treats this business differently on purpose, an app store that rejects the category outright or a bank that closes the account on sight, this exposure does not discriminate by industry. It reaches a listings marketplace the same way it reaches a shoe retailer, and only the court deciding the case changes that.
What actually gets picked apart on a listings heavy site
Photos are the first thing a review targets, because a directory publishes far more of them than most commercial sites do. Every listing photo without a written text alternative is not one violation but one multiplied by however many unlabeled images the site is running at the time of the complaint, which on a live directory can run into the thousands.
An age or location gate is close to universal on this business's homepage, and it is exactly the kind of custom interface that trips the most common technical defect in these complaints. A gate built only for a mouse click, one that never returns keyboard focus to the right place once it closes or that traps a keyboard user inside it with no way out, is the textbook keyboard navigation failure reviewers are trained to look for first.
Search and filter controls, the location, category, and price dropdowns that make a directory usable at all, are frequently built as custom widgets rather than native form elements, and custom widgets are exactly what goes unlabeled for a screen reader user unless someone deliberately adds the missing role and name. The same applies to any contact, inquiry, or account signup form: a field with no visible or programmatic label, and no way for a screen reader to hear that a required field was left blank, is one of the most frequently cited defects in filed complaints.
None of this is a mystery a business has to guess at. The Department of Justice's own guidance on web accessibility lists the same handful of barriers as the baseline any business should check for: poor color contrast, information conveyed by color alone, images without text alternatives, videos without captions, and forms without labels or error messages a screen reader can announce. The Department has never issued a specific technical regulation for Title III websites, and instead points businesses toward the Web Content Accessibility Guidelines and the federal Section 508 Standards as the benchmarks to build toward.
Treating this as a one time redesign misses where the defects actually come from: new listings, submitted every day, each with photos nobody has described. The same intake step that already runs a submitted photo past a moderation check before a listing goes live is the natural place to also require a short written description of it, because alt text written the moment a photo is uploaded costs almost nothing next to what it costs to retrofit years of an existing listings database after a demand letter arrives.
The Missouri experiment, and what it says about who is actually filing
Missouri drew 86 of 2025's federal filings, sixth most in the country. A closer look at the docket found something sharper: one plaintiff, represented by a single law firm, was responsible for every one of the 121 website accessibility lawsuits filed in Missouri across 2024 and 2025 combined. It did not take a movement or an industry campaign. It took one motivated plaintiff and one firm running the same complaint template state by state, which the fee only remedy above makes a workable business model on its own.
Missouri responded with a law that becomes operative on August 28, 2026. It lets a Missouri resident sued in one of these cases, and separately the state's attorney general, petition a court to declare the underlying lawsuit abusive litigation, weighing factors like whether the same plaintiff or firm has filed many similar suits without real attempts to resolve them. The law sets a specific safe harbor: if the defendant received written notice of the alleged barrier and began a genuine, substantial effort to fix it within 90 days, the litigation is presumed abusive unless the plaintiff can show otherwise. Kansas passed a similar law back in 2023; no lawsuit appears to have tested it yet, likely because Kansas drew little of this litigation even before the law existed.
The practical lesson holds regardless of which state a directory operates from. The 90 day window Missouri just wrote into statute describes almost exactly what defense lawyers already recommend doing the moment any demand letter arrives, anywhere: acknowledge the specific complaint, start fixing it without delay, and keep a dated record of what changed and when. That posture is what turns a demand letter into a closed matter instead of a filed lawsuit, whether or not the particular law rewarding it has reached the state where a directory happens to get sued from.
What actually reduces exposure
Do not treat an accessibility overlay or widget as the fix. Tools that promise compliance through a single script tag catch what an automated scanner catches; they do nothing about a keyboard trap on an interstitial or a missing label on a filter dropdown, which are exactly the manual defects that keep showing up in filed complaints against sites already running one.
Get an actual audit against WCAG 2.1 AA, and insist it includes someone testing the site keyboard only and with a screen reader, not just an automated scan. Automated tools catch missing alt text and contrast failures reliably; they miss keyboard traps and broken focus order almost entirely, and those are the defects that turn a demand letter into a filed complaint.
Fix the age or location interstitial first, since it is the one element every visitor hits before seeing anything else: proper keyboard operability for its own controls, a focus trap only while it is open, and focus returned to the right place the moment it closes.
Push alt text into the listing submission pipeline itself, as a required field alongside the photo, rather than a backlog to clear once. The cost difference between writing it at upload time and retrofitting it across an existing database later is the difference between a small process change and a project.
If a demand letter arrives, do not respond alone and do not pay the first number asked. Get a lawyer who specifically defends ADA Title III website cases rather than general counsel; both sides of these cases work from a well worn playbook, and a lawyer who has seen it before negotiates from a different position than one seeing it for the first time.
Keep a dated log of every fix starting the day a complaint arrives. It is the one thing that helps in every state a directory could be sued from, and it is the exact thing Missouri's new law now rewards by name.
