css-meeting-bot
commented
2 months ago The ARIA Authoring Practices (APG) Task Force just discussed Feedback on Tooltip Pattern Language.
The full IRC log of that discussion
<jugglinmike> Topic: Feedback on Tooltip Pattern Language<jugglinmike> github: https://github.com/w3c/aria-practices/issues/3109
<jugglinmike> Matt_King: there's a note in the tooltip pattern about the mouse-dismiss behavior
<jugglinmike> Matt_King: The reporter has suggested that the way we worded the second note in the tooltip pattern doesn't conform with WCAG
<jugglinmike> Matt_King: I don't think that was our intent, but it is vague when it says "on mouseout" (not "on mouseout of the tooltip")
<jugglinmike> Matt_King: I wonder if other people interpret this language in the way that the person who raised this issue interprets it
<jugglinmike> Matt_King: The language of concern: "If the tooltip is invoked when the trigger element receives focus, then it is dismissed when it no longer has focus (onBlur). If the tooltip is invoked with mouseIn, then it is dismissed with on mouseOut."
<jugglinmike> Matt_King: "invoked with mouseIn" -- I interpret that to mean that the user hovers over the element that displays the tooltip
<jugglinmike> Matt_King: "on mouseOut", that sounds like the mouse moving out of the element that triggers the display of the tooltip, but that is not what WCAG requires, right?
<jugglinmike> Matt_King: WCAG requires that you can move the mouse into the tooltip itself and the tooltip won't disappear
<jugglinmike> jongund: We should probably write about the "pointer" rather than the "mouse", but that's a separate issue
<jugglinmike> jongund: But the reporter's issue makes sense to me
<jugglinmike> jongund: It's doubtful that the triggering element and the tooltip itself will be contiguous, so there may need to be some kind of delay to allow the pointer to travel from the triggering element to the tooltip
<jugglinmike> Matt_King: It would be helpful to have some wording which captures the precise "dismiss" conditions
<jugglinmike> Matt_King: I wonder if WCAG already has some wording to this effect
<jugglinmike> Adam_Page: I don't think it does
<jugglinmike> Adam_Page: I think the reporter would be satisfied with a clarification that users can mouse into the tooltip content without dismissing the tooltip
<jugglinmike> Adam_Page: Because I think they're coming from a place of good faith where the tooltip content is adjacent to their trigger
<jugglinmike> Matt_King: Does anyone want to propose some wording?
<jugglinmike> Adam_Page: I'd be glad to take this on
<jugglinmike> Matt_King: Thank you, Adam_Page! If you just want to make a proposal in the issue itself, then we can get aligned with the reporter and with each other, and then that makes it easier for anyone to pick it up as a formal pull request
<jugglinmike> Matt_King: I've assigned you, Adam_Page
<jugglinmike> Matt_King: Thanks, everyone! Have a great rest of your day, wherever you are
<jugglinmike> Zakim, end the meeting
WW3
https://www.w3.org/WAI/ARIA/apg/patterns/tooltip/
The 2nd item of the note in the APG page ("If the tooltip is invoked when the trigger element receives focus, then it is dismissed when it no longer has focus (onBlur). If the tooltip is invoked with mouseIn, then it is dismissed with on mouseOut."), does not align with the "Hoverable" truth "If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing"