ADA Compliance for Real Estate Websites

Everything in this guide

4 pages, grouped by what you are trying to do.

What accessibility actually means on a real estate website

Strip away the legal vocabulary and the subject is narrow. Some people cannot use a mouse, so they move through a page with a keyboard, tabbing from link to link. Some people cannot see the screen, so software reads the page aloud in order and announces what each control does. Some people see the screen but cannot separate pale grey text from a white background. Accessibility is whether your site still works for those visitors.

On an agent website this gets specific fast. A photo of a kitchen with no text description is silence to a screen reader. A property search filter that only responds to a mouse click locks out a keyboard user. A contact form whose fields are labelled only by faint placeholder text inside the box announces nothing useful when read aloud, so the visitor hears an unnamed edit box and has no way to know what belongs in it.

That last example is the one worth sitting with, because it is where accessibility and lead capture turn out to be the same problem. A form a visitor cannot complete is a lost enquiry whether the reason is a disability or a confusing layout. Most of the work on this hub improves the site for everyone who uses it, which is the honest reason to do it before anyone sends a letter.

The legal position, stated accurately

This topic attracts a lot of confident writing that does not survive contact with the actual sources. Here is what can be verified.

The Americans with Disabilities Act does not mention websites. Congress passed it in 1990 and the statute addresses places of public accommodation. Whether that extends to a website has been worked out case by case, which is why the answer sounds unsatisfying: it depends on the court and on the facts.

The most cited decision is Robles v. Domino's Pizza, decided by the Ninth Circuit on 15 January 2019. The panel held the ADA applied to Domino's website and app because customers used them to locate a nearby restaurant and order food, and the opinion calls that nexus between the website and the physical restaurants critical to the analysis. The Supreme Court declined to review the decision in October 2019, which left it standing without endorsing it nationwide.

Two details from that opinion are routinely dropped by pages that cite it, and both cut against overstating the duty. The panel wrote that it need not decide whether the ADA covers websites where inaccessibility does not impede access to the goods and services of a physical location. And on WCAG specifically, the court treated conformance as a possible equitable remedy a court might order, while noting the plaintiff was not seeking to impose liability for failing to meet WCAG 2.0, which the opinion describes as private industry standards. So the accurate sentence is that a court may order WCAG conformance as a fix, not that the law commands it in advance.

The Department of Justice did publish a web accessibility rule adopting WCAG 2.1 Level AA. It binds state and local governments under Title II of the ADA, with compliance dates of April 26 2027 for larger entities and April 26 2028 for smaller ones and special districts, following an extension published in April 2026. A real estate agent is a private business under Title III, so this rule sets no deadline for you. It is worth knowing because it tells you which standard the federal government reaches for when it does write one down.

How often this actually reaches a courtroom

Numbers in this niche are unreliable in a specific direction, because the companies publishing them sell the fix. While researching this page we found a widely repeated figure of over 5,100 lawsuits and a 37% jump, sourced to accessibility vendors, that does not match the court data.

The figure that can be checked comes from Seyfarth Shaw, a law firm that counts federal dockets and publishes the tally. Its March 2026 report found 3,117 federal website accessibility lawsuits filed in 2025, an increase of 665 over the 2,452 filed in 2024, which is 27% growth. Those cases were 36% of all federal ADA Title III filings in 2025, up from 28% the year before.

Read that carefully, because it says something more useful than the raw count. Total Title III filings were roughly flat, 8,667 in 2025 against 8,800 in 2024, while the website share climbed by eight points. The activity is not simply growing, it is shifting from physical premises toward websites.

Two honest caveats. These are federal filings only, so state court cases and the far more common demand letter that settles quietly are not in the count. And nobody publishes a reliable breakdown by industry, so we cannot tell you how many named a real estate agent. Anyone who gives you that number without a docket source is estimating.

What actually fails, measured rather than guessed

WebAIM, an accessibility centre at Utah State University, runs an automated test across one million home pages every year and publishes the results. The February 2026 report detected WCAG failures on 95.9% of pages tested, up from 94.8% the year before, averaging 56.1 detected errors per page.

The valuable part is the concentration. Six error types account for 96% of everything found, and they are all mundane:

• Low contrast text, on 83.9% of pages. Pale grey body copy on white, usually a design choice nobody revisited.
• Missing alternative text on images, on 53.1%. On an agent site this is every listing photo and every headshot.
• Missing form input labels, on 51%. This is the contact form, the search box, and the valuation request.
• Empty links, on 46.3%. Usually an icon or a photo wrapped in a link with no text inside it.
• Empty buttons, on 30.6%. The same problem on a button, common for icon-only controls.
• Missing document language, on 13.5%. One attribute on the html element that tells a screen reader which language to pronounce.

Why real estate sites fail in their own particular way

The WebAIM list is the general web. Agent websites add a problem most industries do not have, and it sits on the most important page.

