Reviewed October 22, 2026

Accessible store locators: maps that work without a mouse

Store locator pages assume a mouse and a visual map. Pinch, drag, click a pin, read a tiny popup. For keyboard and screen reader shoppers that pattern is a wall. The list based fix that serves everyone better.

The map is the barrier

Embedded maps are built for pointer interaction. Pins cluster until you zoom, zooming needs a scroll wheel or precise pinch, and store details hide inside popups that open on click. Keyboard focus typically lands on the map frame and then has nowhere useful to go, while screen readers announce a string of unlabeled graphics or nothing meaningful at all.

The irony is that the map is the decorative part. What a shopper actually needs is a short list: which stores are near me, how far, when do they close, and how do I get directions. Every one of those answers is text, and text is the format assistive technology handles perfectly. The map should be an enhancement layered on top of the list, never the only door.

The list pattern that works

Start with a search field with a real label, accepting a postcode or city, and return results as a structured list rather than as map pins only. Each result gets the store name as a heading, address, distance, opening hours, a phone number as a tappable link, and a directions link that hands off to the shopper's own maps app.

Order results by distance and say so, because screen reader users cannot skim a map to infer which pin is closest. If stock checking is part of the locator, include the stock status in the list item text rather than as a color dot on a pin. Color alone as the carrier of stock or open status information fails both screen reader and color blind shoppers at once.

Keyboard details that get missed

If you keep the interactive map, its controls need labels: zoom in, zoom out, and the map region itself should be reachable but not a focus trap. Arrow key panning inside a map frame can swallow dozens of Tab stops' worth of effort, so the frame should be one stop, with instructions, not an endless field.

Popups deserve special attention. When a pin opens a detail card, focus should move to it deliberately, the card needs a labeled close button, and closing it should return focus to where the shopper was. A popup that appears visually while focus stays lost behind it is the locator equivalent of a door that opens into a wall.

Testing the locator like a customer

Unplug the mouse and complete the whole task by keyboard: search for a nearby town, identify the closest store, find its closing time, and open directions. Time it. A sighted mouse user does this in under a minute, and a working accessible version should land in the same neighborhood rather than five times longer.

Then repeat with a screen reader and check that distances and hours are announced with each store rather than detached from it. Locators are high intent pages; someone checking your store hours is planning a trip. Failing them at this exact step costs a visit, not just a page view.

Frequently asked questions

Is an embedded map automatically inaccessible?

Not automatically, but a map as the only interface effectively is. Pair it with a labeled search and a structured text list of results and the page works for everyone, with the map as a visual enhancement for those who use it.

What should each store listing include?

Store name as a heading, full address, distance from the searched location, opening hours, a tappable phone number, and a directions link. Stock status belongs in the text too if you show it, not only as a colored indicator.

Do directions links need anything special?

They should be descriptive, like get directions to the Riverside store, rather than a bare click here, and they should open the shopper's preferred maps application or site. The link purpose must be clear from its text alone for screen reader users navigating by links.

How do I test a locator without special tools?

Use only your keyboard for the full task and note where focus disappears or gets trapped. Then run a free screen reader for one search. Most locator failures are obvious within two minutes of either test.