Fixed
Status Update
No update yet.
Comments
mi...@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
st...@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.
[Deleted User] <[Deleted User]>
✨
sh...@google.com
Apologies for not getting back to you earlier.
We are interested to know if this is still a desired feature and if so, could you please provide your use case?
We are interested to know if this is still a desired feature and if so, could you please provide your use case?
sh...@google.com
[Deleted User] <[Deleted User]>
I must have missed the original notification from a month ago, so apologies for the late reply. This is still a valid use case.
For a keyboard user that's navigating to the map, there are some useful keyboard navigation features that you've encoded into the map (such as using the arrow keys to pan around the map area). However, because there's no focus ring around the entire map when the map has focus, it's unclear when the map itself has focus and when those keyboard shortcuts do anything. Also, since there's some additional hidden tab stop between the map itself and the first visibly focusable element in the map, it's easy to miss when you've tabbed to the element that has key event listeners to update the map location.
Please fix this issue, it's still an issue in the map link I posted earlier.
For a keyboard user that's navigating to the map, there are some useful keyboard navigation features that you've encoded into the map (such as using the arrow keys to pan around the map area). However, because there's no focus ring around the entire map when the map has focus, it's unclear when the map itself has focus and when those keyboard shortcuts do anything. Also, since there's some additional hidden tab stop between the map itself and the first visibly focusable element in the map, it's easy to miss when you've tabbed to the element that has key event listeners to update the map location.
Please fix this issue, it's still an issue in the map link I posted earlier.
Description
# It is OK to share your API Project ID, but _not_ API keys.
Issue report
----------------
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. Go to any page that has a map (ex:
2. Tab forward until you should be at the map
What happens:
When the map is focused, there is no focus ring
What's expected:
When the map is focused, there's a focus ring.
This is particularly problematic because it's unclear when you can use keyboard shortcuts (ex. panning with arrows) without the focus ring. I found that I can back tab (shift+tab) twice from when the Google logo gets focus to be on the map. If I back tab once, I don't know what element I'm on, but it doesn't accept keyboard shortcuts.