Skip to content
wcagc
Create account
←Back to blog
ADAreal estateWCAG

ADA compliance for real estate and listing websites

How the ADA applies to real estate websites: brokerages, IDX listing feeds, map search and filters, and which WCAG criteria listing sites fail.

P

Pavel Charkasau

ADA compliance for a real estate website means a buyer or renter using a screen reader, a keyboard, or magnification can search listings, read them, and contact an agent the same way everyone else can. Real estate offices are not named in Title III's list of public accommodations, but the list ends with "or other service establishment" (42 U.S.C. § 12181(7)(F)), and a brokerage that serves the public fits that phrase. The Justice Department's position is that businesses open to the public must make the goods and services they offer online accessible, while admitting it "does not have a regulation setting out detailed standards" for private websites (ADA.gov, March 18, 2022).

So the working target is WCAG 2.2 Level AA, applied to the parts of the site people actually use: the search form, the map, the filters, the listing page and the contact form. Those are also where listing sites tend to break. The rest of this post goes through the legal picture, the listing feed you don't control, and the specific WCAG failures I'd look for first. It is not legal advice.

Does the ADA apply to real estate websites?

For most brokerages, yes in practice, though the case law is less tidy than vendors suggest. Title III covers "places of public accommodation," and the statute's examples include travel services, insurance offices, and the office of an accountant or lawyer before closing with "other service establishment" (42 U.S.C. § 12181(7)(F)). A brokerage with an office that meets clients belongs in that group.

Whether the website itself is covered is less settled. The Supreme Court has never ruled on it, and the closest thing to a clean appellate answer was undone: the Eleventh Circuit held in April 2021, in Gil v. Winn-Dixie, that websites are not places of public accommodation, then vacated that opinion as moot on December 28, 2021 (Eleventh Circuit, No. 17-13467). The National Association of Realtors cited the April opinion in its own coverage of demand letters that spring and noted the question would stay open until the Justice Department or the Supreme Court acted (NAR, April 27, 2021). Our ADA overview and the post on whether the ADA applies to websites cover the split in more detail.

My view is that the jurisdiction question is the wrong place to spend your time. A home search is a service. If a blind buyer can't get past your filter panel, they go to another brokerage's site, and that happens whether or not a court ever hears about it.

What about the Fair Housing Act?

It is a separate law, and some demand letters to brokers have blurred the two. NAR's legal coverage calls Fair Housing Act claims about broker website accessibility "meritless and frivolous" and says "no court has ever concluded that the act requires a real estate broker to maintain an accessible website" (NAR, April 27, 2021). That article is five years old and archived, and NAR notes its content may not be current, so treat it as one association's reading. It is not a ruling.

The same article gives the advice I'd repeat: if a letter arrives, contact your insurance carrier and get legal counsel before you reply. Our guide to responding to an ADA demand letter covers the steps without the panic.

Are you responsible for the IDX listing feed you embed?

For what visitors see on your domain, mostly yes. Most brokerage sites pull listings from the local MLS through an IDX plugin, an iframe, or a vendor-hosted search page under your subdomain. You didn't write that code, but Title III covers discrimination carried out "directly, or through contractual, licensing, or other arrangements" (42 U.S.C. § 12182(b)(1)(A)(i)). To a visitor, the search on homes.yourbrokerage.com is your search.

In practice that turns into three jobs:

  • Ask your IDX vendor for an accessibility conformance report (a VPAT) for the search and listing templates, and read the "Partially Supports" rows. Our explainer on what a VPAT is shows how.
  • Test the vendor's pages yourself, because a report describes a product version and your configured theme may differ.
  • Put accessibility requirements and a fix timeline into the next contract renewal. Renewal is when the vendor is most likely to say yes.

Listing photos are a harder case. The MLS feed usually supplies images with no description at all, and the description you'd want ("open-plan kitchen, island with seating, step-down into living room") exists only in the agent's head. More on that below.

Which parts of a listing site usually fail WCAG?

Map search, filters and photo galleries, in roughly that order. These are the patterns I find again and again on listing templates, with the WCAG 2.2 criterion each one fails:

What you seeWhy it failsWCAG criterion
Map can only be panned by draggingNo single-pointer alternative such as arrow buttons2.5.7 Dragging Movements (AA)
Price pins are <div>s with click handlersKeyboard users can't reach or open them2.1.1 Keyboard (A)
"Min price" and "Beds" dropdowns built from styled <div>sNo accessible name, role or state for a screen reader4.1.2 Name, Role, Value (A)
Results update silently after a filter change"124 homes found" is never announced4.1.3 Status Messages (AA)
Photo carousel with alt="listing image" on every slideNothing describes what the photo shows1.1.1 Non-text Content (A)
Light grey price text on a photo overlayContrast below 4.5:1 for normal text1.4.3 Contrast (Minimum) (AA)

