RE: CFC - Issue 630 response


I like Mike’s response, and as we’ve discussed on the calls, on hover functionality can be difficult for people, such as those with tremors or other mobility issues. In addition, on hover functionality can be over-used and used improperly.

I like the whole last paragraph and think it should stand as is, because it calls out the fact that it can be a tricky interaction for some people, and perhaps nudges authors to be judicious in using it.

As will be made clear in the Understanding document, this SC is not recommending or encouraging the use of On Hover or On Focus as the trigger for displaying new content. This is considered a poor interaction by many, since users may easily inadvertently trigger new content. However, where an author elects to employ On Hover as a trigger, this SC places requirements on the implementation which make the resulting experience more accessible.

However, if we feel it would be best to reword so as not to conflict with other standards, that is reasonable. I would not want to lose the general idea that on hover can be problematic for some though, because that’s the point of this SC.


From: Andrew Kirkpatrick []
Sent: Tuesday, January 02, 2018 6:09 PM
Subject: CFC - Issue 630 response
Importance: High

Call For Consensus — ends Thursday January 4nd at 7:00PM Boston time.

The Working Group has discussed a response to issue 630 (

The specific response is at , and it was surveyed at and received minor edits during the call that are reflected in the proposed response in the wiki.

Call minutes:

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.


Andrew Kirkpatrick
Group Product Manager, Accessibility

Received on Thursday, 4 January 2018 19:43:21 UTC