All industries » Real estate brokerage website accessibility

Real estate brokerage website accessibility: IDX, MLS feeds, listing galleries, inquiry forms

Real estate brokerage sites are subject to ADA Title III. Plaintiff-side firms have filed steady volume against brokerages because the structural pattern is consistent: an IDX or MLS feed pulled into the site as an iframe, hundreds or thousands of listing pages with photo galleries, mortgage and tour-request forms, and agent bio pages. The IDX vendor is usually a third party (kvCORE, Sierra Interactive, BoomTown, IDX Broker, Real Geeks, Showcase IDX, Placester, others), but the brokerage is the responsible party for what visitors experience on its domain. Site Brace audits any brokerage site for $149 flat.

The rules that apply to brokerages

ADA Title III

Brokerage websites are public-accommodation services covered by Title III. The 9th Circuit decision in Robles v. Domino's Pizza is the canonical authority that a customer-facing website is part of the public accommodation, and it has been applied in real estate cases across multiple circuits. The National Association of Realtors has issued informational guidance on web accessibility but has no enforcement authority; the federal cause of action is independent of NAR membership status.

State human-rights laws

Brokerages are subject to state-law equivalents of ADA Title III. California's Unruh Civil Rights Act provides statutory damages of $4,000 per violation; brokerages with California listings or California-facing inquiry forms have exposure under the Unruh Act independent of federal Title III. New York, Illinois, and several other states have analogous statutes. See the state Title II guides for the public-entity dynamics, though brokerages fall on the Title III side.

Fair Housing Act overlap

The federal Fair Housing Act prohibits disability discrimination in housing. HUD has historically applied the FHA to advertising and listing practices but has not issued formal web-accessibility rules under the FHA. For now the ADA Title III rule and state human-rights laws are the load-bearing requirements.

The high-risk surfaces specific to brokerage sites

IDX and MLS feed iframes

Most brokerage sites pull listings from the local MLS through an IDX vendor. The IDX widget is typically an iframe embedded on a "Search" or "Listings" page; some vendors render listings server-side, but iframe embeds remain common. The most frequent failures: the iframe has no title attribute (axe-core frame-title), the search controls inside the iframe have no keyboard support, the map view lacks an accessible alternative for non-sighted users, and the filter pills are buttons without accessible names. The brokerage is the responsible party even when the underlying widget is third-party. Vendor support for accessibility varies; kvCORE and Sierra Interactive have made improvements, IDX Broker and Real Geeks have been slower to address, and customizing a vendor's widget often requires their support team rather than the brokerage's web developer.

Listing photo galleries

Each listing page typically carries 20 to 40 photos. The gallery widget is the highest-interaction element on the page and the most-frequent place keyboard focus gets trapped. Common patterns that fail: the gallery opens in a Lightbox modal where Tab moves focus outside the visible photos, the previous and next buttons have no accessible name (icon-only), the close button is unreachable by keyboard, and photo alt text defaults to the filename or to a generic "listing photo 1 of 30" pattern that conveys no actual content. Replacement alt text should describe the visible content (kitchen, primary suite, backyard pool) so a screen reader user can navigate the listing.

Inquiry forms

"Request more info," "Schedule a tour," and "Get pre-qualified" forms are present on every listing page and most of the supporting pages. They collect contact information, listing identifier, optional financing details, and sometimes Social Security number on the pre-qual variant. Many are built in the IDX vendor's form builder, which styles placeholder text as the label and leaves <label> elements off the input. Screen-reader users cannot determine what each field expects.

Agent bio pages

Independent brokerages and individual agents within larger firms each have a bio page. The agent headshot frequently has filename-style alt text ("john-smith-realtor.jpg"). The bio page often includes a "Contact this agent" form with the same labeling issues as the inquiry forms.

Embedded Google Maps

Listing pages and the "Communities" or "Neighborhoods" pages frequently embed Google Maps in iframes. The iframe usually has no accessible name, and the interior map is not navigable by keyboard.

What we typically find on a brokerage site

Notes on IDX platforms

kvCORE and Sierra Interactive

The two leading platforms for mid-size and larger brokerages. Both have iterated on accessibility but still ship templates with platform-level issues. Per-brokerage customization is limited; the vendor's roadmap drives most fixes.

IDX Broker, Real Geeks, BoomTown, Placester, Showcase IDX

Common platforms at independent brokerages and individual agents. Accessibility varies by platform and by template version. A site running an older theme on any of these platforms is likely to have several platform-level findings before per-page issues are even counted.

Custom WordPress with IDX plugin

Smaller brokerages often run custom WordPress with an IDX Broker or Showcase IDX plugin. The brokerage controls everything outside the plugin but is dependent on the plugin vendor for the listings surface itself. WordPress accessibility plugins often add aria-label on generic elements (the aria-prohibited-attr failure).

Why overlays are a poor fit for brokerages

Accessibility overlays are heavily marketed to brokerages because the perceived problem (a lot of pages, an iframe nobody controls) sounds like the overlay's pitch. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For brokerages specifically:

• Overlays cannot reach inside the IDX iframe; the listings surface (the largest part of the site) is untouched.
• Listing photo galleries with focus traps are inside the listing iframe in many platforms; the overlay cannot intercept the keyboard event chain.
• The FTC's April 2025 settlement with accessiBe ($1 million) makes overlay compliance claims a documented liability the brokerage cannot delegate to the vendor.

How Site Brace audits a brokerage site

The standard page mix for a brokerage audit:

• Homepage
• Listings or Search page (where the IDX widget loads)
• 3 to 5 listing detail pages of different property types (single-family, condo, land, luxury, recent reduction)
• Agent roster page
• Individual agent bio pages (top 4 to 6 agents by listing count)
• Communities or Neighborhoods page
• Buying and Selling resource pages
• Mortgage pre-qualification page
• Contact and office locations
• Accessibility statement (if one exists)

That mix covers up to 25 pages for a small or mid-size brokerage. The audit runs axe-core 4.10 against each page, captures element-level screenshots of every contrast failure, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.

Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional ecommerce site. The findings shape (photo alt, color contrast, form labels, iframe titles) is the same shape brokerage audits surface.

Start a brokerage site audit, $149

Related:

• E-commerce accessibility audit - the photo gallery and inquiry form patterns overlap heavily
• Free single-page WCAG check
• Why accessibility overlays do not make sites WCAG-compliant
• axe-core vs WAVE vs Lighthouse
• aria-label on a div: why screen readers ignore it