Why Real Estate Agent Websites Get ADA Lawsuits (And How to Lower Your Risk)

If you are a real estate agent or run a small brokerage, your website is probably one of the most litigated types of site on the internet — and most agents have no idea. Property listing sites show up again and again in the annual tallies of ADA website accessibility lawsuits, right alongside retail and restaurants. The reason is not that real estate agents are careless. It is that a property website is built out of exactly the features that tend to fail accessibility tests: image-heavy listings, interactive maps, photo galleries, search filters, and contact forms. Put those together and you have a site that a blind or motor-impaired visitor often cannot use — which, under the Americans with Disabilities Act, can be treated as a barrier to a place of business.

This guide is written for the agent, not the developer. You do not need to know how to code to understand where the risk comes from or to have an informed conversation with whoever built your site. Let’s walk through why real estate sites attract complaints, which features cause the most trouble, and the practical steps that lower your exposure.

Why real estate sites are such a common target

There are a few things that make property websites stand out to the law firms that file these cases.

They are public accommodations. Courts have widely treated the websites of businesses that serve the public — including real estate brokerages — as covered by ADA Title III. If your site lets someone browse listings, request a showing, or contact an agent, it is doing the work of your business, and it is expected to be usable by people with disabilities.

They are visual by nature. Real estate is sold with photos. A listing is dozens of images, a floor plan, a neighborhood map, maybe a virtual tour. Every one of those is a place where information can be locked away from someone who cannot see it. A screen reader — the software a blind person uses to have the page read aloud — cannot describe a photo unless someone has written a text description for it.

They reuse the same templates. Many agents build on the same handful of platforms, IDX plugins, and listing widgets. When one of those has an accessibility flaw, it exists on thousands of sites at once, and a single law firm can send near-identical demand letters to all of them. This is why these cases so often arrive in waves.

The demand letter is cheap to send. Most of these matters never see a courtroom. A firm runs an automated scan, finds violations, and sends a letter demanding a settlement — often in the low five figures — to make the complaint go away. Settling is frequently cheaper than fighting, which is exactly why the letters keep coming.

The features on your site that create the most risk

Not every part of your website carries equal legal weight. These are the pieces that show up most often in real estate accessibility complaints.

Property photos without descriptions

Every listing photo needs a short text description — called “alt text” — so that a screen reader can tell a blind visitor what the image shows. On most real estate sites, photos are uploaded straight from the MLS with filenames like IMG_4821.jpg and no description at all. To a screen reader user, an entire gallery of a home can come across as “image, image, image” with no information about the kitchen, the yard, or the view. This is the single most common failure on property sites, and it is directly tied to WCAG 1.1.1, the most-cited accessibility rule in demand letters.

You do not need to describe every photo in exhaustive detail. A short, useful line — “Renovated kitchen with white cabinets and a large island” — is far better than nothing. Floor plans and infographics need a bit more: a text summary of the key information, because the plan itself is unreadable to a screen reader.

Interactive map searches

The “search by map” feature that lets buyers drag around a neighborhood and click pins is one of the hardest things on any website to make accessible. These maps are usually operated by mouse — click, drag, zoom — and a person who navigates with only a keyboard often cannot use them at all. If the only way to browse listings in an area is through that map, you have effectively locked out anyone who cannot use a mouse.

The fix is not to remove the map. It is to make sure there is always another way to get the same result: a text-based list of listings, filters for city, price, and bedrooms, and a plain results page that works with a keyboard. The map can stay as a nice-to-have; it just cannot be the only door in.

Photo galleries and virtual tours

Slideshows, lightboxes, and carousels are notorious for accessibility problems. Common failures include galleries that a keyboard user cannot advance, “next” and “close” buttons that a screen reader announces as unlabeled, and auto-advancing slideshows that move faster than someone can read. Virtual tours and embedded 3D walkthroughs are often completely inaccessible and need an alternative — even something as simple as a written description of the layout and a set of captioned still photos.

