<laura> me too.

<steverep> Hey folks, let me know if and when you might be on WebEx

<laura> It looks like jim and I are on WebEx now

<steverep> Thanks, Laura. I should be able to join shortly.

<laura> Okay.

<laura> https://www.w3.org/2002/09/wbs/35422/understanding_SC/results

<laura> Accepted WCAG 2.1 SC: https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

https://www.w3.org/WAI/GL/wiki/Comment_Summary_1-4-10

<shawn> Hi Alastairc and Allanj -- It looks like there is not a polycom in your room (Boardroom 2)

<shawn> I have informed the staff so hopefully there will be soon

<laura> https://lists.w3.org/Archives/Public/w3c-wai-gl/2017OctDec/0313.html

<laura> Overview of current comments: https://lists.w3.org/Archives/Public/w3c-wai-gl/2017OctDec/0313.html

<laura> Hi shawn

<laura> https://www.w3.org/WAI/GL/wiki/Special:RecentChanges

<laura> Comment Summary 1-4-10: https://www.w3.org/WAI/GL/wiki/Comment_Summary_1-4-10

<scribe> scribe: allanj

content on hover

proposals made. CfC requested

discussion bullet 1

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;

sr: discussion on repositioning. that is not the point of the SC. got some clarity on repositioning. When is repositioning ok when the other conditions cannot be met.
... dismissing hover content is still a bit of concern
... use case - error messages on validation. should not be an issue.

<laura> Nov 6 Content on hover or focus AG minutes: https://www.w3.org/2017/11/06-ag-minutes.html#item07

<laura> https://www.w3.org/2017/11/06-ag-minutes.html#item05

<steverep> Plain language transformation of 1st bullet: The additional content can be dismissed by the user without moving focus or hover, unless the infromation is critical or it doesn't obscrure anything.

channeling Al Gilman - Author proposes, user disposes.

or information is an input error.

sr: could turn it into SC language
... bullet 2 change handle to "hoverable"

<laura> Issue #565: SC Content on Hover or Focus: Hover/Focus to Hoverable/Persistent: https://github.com/w3c/wcag21/issues/565

sr: bullet 3, should appear on hover. on focus is covered by 2.1.1. removed reference to how the hover content is triggered. just say that hover content is persistent.
... discussion on exception - tooltip

<laura> Laura: Would have liked title attribute be included but know that it will liklely be pushed to sliver.

<steverep> AG discussed exception at some length. Some folks take position that if SC is important, there should be no exception. We know others disagree.

<steverep> LVTF can simply take position that we'll accept it either way, but obviously prefer it without the exception.

<laura> +1

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/top sliver./to sliver./
Present: Laura

WARNING: Fewer than 3 people found for Present list!

Found Scribe: allanj
Inferring ScribeNick: allanj

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 09 Nov 2017
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)