Success Criterion 1.4.14 Content on Hover or Focus

[GreggVan]

When content becomes visible when triggered by a user interface component receiving keyboard focus or pointer hover, the following are true, except where the visual presentation of the content is controlled by the user agent and is not modified by the author:

Visible trigger
Either the additional content does not obscure any essential content within the triggering user interface component, or the additional content can be closed or repositioned by the user.

Hover
If the additional content is triggered via pointer hover, then that content remains visible when the pointer is moved over it.

Focus
The additional content remains visible while the triggering user interface component has keyboard focus, unless the user dismisses the additional content.

NOTE
Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.

NOTE
Custom tooltips, sub-menus, and other nonmodal popups which display on hover and focus are examples of additional content covered by this criterion.

==================================================================
issue
You could satisfy the " visible trigger" provision by simply saying that the user can move off of the element. I don't believe that is the intent

POTENTIAL SOLUTION
add " without moving the focus or hover off of the trigger "to the end so that it reads

Visible trigger
Either the additional content does not obscure any essential content within the triggering user interface component, or the additional content can be closed or repositioned by the user without moving the focus or hover off of the triggering user interface element.

[steverep]

You could satisfy the " visible trigger" provision by simply saying that the user can move off of the element. I don't believe that is the intent

The criterion is specific to only be applicable "when additional content becomes visible" in order to mitigate any claim like that. This can certainly be emphasized in Understanding so I'll make a note to do so.

[GreggVan]

you missed my what I was pointing out The person points to something which causes additional content to become visible, thus triggering this SC. However the person can simply move the pointer off of that item and the visible content will disappear thus satisfying the SC. So there is actually nothing that the authors required to do, because a user can always move away from the item. Do you see what I mean? Am I missing something?

…

On Sep 6, 2017, at 3:07 PM, Steve Repsher ***@***.***> wrote: You could satisfy the " visible trigger" provision by simply saying that the user can move off of the element. I don't believe that is the intent The criterion is specific to only be applicable "when additional content becomes visible" in order to mitigate any claim like that. This can certainly be emphasized in Understanding so I'll make a note to do so. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#350 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJph3oACQgr_AHyHVj7T0q6POSaSk-1Sks5sfu1ngaJpZM4PJrlD>.

[steverep]

I did see your point, but I thought the criterion had it covered. On second thought, I agree with you. This is an artifact of adding the ability to close the content later on as satisfactory, which was not in the original language. The closing mechanism is meant to be an action without moving focus or pointer as you said, such as a button or pressing ESC. Thanks for catching this.

[steverep]

@GreggVan, pending working group approval of pull request #569, the proposed new language should address your issue.

[GreggVan]

Looks good

…

On Dec 6, 2017, at 3:55 AM, Andrew Kirkpatrick ***@***.***> wrote: Closed #350 <#350> via #569 <#569>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#350 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJph3r1rclnZbfK3K1-FHeQxyJMWitLdks5s9gIFgaJpZM4PJrlD>.