W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

Re: Accessible map with polygons

From: Michiel Bijl <michiel.list@moiety.me>
Date: Wed, 29 Nov 2017 10:27:10 +0100
Cc: W3C WAI ig <w3c-wai-ig@w3.org>
Message-Id: <CC22D337-C26D-4F60-A475-C1C101D94E50@moiety.me>
To: Matt King <a11ythinker@gmail.com>

> On 29 Nov 2017, at 09:04, Matt King <a11ythinker@gmail.com> wrote:
> The polygon is drawn around a point on the map … does that point have a name, address, or something to identify it?

Let’s say the point is your house and we want to show all the places you can reach within a certain time. Four oddly shaped polygons will be drawn to indicate areas that you can reach within 5, 10, 20, and 30 minutes respectively all centred on the initial point. So an actual list of all the point within that area would be pointless (ha) because there would be too much data. You could filter it down to a few places of interest but that might exclude the user is actually looking for. 

> If the objective is to communicate that the time to travel from your current location to bus stop 23 is 5 minutes and the time to get to bus stop 18 is 10 minutes, why not label the polygons with both the time and the point of interest? Then, each element will accomplish its objective for screen reader users without the need to reference the key.

I’ve talked a bit more with the UX people and in the final product you can click/tap anywhere on the map and get an indication of how long it’ll take you to get there. Which is fine on touch devices, but doesn’t solve the problem for all users.

Perhaps a filtered list of points of interest is a good alternative after all, hmm.

— Michiel
Received on Wednesday, 29 November 2017 09:27:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:11 UTC