W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

Re: Using Maps

From: Olaf Drümmer <olaflist@callassoftware.com>
Date: Fri, 21 Feb 2014 18:01:42 +0100
Cc: Olaf Drümmer <olaflist@callassoftware.com>
Message-Id: <478E2C09-2283-45D6-BB3F-22BBE43AA633@callassoftware.com>
To: James Homme <james.homme@highmark.com>, W3C WAI ig <w3c-wai-ig@w3.org>
Depending on how the map is presented, one of the better approaches is to repeat the relevant information by means of a list. If the map has some substructure, like by federal state, create a nested list, grouped by federal state. For each actual entry offer the content (could be just the street address, or maybe also a phone number, or instructions, or whatever) and functionality (if on the map view you can interactively ask for getting directions how to get there from somewhere else, preferably offer the same feature in the list representation). For both keep mind, how someone with only keyboard access or only a pointing device and onscreen keyboard, can use the information. The list, if done well, takes care of non-sighted users or print-disabled users (e.g. via text to speech). Even users without any disability will benefit from the dual presentation approach.

My 2 cents,


On 21 Feb 2014, at 17:40, "Homme, James" <james.homme@highmark.com> wrote:

> Hi,
> In something like a store locator, maps help people without disabilities figure out a store's location. From the map, someone might infer how to get there. Would the address of the store be a good equivalent for a screen reader user, or are there other considerations?
> Thanks.
> Jim
> This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark, its diversified business, or affiliates.

Received on Friday, 21 February 2014 17:02:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:46 UTC