Real Estate Website ADA Compliance: The Real Numbers

If you run a brokerage, you have probably been emailed a frightening number about real estate website ADA compliance. Here is the first thing to know about that number: whoever sent it is almost certainly selling accessibility services, and there is no neutral figure anywhere to check it against.

We went looking for one. There are four different totals in circulation for 2025 website accessibility lawsuits, running from 3,117 to more than 5,000. Every single one was published by a defense law firm or a remediation vendor. No court system, government agency or nonprofit publishes a count. One tracker disagrees with itself across three of its own documents. And in the only tracker that breaks filings out by industry, real estate sits below one percent.

We also found that we had published one of those numbers incorrectly ourselves. That correction is in this article, because a blog that argues about sourcing should show its own.

The four numbers, and why they disagree

They are not four measurements of the same thing. They are four different populations, and once you line up the methodologies most of the gap explains itself.

Seyfarth's 3,117 is the smallest because it is the narrowest: federal courts only. Seyfarth also reports that this was 36% of all 8,667 ADA Title III federal filings in 2025, up from 28% the year before. EcomBack adds state courts and gets 3,948. UsableNet adds mobile apps and video content on top of that and passes 5,000.

So far, so reconcilable. Then there is the last row.

One tracker, three documents, three answers

UsableNet's 2025 year-end PDF states that it "reviewed more than 5,000 ADA-related digital accessibility lawsuits filed in federal and state courts," and its own chart gives the components: 3,195 federal (62%) and 1,919 state, New York and California (38%). Those add to 5,114.

UsableNet's live lawsuit tracker page, on the same domain, says something else: "By the end of 2025, plaintiffs filed 4,928 web accessibility lawsuits." That page describes its scope in the same terms, "lawsuits filed in state courts in New York, California, and federal courts," so the difference is not a scope difference. It is a 186-case gap between two documents published by one company about one year, with no note anywhere explaining it.

One more detail worth having. The PDF's own methodology says the data covers "January 1, 2025, to Dec 15, 2025." The year-end report stops sixteen days before the year ends.

None of this makes UsableNet dishonest. It makes the numbers softer than they look when they arrive in your inbox as a single confident figure.

We got one of these wrong, and here is the correction

In our post on advisory website best practices we wrote that one tracker "recorded 4,605 federal filings, up 12% year over year" in 2025.

That is wrong twice over.

4,605 is UsableNet's 2023 total, not its 2025 total. Its 2023 year-end report says it plainly: "Plaintiffs filed 3,086 lawsuits across all federal courts and 1,519 lawsuits in state courts... When combining state and federal cases, plaintiffs filed 4,605 lawsuits in 2023." And because it combines federal and state, it was never a count of federal filings either.

The figure reached us the way these figures reach everyone: through content sites recirculating a two-year-old number with a current year attached to it. We have corrected the post. The lesson is the one worth taking away from this whole article, which is that a statistic with no year attached to its primary source is a statistic waiting to be wrong, and this market is full of them.

For what it is worth, the other number we published, that some compilations put 2025 above 5,000, turned out to be right and traces to UsableNet's own report.

Nobody independent counts this at all

This is the finding that reframes everything above, and it took two research passes to be confident of it.

There is no government or nonprofit count of website accessibility lawsuits. The infrastructure to produce one exists: CourtListener's RECAP archive mirrors federal dockets, the Administrative Office of the US Courts publishes caseload tables, and the Federal Judicial Center maintains an integrated database of federal civil filings. But none of them publishes a web-accessibility-specific figure, because the federal nature-of-suit code these cases fall under is "Other Civil Rights," which sweeps in a great deal that has nothing to do with websites.

So every headline number in this market, including all four above, rests on a private company's proprietary judgment about which complaints count. Those judgments are not published. You cannot audit them. And the companies making them sell the remedy.

That is not a conspiracy. It is just the shape of the evidence, and it is worth knowing before you act on a number.

