-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[a11y]: JAWS reads Tooltip as button #10667
Comments
Duplicate issue but closed as won't fix |
@dakahn can you confirm if this is an issue after all? |
Potentially relevant |
attempted to verify with JAWS 2022.2112.24 and couldn't reproduce. When the tooltip button receives focus it's read as "tooltip label button expand/collapse" which seems right to me. Describes the element, what it is, and what will happen if it's activated. Im closing this as a false report, but after you upgrade JAWS if you still are encountering this error let me know and we can reopen 👍🏾 |
Package
Browser
Chrome
Operating System
Windows
Package version
10.52.0
React version
17.0.2
Automated testing tool and ruleset
JAWS 2021
Assistive technology
No response
Description
What is expected: Jaws could recognize Carbon Tooltip as tooltips, read tooltip label and tooltip messsage.
What happens: All the tooltips info within application are not able to be read by JAWS. When a respective tooltip is opened, JAWS reads it as button collapsed to open press space bar/Enter key, expanded. Pressing Space Key/Enter key closes the tooltip. Here the user will get confused as there is no button it’s just tooltip.
After update to "carbon-components": "10.52.0" "carbon-components-react": "7.52.0", JAWS is able to read tooltip message, automatically open and close when focus on and off. But it still reads tooltip as button, tells press enter to activate.
WCAG 2.1 Violation
No response
CodeSandbox example
https://react.carbondesignsystem.com/?path=/story/components-tooltip--default-bottom
Steps to reproduce
Code of Conduct
The text was updated successfully, but these errors were encountered: