Closed ferllings closed 1 year ago
Hello,
On non-interactive mode, the tooltip fails WCAG 1.4.13 criteria. https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html
Using interactive=true would allow the tooltip to be hoverable, but it removes aria-describedby attribute and incorrectly adds aria-expanded.
interactive=true
aria-describedby
aria-expanded
I'm trying to see, if I can change the default behaviour using the tippy Lifecycle Hooks, but it would be good if this is implemented by default.
Closing as already answered: https://github.com/atomiks/tippyjs/issues/750
Hello,
On non-interactive mode, the tooltip fails WCAG 1.4.13 criteria. https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html
Using
interactive=true
would allow the tooltip to be hoverable, but it removesaria-describedby
attribute and incorrectly addsaria-expanded
.I'm trying to see, if I can change the default behaviour using the tippy Lifecycle Hooks, but it would be good if this is implemented by default.