Feature tab order

[prushforth]

For a blind user, the visual map is not relevant. However, the features in the map could be relevant, much like a search result, if they were presented as a list of things, sorted in descending order of spatial relevance, which at a first approximation, and for this experiment could be taken to be "distance from the centre of the map".

I think that may be how maps are relevant to blind users - the content that sighted users can distinguish at a glance could be automatically ordered by the user agent based on space / spatial criteria.

cc @shepazu

[Malvoz]

For a blind user, the visual map is not relevant.

That's only true because there is no feedback to the user during/after panning and zooming. If any feature/POI in view would be announced to the user as well as the direction in which they're panning, even a visually impaired user could build a mental model of the physical relation between them.

The alternative interaction model that Esri uses in the a11y-map prototype accomplishes the above (although not bug free). You can try the demo here: https://esri.github.io/a11y-map/ (follow the instructions for keyboard navigation). @shepazu I hope that you can try it out as well if you haven't already, it's very inspirational.

[Malvoz]

(follow the instructions for keyboard navigation)

The Features section is actually a bit more clearer about available keyboard shortcuts.

[Malvoz]

@prushforth since you raised Maps4HTML/MapML.js#385 I think that's a better place to hold this discussion, can we close this issue?

[prushforth]

I think that's a better place to hold this discussion, can we close this issue?

Sure thing