IssueTracker

Are you planning to make a fix for v3?

Bump...

Lack of keyboard accessibility (or an easy way to implement it - just put classes or ids on your control elements!) is one of the biggest obstacles to big corporations adopting Google Maps. The government of Canada was successfully sued over a webpage that wasn't keyboard and screen reader accessible. They're not going to risk another lawsuit by using Google Maps until this is resolved.

Google maps isn't keyboard accessible out of the box:
http://toerisme.groningen.nl/over-groningen/groningen-op-de-kaart (You can't reach any of the bookmarks, nor the navigation buttons, nor the "map, satellite, both" buttons.)

This can be fixed somewhat yourself:
http://www.accessibilitymonitor.nl/contact (This example shows a google maps implementation that is keyboard accessible with the tab and enter buttons)

However in the new versions of maps this is harder to do.

Could we please have an out of the box solution for this?

I am an accessibility inspector and frequently inspect websites for the Dutch government (city websites, province websites, etc.) they want to use google maps on their websites but I see them take google maps of their websites more and more often because they have to conform to accessibility standards (WCAG):
http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html

Thank you for reading,

Brian Bors.

I'd like to bump this up and add on to this - regular Google Maps has buttons that are actual buttons (on https://www.google.com/maps/). The maps created through the Javascript V3 API (https://developers.google.com/maps/documentation/javascript/) are clickable divs, which are not accessible. This is extremely important for us in order to keep using Google Maps. Mapbox supports keyboard accessibility much better out of the box. It would be good to add in the same support to your Javascript created maps that you have available on your regular maps product.

Thanks,
Diane Ko

Are there any intentions of fixing this soon? This was defined/marked as a feature request, but it really should be considered a bug. Switching out the divs for buttons would fix this problem and would be fairly easy/straightforward to fix.

Thanks you for your interest in this feature request. We are still gathering support for this issue, please keep starring this issue to give it more "weight".

We've fixed the control buttons on the map. This doesn't apply to StreetView controls and UX which still require a pointing device. Please open another issue if that's a problem.