Change Details

From our accessibility consultant we've received the feedback, that `role=tooltip` should only be used on static tooltip content. If the content has actionable items, it should be using a different role, to expose the interactivity clearly. [[ https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html#techniques | WCAG 2.1 ]] is not explicitly outspoken about it, but [[ https://github.com/w3c/aria-practices/issues/128#issuecomment-396276370 | this discussion provides a clearer feedback ]] on why it's not a good idea to have interactive elements or even ”complex structured content, as it's read out 'in a oner' by AT”. We should remove `role=tooltip`. In current state the previews are not properly exposed to screen readers anyways, as there's no machine-readable clear connection between the calling link and the preview, see T220777.

From our accessibility consultant we've received the feedback, that `role=tooltip` should only be used on static tooltip content. If the content has actionable items, it should be using a different role, to expose the interactivity clearly. [[ https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html#techniques | WCAG 2.1 ]] is not explicitly outspoken about it, but [[ https://github.com/w3c/aria-practices/issues/128#issuecomment-396276370 | this discussion provides a clearer feedback ]] on why it's not a good idea to have interactive elements or even ”complex structured content, as it's read out 'in a oner' by AT”. ==Update 2019-05-29 Changed from “Evaluate” to “Remove” due to the findings in resources above. We should remove `role=tooltip`. In current state the previews are not properly exposed to screen readers anyways, as there's no machine-readable clear connection between the calling link and the preview, see T220777.

From our accessibility consultant we've received the feedback, that `role=tooltip` should only be used on static tooltip content. If the content has actionable items, it should be using a different role, to expose the interactivity clearly. [[ https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html#techniques | WCAG 2.1 ]] is not explicitly outspoken about it, but [[ https://github.com/w3c/aria-practices/issues/128#issuecomment-396276370 | this discussion provides a clearer feedback ]] on why it's not a good idea to have interactive elements or even ”complex structured content, as it's read out 'in a oner' by AT”. ==Update 2019-05-29 Changed from “Evaluate” to “Remove” due to the findings in resources above. We should remove `role=tooltip`. In current state the previews are not properly exposed to screen readers anyways, as there's no machine-readable clear connection between the calling link and the preview, see T220777.