Status Update
No update yet.
Comments
ro...@gmail.com
However, looking for keyboard accessibility, we are not able to trigger the information dialog using a keyboard similar to how to map markers can be triggered using arrow keys:
Is there something we can do about it?
Thank you!
Map version: 3.49.12
ro...@gmail.com
Thanks for your suggestion!
We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.
ro...@gmail.com
✨
ro...@gmail.com
The proposed HTML focusgroup attribute is specifically designed to mitigate excessive tab stops:
- Explainer:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/explainer.md - Polyfill:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/focusgroup_polyfill.js - Chromium bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1286127
It would in theory also resolve:
jo...@gmail.com
I don't think this is an issue anymore because users can't even tab to markers at all anymore or use the keyboard shortcut to markers. So we went from too many to none at all.
Tested on 06/10/2022 Chrome 102.0.5005.61 on Mac OSX 12.3.1 on
Description
Reported externally as
Feature request to not have more than twenty tabbable points on a map at a time. From reviewing various map implementations across the web it looks like developers and designers often seek to have no more than ten to twenty tab stops on a map.
Having too many tab stops on a web page can make it very difficult for people to navigate that are unable to use the mouse. By default our map visualization would have over two hundred tab stops due to the number of locations in NYC.
For more information, please check:https://equalentry.com/accessible-maps-on-the-web/#issueexcessivetabstops_dfR