Assigned
Status Update
No update yet.
Comments
rc...@google.com
We are building a polygon array with a click event: https://developers.google.com/maps/documentation/javascript/examples/polygon-arrays
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:https://developers.google.com/maps/documentation/javascript/examples/marker-accessibility
Is there something we can do about it?
Thank you!
Map version: 3.49.12
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
jh...@google.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.
Description
# It is OK to share your API Project ID, but _not_ API keys.
What would you like to see us add to this API? What would you like to see us add to this API?
At the moment, using a screenreader on Google Maps with the dynamic markers will result in the use case described below. Our recommendation is to revise the map toggling ordering from maps to pins; at the moment, if you toggle from another HTML element to the map, you encounter a problem in which the generic map pins are named before the accessible map pins (see "use case" section for further details)
What part of the API (please specify, a library, or the code module)?
Marker Library
Please describe how the feature should work:
Our recommendation is to revise the map toggling ordering from maps to pins.
Please give a use case or explain where and why you need this feature:
At the moment, the screenreader "VoiceOver" goes through a list of generic, unnamed pin HTML elements before reaching the accessible ones (with the correct id/title that is set in the Marker constructor). These generic pins take 2 swipes to go toggle for each pin- one for saying "map pin" and another for saying the pin's number- and don't have any descriptive speech other than that. For the accessible pins, the entire id/title is read, and the visual focus is updated on pin toggle. After reaching the end of the accessible pins, the focus goes to the zoom button, unlike on desktop where VoiceOver continues to loop through the pins- this could be because mobile VoiceOver doesn't have a different gestures (with desktop we have arrow keys and tab, on mobile it's just the swiping motion).
This issue occurs on mobile, and this indicates that Google Maps is not an accessible experience for those using screen readers.