Search filters and forms

The filters buyers use to narrow listings — price range, bedrooms, property type — are form controls, and form controls need clear labels that a screen reader can read. A slider with no label, or a dropdown that only makes sense next to a visual icon, leaves assistive-technology users guessing. The same goes for your contact and showing-request forms: every field needs a visible, properly connected label, and error messages (“please enter a valid phone number”) need to be announced, not just shown in red.

Forms are worth extra attention because they are where the transaction happens. A photo a blind user cannot see is a frustration; a contact form they cannot submit is a lost client and a much stronger legal claim.

Color and contrast

Real estate branding leans on light grays, gold accents, and thin fonts. Pale gray text on a white background may look elegant, but if the contrast is too low, people with low vision — a large and growing group as the population ages — cannot read it. Price tags, “new listing” badges, and call-to-action buttons are the usual offenders. There are free tools that check contrast in seconds, and this is one of the easiest categories of problem to fix.

What you can actually do about it

Here is the reassuring part: you do not have to become an accessibility expert, and you do not have to rebuild your site from scratch. A handful of concrete steps meaningfully lower your risk.

1. Run a quick check yourself. Free tools like WAVE or the built-in Lighthouse report in the Chrome browser will scan a page and flag obvious problems in a couple of minutes. They will not catch everything — no automated tool does — but they will show you the biggest issues on your busiest pages: the home page, a listing page, and your search results.

2. Fix alt text on your key images first. You will not caption ten thousand MLS photos overnight, but you can make sure the images on your most-visited pages have descriptions, and you can build the habit of adding a one-line description whenever you upload new photos. Ask your platform or IDX provider whether alt text can be pulled from listing data automatically — many can.

3. Make sure there is a non-map way to search. Confirm that a visitor can find listings using text filters and a results list, not only by dragging a map. If the map is the only option, that is the first thing to raise with your web person.

4. Test with your keyboard. Unplug your mouse, or just set it aside, and try to use your own site with the Tab key and Enter. Can you reach every listing, open a photo gallery, and submit the contact form? If you get stuck, so does every keyboard and screen reader user. This five-minute test surfaces a surprising number of real problems.

5. Talk to whoever built your site — with specifics. Whether it is a freelancer, an agency, or a platform like a real estate CRM, you now know the vocabulary: alt text, keyboard access, form labels, color contrast, an accessible alternative to the map. Ask them directly whether the site meets WCAG 2.1 AA — the standard nearly every settlement and regulation points to. A vague “our platform is accessible” is not an answer; ask what has actually been tested.

6. Publish an accessibility statement, and mean it. A short page that says you are committed to accessibility, describes what you have done, and gives visitors a way to report problems and request help does two things: it gives someone who hits a barrier a path other than a lawyer, and it demonstrates good faith. It is not a magic shield — a statement on top of an unusable site can actually hurt you — but paired with real fixes, it matters.

A word on overlay widgets

You will likely be pitched an “accessibility widget” — a line of code that promises to make your site compliant automatically, often with a little accessibility icon in the corner. Be skeptical. These overlays do not fix the underlying problems in your listings, maps, and forms, and a growing number of ADA lawsuits have been filed against sites that were running one. They can create a false sense of security while the real barriers remain. Your money is better spent on actual fixes to the content and structure of your site.

The bottom line

Real estate websites get sued because they are visual, interactive, and built on shared templates — a combination that produces exactly the barriers accessibility law is written to remove. But the same features that create the risk are ones you can improve without a full rebuild: describe your images, make sure listings can be found without a map, label your forms, check your contrast, and test with a keyboard. None of that requires you to write code. It requires you to know what to look for and to ask the right questions of the people who maintain your site.

Accessibility is also, quietly, good business. Older buyers, people browsing on phones in bright sunlight, and anyone using assistive technology are all real clients who bounce off a site they cannot use. Fixing these issues does not just lower your legal exposure — it widens the pool of people who can actually work with you.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.