-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[High]: Chrome+JAWS: Screen reader: Role is not defined for control. #8393
Labels
Comments
52 tasks
This was referenced Jun 2, 2022
This was referenced Jun 9, 2022
@SumitDiyora, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
50 tasks
71 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Action Performed:
Expected Result:
Role should be defined as a 'button' for the "Invite" control.
Actual Result:
Role is not defined for the "Invite" control. This made it difficult for screen reader users to access the functionality associated with it.
Other Occurrences:
Workaround:
Yes
Area issue was found in:
Invite new members
Failed WCAG checkpoints
4.1.2
User impact:
Screen reader users will not be made aware that these elements are buttons.
Suggested resolution:
Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:
Platform:
Version Number: 1.1.49-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Reference link: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role
Issue reported by: Sumit
The text was updated successfully, but these errors were encountered: