Re: CFC - Updated Response to issue 650/655/695/711 on Content on Hover or Focus

+1 
Okay I am withdrawing my -1. Steve is correct that my concerns are 
strictly editorial.
However, I do think a number of people have now commented on the 
difficulty of parsing the latest text, so I am very wishful that this text 
get tweaked. I am happy to be one of the ones working on it offline.

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   Michael Gower/CanWest/IBM
To:     Andrew Kirkpatrick <akirkpat@adobe.com>
Cc:     WCAG <w3c-wai-gl@w3.org>
Date:   2018-01-18 08:21 AM
Subject:        Re: CFC - Updated Response to issue 650/655/695/711 on 
Content on Hover  or Focus


-1 Sorry, but the SC preliminary text is incomprehensible now. I tried 
taking a stab at correcting this, but I don't like my version. 

> Where receiving pointer hover or keyboard focus triggers additional 
content to become visible, and removing hover or focus causes the 
additional content to be hidden, the following are true: 

Perhaps if the additional content become the subject of the text?

I don't understand why the accommodation was made for 650, since a tab 
panel's content is updated on activation, not on hover. What that comment 
may have exposed is that some things like tab items may be authored to 
include hover as well as selection as a means of updating the tabpanel. If 
that is the case, this SC needs to be revamped to clarify that it is the 
dependency on hover to expose information that needs to be addressed.

Here's a revision that I think addresses both issues:

> When additional content is revealed or hidden based solely on a trigger 
item receiving keyboard focus or pointer hover, the following are true:




Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034




From:   Andrew Kirkpatrick <akirkpat@adobe.com>
To:     WCAG <w3c-wai-gl@w3.org>
Date:   2018-01-17 04:09 PM
Subject:        CFC - Updated Response to issue 650/655/695/711 on Content 
on Hover  or Focus



Call For Consensus — ends Friday January 19th at 7pm Boston time.
 
The Working Group has discussed responses to the following issues:
650: (https://github.com/w3c/wcag21/issues/650)
655: (https://github.com/w3c/wcag21/issues/655)
695: (https://github.com/w3c/wcag21/issues/695)
711: (https://github.com/w3c/wcag21/issues/711)
 
Response to Issue 650: 
https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#650

Response to Issue 655: 
https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#655

Response to Issue 695: 
https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#695

Response to Issue 711: 
https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#711

 
The changes to the SC are implemented in this pull request: 
https://github.com/w3c/wcag21/pull/739

The changed SC can be viewed here: 
http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#content-on-hover-or-focus

 
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.
 
Thanks,
AWK
 
Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 
 
akirkpat@adobe.com
http://twitter.com/awkawk