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
ch...@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?
We recommend allowing the user to use tabs to get to the next pin instead of the arrow key to better accommodate screen reader functionality.
What part of the API (please specify, a library, or the code module)?
Part of the Marker Library - using the new pins that Yext implemented for Chick-fil-A
Please describe how the feature should work:
When using the JAWS or NVDA screenreader, it should read aloud the next pin when we toggle to the next pin; right now, using the arrow key to toggle will result in an inconvenient experience where the individual letters of the pin ID are read aloud.
Please give a use case or explain where and why you need this feature:
At the moment, JAWS (screenreader) reads the first pin id/title, but on arrow key, will list out the letters on the id/title. Reaching the end of the id/title will toggle to the next pin. There is no clear audio indicator that it has toggled to the next pin, other than a spoken "blank". On all pins but the first one, the pin id/title is not read aloud as words, but instead as letters. On pin toggle, visual focus does shift to the next pin.
NVDA will speak the full id/title of the first pin that receives focus. Hitting arrows keys to toggle to diff pins will first read out the letters of the current pin, after which NVDA say "out of button, button" and then proceeds to spell out the id/title of the next pin. Visual focus indicator is not updated on pin toggle.
Use case: Google Maps is currently not built to WCAG 2.0 AA standards, and the above feature request will make the experience more accessible.