Listing data usually arrives through IDX, an embedded feed from the local board or MLS that displays properties on your site. You did not build that component, it renders through JavaScript after the page loads, and you frequently cannot edit its markup. So the single most valuable thing on your website, the listings, is the part you have the least control over.

There is a second consequence that has nothing to do with disability, and noticing it is the most useful thing on this page. Content that only exists after JavaScript runs is invisible to a screen reader and invisible to a text-only crawler. That is the same defect producing two different failures: a blind visitor cannot read your listings, and an AI assistant cannot cite them. The accessibility fix and the AI visibility fix are the same fix, which is why the IDX page in this hub links across to the AI search hub.

Map views have the same shape. An interactive map is genuinely hard to make accessible, and the standard answer is not to fix the map but to provide the same information another way, as a readable list of properties with addresses and prices in text.

The widget question, answered by the FTC

Search for a solution and you will be offered an overlay: one line of JavaScript that promises compliance in minutes. The appeal is obvious. It is also the most consequential mistake in this area, and unusually for an accessibility argument, there is an official ruling to point at rather than an opinion.

In April 2025 the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million. The FTC's complaint was that the company falsely claimed its accessWidget product could make any website compliant with WCAG when it did not, and separately that it formatted third-party articles and reviews to look like independent opinions while failing to disclose its connections to the reviewers. The order bars the company from claiming an automated product can make any website WCAG compliant without evidence to back it.

That is a federal regulator stating the central claim of the category was deceptive. It does not make every overlay worthless, and some vendors are more careful about what they promise. It does mean a widget is not a defence, and buying one does not end the question.

The mechanism explains why. An overlay runs in the visitor's browser after your page has loaded, and tries to guess what your markup meant. It can raise contrast. It cannot invent a caption describing your kitchen photo, because it does not know what is in the photograph. Fixing the markup fixes it for every visitor and every assistive tool. Guessing at it afterwards does neither reliably.

What to do, in the order worth doing it

The sequence matters, because the cheap checks tell you whether you have an expensive problem.

• Run a free automated scan, such as WAVE from WebAIM, on your home page, one listing page, and your contact page. It takes minutes and finds the contrast, alt text, and label problems that make up most of the list above.
• Understand the ceiling on that result. Automated tools detect a portion of issues and cannot judge whether your alt text is meaningful. A clean scan is a floor, not a certificate.
• Test with the keyboard yourself. Put the mouse aside and press Tab through your contact page. If you cannot reach and submit the form, or you cannot see which element is focused, you have found a real barrier without any tooling.
• Fix the contact form first. It is the highest-value page on the site, the fixes are small, and it is where an inaccessible site costs you an enquiry directly.
• Deal with images next, writing alt text that describes what is in the photograph rather than repeating the address.
• Then confront IDX. Ask your provider directly what accessibility testing their component has had, and get the answer in writing. This is a vendor question, not a you question.
• Publish an accessibility statement with a phone number and email, so someone who hits a barrier can reach a person. NAR recommends offering direct assistance to anyone unable to use services on the site, and it is the cheapest item here.
• Treat a widget as an interim comfort at best, never as the fix, for the reasons above.

Where a rebuild changes the answer

An honest scope note. Most of what is above can be done on your current website, and if your site is basically sound you should do exactly that rather than replacing it.

A rebuild changes the calculation when the problems are structural rather than cosmetic. Contrast and alt text are content edits on any platform. Missing form labels, empty buttons, headings used for visual size instead of document structure, and content that only exists after JavaScript runs are all decisions baked into the markup a template generated. On a platform that does not let you edit the markup, there is no content edit available.

That is the case where the same work resolves several problems at once, because readable structure is what a screen reader needs, what a search crawler needs, and what an AI assistant needs to quote you. Saige rebuilds the site with that structure in place, and the preview is free, so you can look at the result before any money is discussed. Whether you need one depends on what your scan and your keyboard test turn up, which is why both come first on the list above.

Frequently asked questions

Related reading from Plot

• Real Estate Agent Website Checklist: What to Check First
• Does IDX Actually Bring You Clients? An Honest Assessment
• What to Put on a Real Estate Contact Page (and What to Cut)

Sources

Every claim on this page that could be checked against a primary source is linked below. Where something is not publicly documented by a vendor, the page says so rather than filling the gap with an estimate.

• Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025 (Seyfarth Shaw LLP (published 25 March 2026))
• FTC Approves Final Order Requiring accessiBe to Pay $1 Million for Deceptive Claims (Federal Trade Commission (order approved 22 April 2025))
• Robles v. Domino's Pizza, LLC, No. 17-55504 (9th Cir. 2019) (US Court of Appeals for the Ninth Circuit (decided 15 January 2019))
• Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps (US Department of Justice, Civil Rights Division)
• The WebAIM Million: An annual accessibility analysis of the top 1,000,000 home pages (WebAIM, Utah State University (published February 2026))
• How to Meet WCAG 2.1 (Quick Reference) (World Wide Web Consortium (W3C))