E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Murphy, Sean
Date: Sun, Feb 23 2020 8:02PM
Subject: Country maps best practise and examples.
No previous message | Next message →

All,

I am currently on a hunt for an example of a map which works with Keyboard, Low Vision, cognitive and screen readers. The map must be able to zoom into a street, zoom back up to suburb level, be able to show streets of the near-by suburbs, zoom out to state level and then to the country level. I see this working okay for low vision, keyboard only users and possibly for cognitive disabilities if the map is kept simple. The challenge I see is with screen readers. So if people have examples which they have made accessible. Please let us know.

This is a new area of accessibility for myself. 😊

Regards
Sean

From: Patrick H. Lauke
Date: Mon, Feb 24 2020 1:53AM
Subject: Re: Country maps best practise and examples.
← Previous message | Next message →

On 24/02/2020 03:02, Murphy, Sean wrote:
> All,
>
> I am currently on a hunt for an example of a map which works with Keyboard, Low Vision, cognitive and screen readers. The map must be able to zoom into a street, zoom back up to suburb level, be able to show streets of the near-by suburbs, zoom out to state level and then to the country level. I see this working okay for low vision, keyboard only users and possibly for cognitive disabilities if the map is kept simple. The challenge I see is with screen readers. So if people have examples which they have made accessible. Please let us know.
>
> This is a new area of accessibility for myself. 😊

Particularly for screen reader users, I think it's important to
establish exactly what the purpose of the map is ... what is it trying
to convey exactly (beyond "showing" the map). Is it to determine what
streets (street names/numbers) are in a particular area? List specific
points of interest? If it's just a generic "show all roads" that will be
quite difficult to convey non-visually (other than providing a non-map
alternative that simply lists stuff in text), I would posit.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Murphy, Sean
Date: Mon, Feb 24 2020 2:24AM
Subject: Re: Country maps best practise and examples.
← Previous message | Next message →

Patrick,

Mobile coverage for a specific frequency is the information being shown. At suburb level it might say 3g coverage 90%, at street level it might say 90% 3g cover. More you zoom out the coverage information is similar but at a higher view. Sighted (mouse) users can scroll around at suburb levels to see other streets coverage level all at real time. This currently is shown in colour. I already know there is issues for showing only in colour.

I hope this clarifies things.

Sean

From: Patrick H. Lauke
Date: Mon, Feb 24 2020 2:50AM
Subject: Re: Country maps best practise and examples.
← Previous message | Next message →

On 24/02/2020 09:24, Murphy, Sean wrote:
> Patrick,
>
> Mobile coverage for a specific frequency is the information being shown. At suburb level it might say 3g coverage 90%, at street level it might say 90% 3g cover. More you zoom out the coverage information is similar but at a higher view. Sighted (mouse) users can scroll around at suburb levels to see other streets coverage level all at real time. This currently is shown in colour. I already know there is issues for showing only in colour.

I'd posit that for a screen reader (and probably low vision) user, this
sort of exploratory model will be difficult to navigate, even if the
interface itself was made accessible. It may make more sense to offer a
separate, more targeted interface with a search form and some parameters
(such as the granularity/area) where they can just type in the suburb or
street, and get the information about coverage. If feasible, offer
lower-level/higher granularity options in the results (e.g. if they
chose to get coverage info at suburb level, then list the streets or
whatever in that area).

That'd be my gut feeling on this anyway.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Brandon Keith Biggs
Date: Mon, Feb 24 2020 9:40AM
Subject: Re: Country maps best practise and examples.
← Previous message | No next message

Hello,
You could have people enter their zip code and textually describe the
coverage.
For example:
94115, covered on the west side until California Street, and no coverage
past that point.
Or what most places do is have you enter your address and show if you are
covered.
Thanks,

Brandon Keith Biggs <http://brandonkeithbiggs.com/>;


On Mon, Feb 24, 2020 at 1:50 AM Patrick H. Lauke < = EMAIL ADDRESS REMOVED = >
wrote:

> On 24/02/2020 09:24, Murphy, Sean wrote:
> > Patrick,
> >
> > Mobile coverage for a specific frequency is the information being shown.
> At suburb level it might say 3g coverage 90%, at street level it might say
> 90% 3g cover. More you zoom out the coverage information is similar but at
> a higher view. Sighted (mouse) users can scroll around at suburb levels to
> see other streets coverage level all at real time. This currently is shown
> in colour. I already know there is issues for showing only in colour.
>
> I'd posit that for a screen reader (and probably low vision) user, this
> sort of exploratory model will be difficult to navigate, even if the
> interface itself was made accessible. It may make more sense to offer a
> separate, more targeted interface with a search form and some parameters
> (such as the granularity/area) where they can just type in the suburb or
> street, and get the information about coverage. If feasible, offer
> lower-level/higher granularity options in the results (e.g. if they
> chose to get coverage info at suburb level, then list the streets or
> whatever in that area).
>
> That'd be my gut feeling on this anyway.
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >