Altwise

Locations page, store locator and service area map accessibility for small businesses

How to make your locations page, find-a-store search and service-area map usable for keyboard, screen reader and phone visitors: locations as text, maps that aren't the only way, labelled ZIP search, hours in words and clear directions links.

Clinics with several offices, franchise owners, restaurant groups, contractors with a "where we work" map and shops with more than one branch usually have a Locations page or a "Find a store" tool. People use it to answer simple questions: which location is nearest, is it open now, and how do I get there. These pages often rely on a big map, a ZIP code search and pins you have to click, which is where keyboard, screen reader and phone visitors get stuck. This guide covers what to check, whichever website builder or locator tool you use.

1. Put every location on the page as text

Each location should have its name as a heading, then its street address, phone number, hours and a "Get directions" link as real text, not only inside a map pin or a picture (WCAG 1.3.1, 1.1.1). A plain list of locations below the map is the single most useful fix: it works for screen readers, for people who zoom in, and for search engines.

<h2>Jenkins Street office</h2>
<p>1200 Jenkins St, Springfield, OK 74000<br>
<a href="tel:+15555550100">(555) 555-0100</a></p>
<p>Mon to Fri 8 am to 5 pm. Closed weekends.</p>
<a href="https://maps.google.com/?q=1200+Jenkins+St+Springfield+OK">Directions to the Jenkins Street office</a>

2. The map must not be the only way

Interactive maps are hard to use with a keyboard and say very little to a screen reader. Keep the map if you like it, but make sure everything on it is also in the text list. Give an embedded map a title, such as "Map of our three locations" (WCAG 4.1.2), and check that Tab doesn't get stuck inside it (WCAG 2.1.2). See Google Maps embeds.

3. A ZIP code or city search that works for everyone

The search box needs a visible label like "Enter your ZIP code or city", not only placeholder text that disappears (WCAG 3.3.2). The search button needs a name, even if it's just a magnifying glass icon. When results appear, say so in words, for example "3 locations found within 10 miles", in a status message screen readers announce (WCAG 4.1.3). If nothing matches, say so and suggest what to try. A "Use my location" button is handy, but keep the typed search as well, since some people block location access.

4. Hours and "Open now" in words

Write hours as text, with today's hours easy to find. If you show "Open now" or "Closed" with a green or red dot, include the words, not only the colour (WCAG 1.4.1). Holiday hours belong in the text list too, not only in a banner image. See hours tables.

5. Links and buttons that say which location

Ten links that all say "Directions" or "Book here" sound the same to a screen reader user who lists the links on the page. Name the location in the link, for example "Book at the Jenkins Street office" (WCAG 2.4.4). Make phone numbers tappable and big enough to hit on a phone (WCAG 2.5.8).

6. Service-area maps for contractors and delivery

A shaded map of the area you serve tells a screen reader user nothing. Add a sentence or a list of the towns, counties or ZIP codes you cover, and how far you travel. If the area is only in an image, that text is the fix (WCAG 1.1.1).

7. Phones and zoom

Many locator tools put the map and the result list side by side. Check at 200% zoom and on a narrow phone screen that the list is still readable without sideways scrolling and doesn't hide behind the map (WCAG 1.4.10).

8. Access details, honestly

Visitors with disabilities often want to know about parking, step-free entry, elevators or quiet times before they go. If you list these, keep them factual and current for each location ("step-free entrance on the north side", "elevator to the second floor"), and give a phone number for questions. Don't call a location "fully accessible" unless you've checked what that means for it.

Built-in page vs. store locator tool

Website builders and store locator apps handle maps, search and results lists differently, and they change over time. Whichever you use, test the live page with a keyboard and a phone rather than relying on a feature list, and add a plain text list of locations if the tool doesn't give you one.

Common mistakes

A 5-minute check you can do today

  1. Scroll past your map. Is every location's address, phone and hours there as text?
  2. Use only the Tab key. Can you search, get through the map without getting stuck, and reach each location's links?
  3. Search for a ZIP code with no results. Does the page say so in words?
  4. Turn on VoiceOver or TalkBack and list the links: does each one name its location? See the 10-minute screen reader test.
  5. Zoom to 200% on a phone and check the results list.

What a scan can and can't check here

Automated scans find only part of the barriers on the pages they visit. Our scan can flag maps with no title, unlabelled search fields, buttons with no name, ambiguous links in some cases and many contrast problems. It can't type a ZIP code or judge whether your locations are all listed as text, and it can't tell whether your site meets any law. Our Fix-Pack checks up to 10 pages, which can include your locations page and a location detail page, and gives copy-paste fixes for your platform.

Building locations pages for multi-site clients? The agency 5-pack gives you five white-label reports ($499, use within 12 months).

This is general technical guidance, not legal advice, and it doesn't certify compliance with the ADA or any law, or protect against claims. Altwise isn't affiliated with any map, store locator or website builder.

Want the fixes written for you?

Start with a free homepage snapshot. The $149 Fix-Pack scans up to 10 pages and gives copy-paste fixes for your platform within 48 hours, with a 14-day refund promise. See a sample report first.

This is general technical guidance, not legal advice, and it does not certify compliance with the ADA or any law.

Related guides

All guides

This guide is general technical information, not legal advice. Following it does not certify ADA or any legal compliance. Automated checks find only part of accessibility barriers.

Check your own site, then decide

  1. Free homepage snapshot. Your top 3 issues in about a minute. No signup, no card.
  2. $149 Fix-Pack, if you want the full list. Up to 10 pages scanned, issues ranked by impact, copy-paste fixes for your platform, delivered within 48 hours, plus one re-scan after you apply them.

Get my free snapshot Order the Fix-Pack – $149

14-day refund promise. See a sample report first. A technical report, not legal advice; automated checks find only part of accessibility barriers.