Assigned
Status Update
No update yet.
Comments
ka...@google.com
ka...@google.com
Thank you for the post.
I would just like to clarify if this issue is related to
an...@gmail.com
This is the issue with Maps Javascript API
ka...@google.com
Hello,
We noticed that you attached the same long document for each bug you reported. While we appreciate the detailed information provided, it would be really helpful if you could attach relevant screenshots of the document to each corresponding bug report. This will help us better understand the specific context of each issue. Thank you!
ka...@google.com
Please disregard the request above.
We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
Description
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
# Describe your issue
Issue description
There is no way to perform the function using only the keyboard on the same screen or on a qualifying conforming alternate version.
Element description:
- The location elements on the map
Description of the issue:
- The location buttons on the map shows the location details when activated but they are not operable using the keyboard alone.
RULE :
Functionality MUST be available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard.
HOW TO FIX:
Fix this issue by using use either a device independent event handler (one that works with both the mouse and the keyboard) or use both mouse dependent and keyboard dependent event handlers.
Device independent event handlers include: onfocus, onblur, onselect, onchange, and onclick (when onclick is used with a keyboard-focusable element).
Bad: <button ondblclick="foo()"">Next</button>
Good: <button onclick="foo()"">Next</button>
REFERENCE:
Deque University:
BACKGROUND:
Some people cannot use a mouse due to vision or motor disabilities. Content that can be operated with a mouse must also be made operable with a keyboard. When content is operable through a keyboard, it becomes operable by a variety of assistive technologies such as speech input software, sip-and-puff software, on-screen keyboards, scanning software, and alternate keyboards.