Store Locators and Maps: Watching the Hardest Widget on Your Site
Embedded maps are where accessibility goes to struggle. How to watch a store locator and give every shopper a usable alternative.
Almost every store locator is an embedded map with a search box bolted on, and almost every one fails the same shoppers: keyboard users panning a map with no alternative, screen reader users facing a canvas with no names, and mobile users pinch zooming a frame that traps their scroll. The locator is often the page that sends shoppers to a physical store, so its barriers cost foot traffic too.
You probably cannot make the map itself fully accessible. You can watch it properly and guarantee a parallel path that works for everyone. Here is how.
The list is the accessible product
Every locator should pair its map with a real list of locations in text: name, address, hours, phone, and distance where available, in an order that matches the search. The list is not a fallback for a few users. For many shoppers it is faster than the map, and for assistive technology users it is the product.
Watch the list as a first class surface. When a new store opens or hours change, the list and the map pins must update together. A location present on the map but missing from the list is invisible to exactly the shoppers who rely on the list.
Search and filters on the locator
Locator search fails quietly: a postcode field with no label, results that update with no announcement, filters for accessibility features like step free access buried in an unlabelled panel. Test the search end to end with a screen reader and confirm the results count and the list update are announced.
If your stores have accessibility features, make them filterable and accurate: step free entrance, accessible parking, hearing loop. Bad data here is worse than no data. A shopper who travels to a store listed as step free and finds stairs will not trust the locator, or the brand, again.
Keyboard traps and scroll traps
Embedded maps are notorious focus and scroll traps. A keyboard user tabbing into a map frame should be able to tab out again, and a touch user should be able to scroll past the map without being captured by it. Test both on the live page, because the embed settings that cause traps are often a configuration toggle.
Give the map frame a proper title so screen reader users know what it is and can skip it for the list. Silence is the worst outcome: a frame announced as nothing leaves a shopper guessing whether the page loaded at all.
What to put in the watch plan
Add the locator to your standing watch list with three checks: the list matches the store database, the search announces results, and the frame does not trap keyboard or scroll. Re run them after any locator vendor update and after store network changes like openings and closures.
Also watch the individual store pages the locator links to. Hours, holiday closures, and local services live there, and an accessible locator leading to a broken store page still strands the shopper at the last step.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Watching Product Quick View Modals for Accessibility Failures, Watching Holiday Gift Guide Pages for Accessibility Regressions, and Watching Accessibility Across Multiple Storefronts and Markets.
Frequently asked questions
Can an embedded map be made fully accessible?
Rarely on its own. The practical standard is a fully usable text alternative: a list of locations with addresses, hours, and contact details that stays in sync with the map, plus a map frame that traps nobody and is properly titled for screen readers.
What locator failure hurts most?
A store missing from the text list while present on the map, and search results that update with no announcement. Both make locations effectively invisible to assistive technology users even though the page looks complete to a sighted reviewer.
Should accessibility features of stores be listed?
Yes, if the data is verified: step free access, accessible parking, and similar features help shoppers plan, and filtering by them is genuinely useful. Inaccurate listings are worse than none, so the data needs an owner and a review habit.
How often should a locator be checked?
Whenever stores open, close, or change hours, after locator vendor updates, and on a regular standing cadence. The three core checks are quick: list accuracy, announced search results, and no keyboard or scroll traps.