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

Should aria-tooltip-name fail if it's not focusable? #4395

Open
WilcoFiers opened this issue Apr 3, 2024 · 0 comments
Open

Should aria-tooltip-name fail if it's not focusable? #4395

WilcoFiers opened this issue Apr 3, 2024 · 0 comments

Comments

@WilcoFiers
Copy link
Contributor

I'm not sure the following is actually a failure of WCAG.

<button onhover="toggle('#tooltip')">
  button
</button>
<div role="tooltip">
  <span id="tooltip" hidden> Hello world </span>
</div>

VoiceOver + Safari seems to ignore the empty tooltip, which I think it what it should do while not hovered. If other screen readers also ignore empty tooltips I don't think axe should fail them. Its worth testing if there's a difference when the tooltip is focusable. I assume that will announce the empty tooltip, which would be a problem.

Tooltips shouldn't normally be focusable so I'm a little conflicted about whether we should make this rule a best pracitce, or if this should incomplete when not focusable. Open for discussion, but we should run some AT tests first.

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

No branches or pull requests

1 participant