Closed olaf-k closed 2 months ago
Closing this due to #6951. As mentioned by @chrisdholt this will have wide ranging effects I believe in how attributes are reflected on the host element from the template
element, in the Fluent UI web components we are working on better accessibility solutions, since cross root aria is such an issue I believe our solution there is to have the developer put a <button>
element into the default slot so that any aria
attributes are exposed as part of the light DOM.
Pull Request
π Description
This is an attempt at fixing the following:
aria-describedby
even when the attribute does not exist in the first placearia-describedby
when the tooltip is disconnectedaria-describedby
π« Issues
4 is a fix for #6442
π©βπ» Reviewer Notes
1 to 3 are straightforward and should not pose any issue hopefully.
to "solve" 4, moving
aria-describedby
to the custom element itself and addingrole="button"
seems to make the tooltip's text content picked up by screen readers.Caveat:
once you press Control-Option-Command-Slash as instructed, you are presented with a list of additional data:
there is a Safari ticket that discusses the issue but nothing Fast can do at this point: it is a VO limitation.
β Checklist
General
$ yarn change
Component-specific