RE: CFC - Content on Hover or Focus

This CFC puts me in the difficult position of accepting an SC I certainly agree will help PWDs, versus accepting unnecessary changes that have weakened it considerably.  In the short time this was revised, I have been commenting on GitHub [1,2,3], but could not participate in the call to voice my concerns.

I’m lobbying for 2 simple changes, and then I’d be a +1:

1.       Use “content” to describe the trigger rather than “user interface component”.  Reasons are explained on GitHub in detail, but in summary, there’s no reason to risk saying that we’re only covering UI components as triggers.  Anything can be a trigger, and that ought to be clear.

2.       Specify the parameters of the positioning, rather than just saying “can be repositioned”.  I proposed the following:

a.       Either the additional content does not obscure any essential content within the trigger, the additional content can be dismissed by the user, or the additional content can be positioned by the user to not obscure essential content of the trigger without requiring a specific pointer location.





From: Andrew Kirkpatrick []
Sent: Thursday, August 10, 2017 11:24 PM
To: WCAG <>
Subject: CFC - Content on Hover or Focus
Importance: High

Call For Consensus — ends Monday August 14th at 11:30pm Boston time.

The Working Group has reviewed and approved a new related Success Criteria for inclusion in the Editor’s Draft: Content on Hover or Focus, at level AA, with the goal of obtaining additional input external to the working group.

Call minutes:

The new SC can be reviewed here, in the context of the full draft:

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 Friday, 11 August 2017 15:06:25 UTC