IDX integrations pull live MLS listings into real estate websites through third-party plugins, iframes, or API feeds. These integrations often introduce accessibility issues the site owner did not create and cannot fully control. An audit covers IDX content as part of the site, which means the real estate company is responsible for WCAG conformance across listings, search filters, map views, and property detail pages.
The practical path is to evaluate the IDX integration alongside the rest of the site, document issues specific to the feed, and work with the IDX vendor on fixes while addressing what can be controlled locally.
| Area | What to Know |
|---|---|
| Responsibility | The website owner is responsible for IDX content under ADA and WCAG 2.1 AA. |
| Common Issues | Unlabeled search filters, inaccessible map views, missing image alt text, keyboard traps in listing carousels. |
| Audit Coverage | A manual audit evaluates IDX pages as part of the site, including listing search, detail pages, and saved search flows. |
| Vendor Role | IDX providers must make fixes to feed markup and widgets. Site owners address theme-level and integration code. |
| Scan Limitation | Automated scans only flag approximately 25% of issues and often miss IDX-specific problems tied to user flows. |
What is an IDX Integration?
IDX, short for Internet Data Exchange, is the standard that lets real estate websites display active MLS listings. Brokerages and agents integrate IDX through plugins (common on WordPress), embedded iframes, or direct API feeds that render listings inside the site’s theme.
The integration controls most of what a buyer interacts with: property search, filters, map results, listing cards, photo galleries, agent contact forms, and saved searches. If the IDX layer has accessibility issues, those issues affect the core function of the site.
Why IDX Content Counts Toward WCAG Conformance
Under the ADA and WCAG 2.1 AA, third-party content embedded into a site is treated as part of that site. Courts and the DOJ have consistently held businesses responsible for accessibility of content they display, regardless of where the code originates.
That means a brokerage cannot point to the IDX vendor and step away. If a user with a screen reader cannot filter listings by price or open a property detail page, the site itself has a WCAG conformance problem.
Common Accessibility Issues in IDX Integrations
A manual audit of a real estate site with IDX almost always identifies a recurring set of issues:
Unlabeled form controls in search filters, including price, bedrooms, and property type dropdowns.
Images without alt text on listing photos, or alt text auto-filled with the file name.
Map views that are not keyboard operable and have no accessible alternative for listing locations.
Photo carousels with keyboard traps or no visible focus indicator.
Color contrast issues on price tags, status labels, and call-to-action buttons.
Headings that skip levels or duplicate across listing cards, confusing screen reader navigation.
Dynamic content (load-more, infinite scroll) that does not announce new results to assistive technology.
Automated scans catch a portion of these, but many IDX issues only show up when an auditor moves through the actual search and browse flow with a keyboard or screen reader.
How an Audit Covers IDX Pages
A website accessibility audit from Accessible.org evaluates IDX-driven pages the same way it evaluates any other template. The auditor reviews listing search, map view, listing detail, photo gallery, agent contact, and saved search against WCAG 2.1 AA criteria.
The report identifies issues at the element level with location, severity, and recommended fix. IDX-specific issues get flagged so the brokerage knows which items to send to the vendor versus which belong to the theme or custom code.
This separation matters because remediation responsibility splits between parties. A clear audit report makes the handoff cleaner.
Who Fixes What?
Most IDX accessibility work divides into three categories:
Vendor responsibility: Widget markup, form labels inside iframes, photo carousel behavior, map controls, and anything served from the IDX provider’s codebase.
Site owner responsibility: Theme styles applied to IDX output, color contrast overrides, custom CSS, page headings, and surrounding navigation.
Shared: Listing image alt text, which often requires both the vendor to expose an alt field and the agent to populate it correctly when uploading photos.
Before signing with an IDX vendor, ask for their accessibility statement and whether they can provide an ACR. A VPAT-based ACR from the IDX provider gives real estate companies documentation of the vendor’s conformance posture.
The VPAT and ACR process is how software vendors document WCAG conformance for their customers. If an IDX provider has never produced one, that itself is a signal worth weighing.
How to Reduce Risk on a Real Estate Website with IDX
A practical sequence:
- Conduct a manual audit that covers IDX templates alongside the rest of the site.
- Sort issues by responsibility: vendor, site owner, or shared.
- Send vendor-side issues to the IDX provider with the audit excerpts attached.
- Address theme-level and content issues through your developer.
- Validate fixes with the auditor before claiming conformance.
- Publish an accessibility statement that acknowledges third-party content and a path to report issues.
Real estate has been a frequent target of ADA website lawsuits, and IDX-driven pages are where most claimed issues sit. Addressing them directly reduces legal exposure and makes the site usable for buyers who rely on assistive technology.
Frequently Asked Questions
Does our brokerage need an audit if our IDX vendor says they are accessible?
Yes. Vendor claims cover the widget in isolation, not how it renders inside your theme with your styles, headings, and surrounding content. A full-site audit is the only way to verify WCAG 2.1 AA conformance for what users actually see.
Can scans confirm IDX accessibility?
No. Scans only flag approximately 25% of issues and miss most problems tied to keyboard flow, screen reader output, and dynamic content behavior, which is where IDX issues concentrate.
What if the IDX vendor refuses to make fixes?
Document the request, address what you can control on your side, and weigh switching to a provider that takes accessibility seriously. An accessibility statement should note third-party limitations while showing good-faith effort on issues within your control.
Should we pick WCAG 2.1 AA or 2.2 AA for a real estate site?
WCAG 2.1 AA remains the most widely referenced standard in U.S. legal contexts, including ADA cases. Many real estate companies audit to 2.1 AA and add 2.2 AA criteria as a forward-looking step.
How often should a real estate site be re-audited?
After major theme changes, IDX vendor updates, or at minimum annually. Listings change daily, but the templates rendering them are what an audit evaluates.
IDX is the engine of most real estate websites, which makes it the engine of most accessibility issues on those sites. Treat it as part of the site, audit it accordingly, and split remediation work with your vendor based on clear documentation.
Contact Accessible.org to discuss an audit for your real estate website.
