Real Estate Website Accessibility: Listings and Maps

Opening answer

A property searcher needs to scan listings fast, narrow them by price, bedrooms, and location, look at photos, check a map, and contact an agent. Real estate website accessibility means each of those steps works without a mouse, with photos described in text, filters labelled in words, a list view beside any map, and a contact form that explains errors in plain language. Start with search and filters, then listing pages, then the map view, then the contact form, and test the full path on a phone.

Listing galleries need serviceable descriptions

A listing gallery is not a mood board. A visitor uses photos to judge rooms, layout, light, and condition, and then decides whether to contact an agent. Alt text for a listing photo should state the room and a useful detail in context, such as "Living room with large windows facing the garden" or "Kitchen with a central island and seating for four", rather than a file name or a repeated phrase like "property photo". A photo that shows only decoration, with the same information already in nearby text, should carry empty alt text so a screen reader skips it. WebAIM explains that split, and adds that an image inside a link must carry alt text stating the link function, because a screen reader otherwise has nothing useful to announce: WebAIM alt text guidance

Listing cards need the same care. A card that shows a photo, a price, a bedroom count, a bathroom count, and a location should present those facts in text, in a consistent order, on every card. A visitor who uses a screen reader should hear the price, the room counts, and the location for each listing in the same order, without having to guess which number means what. Link names on cards should state a purpose, such as "See details for the three bedroom house on Oak Street" in generic terms, rather than a repeated "View details" link with no context. If a card image links to the listing page, the alt text plus nearby text should make that destination clear.

Search filters need labels, order, and a clear result count

Filters are where listing sites most often fail keyboard users. A price range, a bedroom selector, a property type selector, and a location field each need a visible label, a keyboard path, and a clear state when selected. A custom dropdown that only works with a mouse, a slider with no keyboard alternative, and a set of checkboxes with no group label each leave a visitor stuck at the search step. Use native controls where possible, because native controls already carry names, roles, and keyboard behaviour that custom controls must rebuild by hand. Where a custom control is used, check that it announces its name, its role, and its current value to assistive technology, and that it can be operated with the keyboard alone.

Results need a clear count and a clear order. After a filter change, state the result in text, such as "12 listings match your search", near the top of the results, so a visitor who cannot see the whole page knows whether the filter worked. Keep the sort control labelled, with options in plain words, such as price low to high or newest first in generic terms. Avoid filter controls that reload the page without warning and move focus back to the top without notice, because a keyboard user then has to tab through the whole page again to reach the results. If a filter change does reload, return focus to the results heading or to a results summary, and state that behaviour in testing notes so the next developer does not undo it by accident.

Maps need a list view and text beside them

A map view is a useful way to scan locations, and it is a poor way to browse listings for anyone who cannot use a map. Every map view on a listing site should sit beside a list view of the same listings, with the same filters applied, so a visitor can browse by list, by map, or by both. A map frame needs a title that states its purpose, such as "Map showing listings in the selected area", rather than a bare frame name. More important than the frame title is the text for each listing in the list view: address in text, price in text, room counts in text, and a contact link in text.

Contact forms, contrast, and photo text

A contact form on a listing page is the moment a search turns into an enquiry, and it is where label and error mistakes cost leads. Every field needs a visible label: name, email or phone, message, and preferred contact method in general terms. Placeholder text is not a label, because it vanishes on typing. Error messages need words next to the field in error, with a suggestion where one is known, such as "Enter a valid email address" or "Add a message before sending". The Department of Justice guidance lists labels, clear instructions, and error indicators as parts of an accessible online form: ADA guidance on web accessibility Colour alone must never carry an error, because a visitor who cannot see that colour, and a screen reader user who hears no error text, will both miss it.

Contrast on listing pages needs a check for text, prices, and controls. WCAG success criterion 1.4.3 asks for a contrast ratio of at least 4.5:1 for normal text, and at least 3:1 for large text: W3C contrast guidance Check price text, room counts, and footer text, not only headings. WCAG success criterion 1.4.11 asks for at least 3:1 for visual information needed to identify a control and its state, such as a filter field border, a selected filter chip, or a focus outline: W3C non-text contrast guidance A selected filter that changes only by a faint colour shift will not read as selected without a text label or a border change to go with it. Try a target size quiz to judge tap spacing on listing cards before a redesign: Target size quiz

What a scan can check on a listing site

A free homepage scan gives a listing site owner a first list without a signup step. Axeazy offers a free homepage scan that takes about 60 seconds, with no signup and no card, and paid plans show price at checkout with annual saving of 20 to 25 percent: Axeazy pricing That scan can surface missing alt text on listing photos, missing labels on search filters and contact forms, unclear link names on listing cards, and heading order problems on listing templates. Those findings sit inside 14 fix categories, covering alt text, skip navigation, language attributes, form labels, link names, button names, ARIA labels on custom widgets, ARIA attribute validity, keyboard tab order, pinch to zoom restrictions, iframe titles, table header structure, landmark structure, and heading structure: Axeazy capabilities A tool choice guide can help weigh a scan, a checklist, and developer time in order: How to choose an accessibility tool: 10 criteria

FAQ

Should a listing site offer both a map view and a list view?

Yes, with the same filters applied to both. A list view lets a visitor browse without a map, and a map view lets a visitor scan locations, so neither view should be the only route to a listing.

What alt text should a listing photo carry?

The room and a useful detail in context, in a short phrase. A decorative photo that adds nothing beyond nearby text should carry empty alt text, so a screen reader skips it.

What is the quickest search filter test?

Tab through the filters with no mouse, change a price or bedroom filter, and check that the result count is stated in text and that focus does not jump back to the top without notice.

Does this article give legal advice?

This is general information, not legal advice. If you received a demand letter or were sued, talk to a qualified attorney, and take the scan report and fix log to that meeting.

Last checked: October 31, 2026

Sources

• W3C contrast guidance
• W3C non-text contrast guidance
• WebAIM alt text guidance
• ADA guidance on web accessibility
• Axeazy pricing page
• Axeazy capabilities page

Start with search and filters, then listings, map, and contact form, beginning with a free scan at Axeazy

Related reading

• Law Firm Website Accessibility: Forms and Contact