What real estate website ADA compliance actually requires

There is no federal technical standard for private commercial websites. The Department of Justice says this on its own site: it "does not have a regulation setting out detailed standards," and "businesses and state and local governments can currently choose how they will ensure that the programs, services, and goods they provide online are accessible." The general duty not to discriminate still applies. The technical rule does not exist.

The rule that does exist does not apply to you. DOJ's 2024 Title II rule sets WCAG 2.1 Level AA as a binding standard for state and local government. It has also just slipped. An interim final rule published on April 20, 2026 moved the deadlines to April 26, 2027 for public entities of 50,000 or more, and April 26, 2028 for smaller entities and special districts. A brokerage is a private business and is covered by neither date.

In practice, courts and settlements use WCAG 2.1 Level AA. WCAG 2.2 has been the W3C's finalized recommendation since December 2024 and is backward compatible, so building to 2.2 covers you either way. WCAG 3.0 is still an incomplete draft and will not supersede 2.x for years.

The circuit split rests on insurance and a vending machine

Whether a website with no physical store attached is even covered by Title III depends on where you are sued, and the cases that decide it are stranger than the debate suggests.

The First Circuit's authority is Carparts (1994), about a self-funded medical reimbursement plan. The Third Circuit's is Ford v. Schering-Plough (1998) and the Sixth's is Parker v. MetLife (1997), both about insurance benefits obtained through an employer. The Fifth Circuit's is Magee v. Coca-Cola (2016), about whether a vending machine is a place of public accommodation. The Ninth Circuit's is Weyer v. Twentieth Century Fox (2000), insurance again, holding Title III applies to businesses with "a connection to a physical place." The Seventh Circuit's is Doe v. Mutual of Omaha (1999), which is the outlier because it actually mentions the internet, referring to "a facility (whether in physical space or in electronic space)."

The Eleventh Circuit tried to settle it in 2021 in Gil v. Winn-Dixie, holding websites are not places of public accommodation without a physical nexus. Then it vacated its own opinion on mootness grounds in December 2021. That vacatur still stands, so the circuit has no controlling rule.

So the law governing your listing search is largely being extrapolated from disputes about health insurance policies and a Coke machine, decided before most brokerages had a website. Nobody has resolved it since.

Real estate is below one percent

UsableNet is the only tracker we found that publishes an industry breakdown including real estate. Its 2025 table:

EcomBack's industry table does not list real estate at all. Seyfarth publishes state and law-firm breakdowns but no industry table.

Documented cases naming a brokerage do exist, and they are rare enough to be worth stating precisely. After two research passes the one docket we located is Robins v. Ashford Green at Aberdeen Association Inc., No. 9:24-cv-81212, filed in the Southern District of Florida on October 1, 2024, which names a real estate brokerage and a realtor professional association among its defendants alongside a homeowners association, with an ADA count. We read that docket through commercial aggregators rather than from the court's own system, and we could not confirm from a primary source whether the website was the barrier at issue, so treat it as evidence that these cases exist rather than as a decided precedent.

What we did not find, after looking specifically, is any settlement, consent decree or DOJ action involving an MLS, an IDX vendor or a listing portal.

Overlay widgets are not a defense, and there is a $1M order saying so

If a vendor has offered you a script that makes your site compliant overnight, the Federal Trade Commission has already looked at that claim.

In its matter against accessiBe Inc. and accessiBe Ltd. (FTC File No. 2223156), the Commission alleged the company "misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with the Web Content Accessibility Guidelines." The complaint was announced January 3, 2025 and the final order, requiring $1 million, was approved April 22, 2025. The order bars the company from claiming its automated product can make any website WCAG compliant without evidence. The FTC also alleged it had disguised paid reviews as independent ones.

