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
The button does not have a role.
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 provided with button role.
RULE :
The name, role, value, states, and properties of user interface components MUST be programmatically determinable by assistive technologies.
HOW TO FIX:
Fix this issue by using ONE of the following techniques:
1. Use a native HTML <button> element.
<button>Apply now!</button>
2. Add role="button" to the custom button container. NOTE: If you use role="button" instead of <button>, you will need to ensure Enter and Spacebar can activate the button.
<span role="button" class="apply-btn" aria-label="Apply Now!"></span>
REFERENCE:
W3C HTML5 Recommendation:
Deque University:
BACKGROUND:
Every user interface control must have a role to convey what type of control it is for screen reader and other assistive technology users. Native HTML elements - such as <button>, <a>, <input>, <select> - already have a role, so nothing more needs to be done. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant role(s) using ARIA as well as expected keyboard interactions.