patternfly
Bug - Tooltip - aria prop not working correctly with VO
Describe the problem
A clear and concise description of the problem. Which components are affected?
There is a bug in the "On icon with dynamic content" demo of Tooltip. http://patternfly-react-v5.surge.sh/components/tooltip#on-icon-with-dynamic-content
In the docs it is mentioned that you can pass aria to prevent the content from being read twice by a screenreader, however the content is still getting read twice in the example if you test with VO.
How do you reproduce the problem?
Go to the link above and navigate to the tooltip with VO.
Expected behavior A clear and concise description of the expected behavior.
Tooltip content is read only once.
Is this issue blocking you?
List the workaround if there is one.
Not blocking, found workaround by setting role="none" on Tooltip
What is your product? Found in ODH
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Following comments are in regards to v6.
Looking into this, it sounded like this is a VoiceOver bug rather than PF. This stack overflow on aria-live content read twice by Mac links to an issue that may be related.
When testing with NVDA in Firefox, though, I get the same issue. This could possibly be a program setting within the screen readers as well, but a potential solution could be to not have the tooltip be an aria-live region and instead dynamically update the trigger's aria-label. We'd have to check whether that is consistent across some AT, though, and if not a duplicate announcement may be the lesser evil.
Also worth noting that the bug doesn't occur with VO+Safari.
Removing the stale label for now, though.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.