Accessible Store Locator Maps: The List Matters More Than the Pins
Map based store locators shut out shoppers who cannot use an interactive map. Why an accessible list, clear details, and keyboard friendly search make the locator work.
A store locator built around an interactive map assumes a shopper who can see pins, drag a canvas, and read tiny popups. For many shoppers that map is a wall. They need the same facts the map holds: which store, how far, when it opens, and how to get there, in a form they can actually use.
The good news is that the accessible version is also the practical version. A clean list with complete store details serves screen reader users, keyboard users, people on slow connections, and anyone who simply prefers reading to pin hunting.
Always pair the map with a real list
Every result on the map should also appear in an HTML list, updated with the same search. Each entry needs the store name, address, phone number, hours, and a directions link in text. Selecting a list item can highlight the map pin for sighted users, but the list must stand on its own.
Distance and open now status should be text, not color coding. A green dot meaning open is invisible information to many shoppers. Write it out, and keep the list order logical, usually nearest first, with that order stated.
Make search and filters keyboard friendly
The postcode or suburb field needs a visible label, an error message in text when nothing is found, and results that are announced or at least predictably placed after the search controls. Autocomplete suggestions must be reachable by keyboard and readable by screen readers, a detail many map libraries get wrong.
Filters like wheelchair access, parking, or specific services are valuable only if they are real controls with labels. Those filters also carry a responsibility: keep the underlying store data accurate, because shoppers plan trips around it.
Give directions and details a text route
Directions links should open a route the shopper can read step by step in their maps app, and the store detail page or expanded entry should include practical access facts: step free entry, nearest transit stop, and parking notes where you know them.
Phone numbers should be tap to call links with the number visible as text. A call icon alone fails voice control users and anyone trying to copy the number into another app.
Test with the map switched off
A revealing test is to disable the map script entirely and try to find your nearest open store using only the list. If that works smoothly, your locator has a solid foundation. If it collapses, you have found exactly what a large group of shoppers experiences whenever the map fails to load.
Repeat the test after any locator app or theme change, and on a phone with zoom enabled, where maps tend to swallow gestures and trap scrolling inside the canvas.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Accessible Returns Portals: Starting and Tracking a Return, Accessible Product Comparison Tables That Actually Compare, and Making Size and Colour Swatches Accessible.
Frequently asked questions
Can an interactive map ever be accessible on its own?
Not fully for most shoppers. Maps are spatial and gesture heavy, so the standard approach is an equivalent list with the same store information in text. The map can stay as an enhancement, but the list is what guarantees access.
What details should each store listing include?
Store name, full address, phone number as visible text, opening hours, distance from the search point, and a directions link. Add access facts like step free entry when you have reliable data, and keep hours updated for holidays.
How should no results be handled?
Say plainly that no stores matched, suggest widening the distance or checking the postcode, and keep the message where keyboard and screen reader users will encounter it. A silently empty map looks like a broken page.
Why test the locator with the map disabled?
Because that is the experience for shoppers who cannot use the map and for anyone when the map script fails. If the list alone completes the task quickly, the locator works for everyone, not just confident map users.