Two notes on that table. W3C's own example for 2.5.7 is a map: users can drag the view, and "the map has up/down/left/right buttons to move the view as well" (W3C Understanding 2.5.7). Many map setups I've tested ship zoom buttons and stop there. And W3C's example for 4.1.3 is a search that adds a message like "5 results returned" to the page (W3C Understanding 4.1.3). That is exactly what a listing filter does, so a role="status" region around the result count fixes it.

The map deserves one more sentence. Even with keyboard-operable pins, a map is a poor way to scan 124 results by ear. Pair it with a list view that shows the same results in the same order. Most listing templates already have one, so the job is making sure it is reachable and kept in sync when someone changes the filters.

How do you write alt text for listing photos?

Describe what a buyer would want to know from the photo, in one sentence. "Living room" is better than "image 3 of 24." "Living room with two large windows, wood floors and a fireplace on the far wall" is better still. If the listing description already says it, keep the alt short and don't repeat whole paragraphs.

Photos that show access-related features deserve the most care: a step-free entrance, a walk-in shower, a stair lift. A buyer who uses a wheelchair is looking for exactly those details, and right now they are often only in a photo. When the MLS sends images with no description, an agent typing a one-line caption at upload time is cheaper than anything you can do later. Our guide to writing good alt text has more examples.

Virtual tours and agent walkthrough videos need captions (WCAG 1.2.2) if they have speech. If a 3D tour has no keyboard controls, the listing photos and floor plan have to carry the same information.

What should a brokerage fix first?

Start where a visitor turns into a lead: the search form and the contact or showing-request form. A form whose fields have no labels or whose errors appear only in red text fails 1.3.1, 3.3.1 and 3.3.2, and those are among the "inaccessible online forms" the Justice Department lists as common barriers (ADA.gov). Our accessible forms guide walks through the fixes.

Then put the mouse away and try one realistic task with only the keyboard: set a price range, open the third result, and request a showing. Where you get stuck is your first engineering ticket. Our WCAG checklist lists the criteria to check along the way.

Be honest about what automation covers. Deque's study of more than 2,000 audits put automated detection at about 57% of issues by volume (Deque); counted by success criteria instead, the figure is closer to 30%. A scanner, ours included, will flag a filter dropdown with no accessible name or a photo with no alt attribute. It can't tell you whether "listing image" describes the photo, or whether the map makes sense to someone listening to it. Full conformance needs human review, ideally from someone who uses a screen reader every day.

If your organization is a public housing authority or another state or local government body, a different rule applies: Title II now requires WCAG 2.1 AA, with compliance dates moved to April 2027 and April 2028 (Federal Register, 91 FR 20902). Our post on the Title II deadline extension covers it.

FAQ

Does the ADA apply to real estate websites?

Generally yes for brokerages that serve the public, though courts disagree on the details. Title III covers "other service establishment[s]" (42 U.S.C. § 12181(7)(F)), and the Justice Department says businesses open to the public must make their online services accessible (ADA.gov).

Is there a WCAG level required for real estate websites?

No federal regulation names one for private businesses; the Justice Department says it "does not have a regulation setting out detailed standards" (ADA.gov). WCAG 2.2 Level AA is the sensible target, and content that conforms to 2.2 also conforms to 2.1 and 2.0 (W3C).

Is my brokerage responsible for an IDX plugin built by a vendor?

For the pages on your domain, plan as if you are. Title III covers discrimination "through contractual, licensing, or other arrangements" (42 U.S.C. § 12182(b)(1)(A)(i)), so ask the vendor for a conformance report and test their pages yourself.

Does the Fair Housing Act require an accessible broker website?

Not according to NAR, which wrote in 2021 that "no court has ever concluded" it does (NAR). That is an association's reading, not a ruling, so get counsel if a letter makes that claim.

Why does map search fail accessibility checks?

Because many maps can only be panned by dragging, and their price pins can't be reached by keyboard. WCAG 2.5.7 asks for a single-pointer alternative such as arrow buttons (W3C), and 2.1.1 requires keyboard access.

See which parts of your listing search fail, with the exact selectors, before you plan the fixes: run a free scan.

Written by Pavel Charkasau, founder of wcagc.com. I built the table above from the WCAG criteria themselves and from the patterns that keep showing up on listing templates.

Last updated: October 21, 2026

Sources