The litigation data points the same way. EcomBack recorded 983 of its 3,948 lawsuits, 24.9%, against sites that already had an accessibility widget installed, up from 22.65% the year before. UsableNet's tracker reported that in July 2026, 113 of 401 defendants were sued while using a third-party accessibility widget. Both are vendors with an interest in that conclusion, which is worth saying. It is also the only data there is, and it points one way.

The question nobody can answer: your IDX widget

Here is the thing a brokerage most needs to know, and the honest answer is that it is unresolved.

The listing search on most brokerage sites is an embedded third-party IDX component. You did not write it, you cannot fix it, and you may not even be able to inspect it. So who is liable if it is inaccessible?

We found no court decision, no DOJ guidance, no settlement and no consent decree addressing embedded third-party component liability under Title III. Several vendors assert that courts consistently hold the site owner rather than the widget vendor responsible. Not one of them cited a case for it, and we could not find one.

The nearest authority runs the same direction without being binding. DOJ's Title II rule says a public entity cannot rely on the third-party-content exception for "embedded content provided by the public entity, directly or through contractual, licensing, or other arrangements." That is a rule for governments, not for you. But the practical logic holds: the visitor experienced the barrier on your domain, and you are the one who gets served.

Plan on being responsible for everything that renders on your site, and ask your IDX vendor for its accessibility conformance report before you sign. Just know that anyone telling you the law is settled here has not read it.

What we would actually do about it

Build to WCAG 2.1 AA during the build, where it is close to free, rather than remediating later, where it is not. That means sufficient color contrast, full keyboard navigation, real alt text on listing photos, labeled form fields, one honest heading structure per page, and visible focus states.

We could not find a single disinterested figure for what any of that costs. Every estimate we located, from roughly $5,000 for a handful of pages up to six figures a year, came from a company selling remediation or monitoring. So we will not quote one at you either, beyond our own: it is part of the build, and the cost of a brokerage website is where our pricing is set out in the open.

Do not buy an overlay. Do not act on a number in a cold email without asking who published it and for what year. And if you are still deciding what your site must legally carry, the state advertising rules are a much more likely source of trouble for a new brokerage than the ADA is.

One state just made these suits harder to bring

Missouri enacted the Act Against Abusive Website Access Litigation, codified at section 537.1250 RSMo, through HCS SS SCS Senate Bills 907, 1154 and 1272, effective August 28, 2026.

It creates a rebuttable presumption that a claim is abusive where a defendant "receives written notice of an alleged website or web content access violation and in good faith initiates substantial steps to correct it within ninety days." A court may order the plaintiff and the plaintiff's attorneys to pay the defendant's costs, plus punitive damages or sanctions of up to three times the attorney's fees awarded. The Attorney General may bring or intervene in these actions.

The most interesting provision is the sunset. If the Justice Department ever issues website accessibility standards under the ADA, the act expires with respect to entities registered as corporations with the Secretary of State and to the state and its political subdivisions. Missouri has written a law designed to switch itself off the day the federal rule that does not exist finally arrives.

No other state was confirmed to have enacted a comparable statute. California has two proposals in play and neither is law.

How we checked this

Two structured research passes plus direct retrieval. Lawsuit totals and industry tables were extracted from the trackers' own PDF reports rather than from coverage of them. DOJ positions and Title II compliance dates are quoted from ada.gov. The FTC matter is from ftc.gov. The Missouri act is from the Missouri Senate's own bill record, after a first pass misidentified the vehicle as a House bill that never became law in that form. Statutes are from the legislatures' own sites. Everything was read on September 3, 2026.

What we could not do: query a federal docket system directly, so every count in this article remains a private tracker's number and is labeled as such. We could not corroborate the Florida case from the court's own system. We found no credible current estimate of pre-suit demand letter volume, and no study with a disclosed sample showing what share of these cases settle, are dismissed, or reach judgment. Those are absences in the public record, not gaps we chose to leave.

If you want the accessibility work done during the build rather than after a letter arrives, tell us about your brokerage. If you would rather see pricing first, build your package in about two minutes.