Skip to content
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

Accessibility: aria-describedby added too late? #191

Closed
dweldon opened this issue Feb 19, 2019 · 1 comment · May be fixed by ajesse11x/cms#3
Closed

Accessibility: aria-describedby added too late? #191

dweldon opened this issue Feb 19, 2019 · 1 comment · May be fixed by ajesse11x/cms#3

Comments

@dweldon
Copy link

dweldon commented Feb 19, 2019

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?
@dweldon dweldon changed the title aria-describedby added too late? Accessibility: aria-describedby added too late? Feb 19, 2019
@hrvojevu
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants