You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v-tooltip adds aria-describedby to the target element, which is fantastic. However, it doesn't become enabled until the first trigger has happened... which makes the description initially not available to screen readers (at least not on Vox+chrome).
Is there some way to force add all instances of aria-describedby when the target element is rendered?
Alternatively, is there some way to only add aria-describedby if aria-label does not exist?
The text was updated successfully, but these errors were encountered:
dweldon
changed the title
aria-describedby added too late?
Accessibility: aria-describedby added too late?
Feb 19, 2019
I was going to open this issue aswell. Can confirm that axe and Siteimprove accessibility checker chrome apps are flagging this as an issue also. It appears to me that the issue is that elements that have v-tooltip added to them have aria-describedby set to an id of a describing element (div) which is removed from the DOM tree after unhovering the element with tooltip.
v-tooltip
addsaria-describedby
to the target element, which is fantastic. However, it doesn't become enabled until the first trigger has happened... which makes the description initially not available to screen readers (at least not on Vox+chrome).aria-describedby
when the target element is rendered?aria-describedby
ifaria-label
does not exist?The text was updated successfully, but these errors were encountered: