Map navigation

[Malvoz]

Many or all aspects of (accessible) map/feature/POI navigation are intertwined. I wonder if we should add a new Project to track issues/PRs that relate to it to keep track of what's done (and TBD) for an overview? Or maybe this discussion is sufficient.

Done:

• Features should have accessible names for discernability #316
• Allow features on a map to be tab navigable  #268
• Focus on the feature when activating feature link #607
• Feature tabbing bypass blocks #280
• Programmatically identifiable map #151
• role="application" #274
• Announce zoom and move and implementing map boundaries  #533
• native-like styles for interactive features #478
• Query handling keyboard access #291
• Allow adding queried features in turn using the "previous" and "next" bypass block buttons  #282

To be done/decided:

• Meaningful Pan & Zoom (and Feature navigation) #396
• Feature Index #397
• Focus features on tab #571
• Tab order based on distance from center #596
• Expose features' relation to layers? (hierarchies) #579
• Implement custom non-visual navigation grids #552
• Replace mapml-focus-buttons with subclass role of composite widget role or proposed focusgroup attribute #535
• Make reticle automatically issue query on move end #405

Testing / validation:

• Map Navigation Tasks for Testing #335
• Test Popup Text Cycling with Screenreader #296
• Feature Links accessibility validation #615

<map> browser bug:

• Features are not announced (by NVDA, at least) when <map is="web-map" ...> is used #472

Instructions:

• Text instructions for keyboard shortcuts and the query reticule #267