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
I'm not sure the following is actually a failure of WCAG.
<buttononhover="toggle('#tooltip')">
button
</button><divrole="tooltip"><spanid="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.
The text was updated successfully, but these errors were encountered:
I'm not sure the following is actually a failure of WCAG.
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.
The text was updated successfully, but these errors were encountered: