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

Re: Accessible map with polygons

From: Léonie Watson <tink@tink.uk>
Date: Wed, 29 Nov 2017 10:58:37 +0000
To: Michiel Bijl <michiel.list@moiety.me>, Matt King <a11ythinker@gmail.com>
Cc: W3C WAI ig <w3c-wai-ig@w3.org>
Message-ID: <3a306b45-df7f-ef5d-ec72-9e5a6d4b8064@tink.uk>
If the point references on the map can be extracted in text format, you 
could offer an alternative view of the information. Perhaps lists that 
included the locations within each radius/polygon.

If you present this in a set of tabpanels, it would enable all users to 
switch between the two views. It's likely that the option to view the 
information in either format will benefit allsorts of different people.

On 29/11/2017 09:27, Michiel Bijl wrote:
> On 29 Nov 2017, at 09:04, Matt King <a11ythinker@gmail.com 
> <mailto: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

@LeonieWatson @tink@toot.cafe tink.uk carpe diem
Received on Wednesday, 29 November 2017 10:59:22 UTC

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