- From: Jonathan Avila <jon.avila@levelaccess.com>
- Date: Tue, 15 Jan 2019 18:03:09 +0000
- To: "public-low-vision-a11y-tf@w3.org" <public-low-vision-a11y-tf@w3.org>
Received on Tuesday, 15 January 2019 18:03:34 UTC
I wanted to bring a question to the group that was raised on github (https://github.com/w3c/wcag/issues/582 ) on the WCAG 2.1 standard. "If pointer hover can trigger the additional content, then the pointer can be moved over the additional content". Is that the correct reading? I.e. if something like a drop-down menu is brought up by tabbing to it, there is no requirement that the user can move the pointer over it and interact with it? Is there a use case for the user to use the keyboard to display additional content and then need to move the mouse to it? I think so... I think there is a case where the user might bring something up with the keyboard and the item doesn't fit in the magnified area. The user may want to use the mouse to pan to the content -- but moving the mouse causes it to go away. The user then must move the point over the hover trigger then to get it to come up again but this causes the user to have to move out of the magnified area. What was our intent with this SC? Jonathan
Received on Tuesday, 15 January 2019 18:03:34 UTC