How should a Hong Kong business present branch locations when a map alone cannot answer a customer’s visit question?

Define the visit the page must support

A customer usually opens a location page to answer more than 'where is the pin?' They may need to know which branch accepts returns, whether a collection counter is open today, how to reach the entrance from a station, or whether an appointment is required. Make those questions the content model. List the branch name, complete address, district, contact route, current opening hours, exceptional closure notice and services available at that branch. Keep these as separate fields rather than burying them in a map popup. A geographic marker can provide orientation, but it cannot by itself explain that the entrance is behind a building or that a service is available only at certain times. State the exact kind of visit each location supports, and send a customer to the right branch rather than merely the nearest coordinate.

Use one authoritative branch record for the map marker, list card, detail page and staff directory, with an owner who checks changes. An address may be legally correct but practically incomplete if the building has several entrances; a landmark or floor can make the trip possible. Conversely, a landmark should supplement the formal address, not replace it. Store coordinates only after checking that they point to the public entrance or explain that they indicate the building rather than the doorway. Separate regular hours from one-off holiday or weather changes, and label the date when a temporary notice applies. Do not invent a standard travel time from a station: walking speed, exits and access needs vary. Give a route description that can be verified on the ground, and invite the visitor to confirm an exceptional opening before travelling.

Give a real route without the map

W3C's guidance on complex images explicitly includes maps showing locations: a short text alternative identifies the image, while a longer explanation conveys information that cannot fit into one sentence. For an interactive branch locator, a structured text list is usually more useful than a long description of every street on the map. A person should be able to choose a district, read each relevant branch, open its details and follow a directions link without entering the map. Keep the list in the same page or one clearly linked page, and do not treat a generic 'Map of our stores' alt label as an equivalent to addresses, hours and services. If the map fails to load, the list should still answer the visit question. This is a product decision as well as an accessibility requirement.

Make each location result identifiable on its own. A link labelled only 'Directions' repeated ten times is hard to distinguish in a list of links; add the branch name in the visible link or its programmatic context. State whether the link opens an external mapping service and provide the address as copyable text so people can use their preferred navigation app. Avoid automatically locating the visitor or treating a denied location permission as an error. A district selector and address search can serve people who know where they want to go without sharing a device location. If distance sorting is offered, explain that distance is an estimate from a selected point, not proof of travel time or accessibility. Check the result when the user enters an English district name or its Traditional Chinese equivalent.

Keep map controls and records in sync

The map itself still needs a workable interaction. Markers should have names that match the branch list, and activating one should expose the same essential detail. Test keyboard access to zoom, marker selection and closing a popup. If the embedded map cannot be made reliably operable, provide a clearly labelled link to open the location in the provider's app alongside the complete on-site list. Do not make a third-party map the sole route to a business-critical fact. W3C's non-text guidance says visual information needs an equivalent-purpose text alternative, while its link-purpose guidance supports clear destinations. These principles help define what the local list must contain and what each external link will do; they do not make every map widget automatically accessible.

Treat a branch move as a coordinated content change. Update the source address, coordinates, entrance directions, hours, contact details, collection eligibility and external directions link together. Verify the old detail URL either leads to a clear moved-branch notice or a relevant new page; it must not silently send a customer to the former premises. Ask a staff member unfamiliar with the change to use the published page to plan a visit, then compare the chosen destination with the actual public entrance. If a temporary closure is announced on social media, reflect it on the locator that customers use for planning. A timestamp on the notice helps, but it is no substitute for a named owner and a process for removing expired notices. Recheck the map and text list together after each update.

Test one realistic journey

Suppose a business has a showroom, a collection counter and a repair intake point in different districts. A customer wants to return a faulty appliance, not browse new models. The nearest map marker may be the showroom, which does not accept repairs. The list should allow the customer to filter or read services, identify the repair point, see whether an appointment is required, copy its full address and find the appropriate entrance. A temporary public holiday closure must attach to that location, not appear as an unexplained site-wide banner. If the customer chooses an external directions app, the destination should correspond to the repair entrance. The worked journey reveals why location data is more than pins: it is a set of operational promises about what the visitor can accomplish.

For acceptance, complete that journey using only the text list, then repeat using the map with a mouse, keyboard and touch screen. Check a screen reader announcement for each branch name and action, and check what happens when the map network request fails. Test one bilingual address that includes a building, floor and entrance instruction; the English and Chinese versions should identify the same place, while each uses natural local wording. Call or visit the branch to confirm hours and the service category before release. Capture mistakes as changes to the branch record and repeat the journey. The page is ready when a customer can independently reach the right place, at the right time, for the intended service, with either route. Review it whenever operations change.

Think about the trip after the map has done its job. A visitor may reach the right building yet find a locked side door, a counter upstairs, or a service that closes earlier than the shop. Include entrance and counter details where they affect the visit. If an accessible route differs from the shortest route, describe the verified route without claiming that every part of the surrounding street is accessible. Check that any phone number serves that branch or clearly routes the caller to central support. A locator that names the correct district but omits the final doorway can still waste a customer journey. These details belong in the maintained branch record so they appear consistently wherever the location is shown.

For multiple branches, test ambiguity deliberately. Search a street name shared by two districts, use an abbreviated building name, and choose a service offered at only one site. The result should identify the branch and explain its service, not silently select the closest coordinate. If there are no matching locations, offer a complete branch list or contact route, rather than an empty map. If a branch is temporarily unable to receive visitors, keep its identity visible with a dated status so existing bookmarks still provide an answer. Make removal from the locator a considered decision when a branch closes permanently, and update links that point to it. This is part of content accuracy, not merely map configuration.