<Detlev> I can also do it

<gowerm> scribe gowerm

<shawn> scribe: gowerm

Persona quotes

<shawn> background: https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018May/0036.html

<shawn> draft: https://w3c.github.io/wai-intro-wcag/standards-guidelines/wcag/new-in-21/

<Detlev> sue

<Detlev> sure

<Detlev> scribe: Detlev

AWK: housing on 'what's new' resource

Shawn: EOWG Face2Face has been working on persona quotes
... draft was communicated - speak up if things are not alright
... intention to publish with 2.1 next week - once stable, add quotes to each understanding doc

<AWK> Issues: a. https://github.com/w3c/wai-intro-wcag/issues

AWK: use GitHub if you have issues with the persona quotes

goverm: Another topic was quick quote at the top - delay?

AWK: yes, postpone
... understanding not TR, can be changed more easily

<AWK> https://w3c.github.io/wcag21/understanding/

Understanding changes and CFC

AWK: We will still need to look at these - changing text, change links to draft techniques etc
... One comment received about 1.4.11 - if change of SC text goes through, what do we do with the understanding text?

goverm: fine what AWK proposed

AWK: proposal was editor's note explaining the late change
... comments?

Rachel: it that is the usual thing to do, seems fine

AWK: Understanding and Techniques will move to a different space
... More time to work on these
... alternative was to strip out text entirely and say it needs more revision

Detlev strip only out of date text?

<AWK> https://w3c.github.io/wcag21/understanding/non-text-contrast.html

AWK: Understanding text needs careful edition to align with new SC text (no longer mentioning visual boundary)
... opinions?

greg: Suggests including note and leave text unchanged for now

Detlev: suggests changing text to bring in line with SC

AWK: When will publishing happen?

Michael: Publishing will happen before Tue daytime

AWK: there is pull request for changes
... survey could be sent out to highlight Changs needed

<Chuck> +1

AWK: People seem OK with including editors note and at the same time trying to change understanding text to bring in line

RESOLUTION: Editor's to included note in 1.4.11 if language changes, and also to try to reach consensus on changes beforehand (thus eliminating the need for the note)

Hakim, take up next

Bleeding autocmplete

<Zakim> gowerm, you wanted to say I just +1'ed the CFC. have designer discussions to relate to group, if there's time

AWK: issue of whether a interactive control must be identified

goverm: Discussion with designers - thought there was concern by designers - the new language allows them to highlight what the key parts are to highlight interactive components / states

<JF> +1 to Mike's point about discussion with designers

Katie: did not see official response of LV TF but if they are OK with it will +1

AWK: (points to mail this morning)

<gowerm> It also lets us remove what was a pretty ugly piece of the understanding doc trying to explain about boundaries

<Ryladog> CfC +1

CfC of 1.4.11 is still open

AWK: Most think that changes address some concerns - Wilco disappointed that SC cannot be automatically tested now
... intent was not to force 3.1 for borders of all interactive components

Wilco: what does "required to identify" mean?

AWK: SC started with that focus needs to have good contrast too
... other things associated is realizing affordances that something can be activated at all -
... AWK analysis of Knowbility would be that while less than idea it does not fail

Wilco: text contrast is required, contrast on icons required so why is there a need for contrast on UI component?

AWK: Not all UI controls are simple controls - so it needs assessment in context - others have no text on them

JF: no there is no requirement for contrast on icon only controls so this is good for perception
... in its rest state borders around it can be less important - more so if it receives focus
... in some conditions default focus border may not be seen

<Zakim> gowerm, you wanted to give example of buttons

Wilco: Not happy, but if group is happy, OK

goverm: We cannot address all - depends on user testing - so if borders are removed, does it still work? Depeds on context as well
... there could be a flag for potential violation rather than straight fail

<Ryladog> +1

<AWK> Who will be at m-enabling?

AWK: question - how many go to M_Enabling conference?

<AWK> +1

<AWK> Kathy: +1

<Zakim> JF, you wanted to ask about updates to Contributors Section

JF: has sent comments to contributor section - will they be implemented before weekend?

MichaelC: yes, probably

AWK: referign to name changes, LevelAccess

MichaelC: will change that name

AWK: Change needed in Understanding as well

MichaelC: share same file

<AWK> https://github.com/w3c/wcag21/issues/937

Detlev: mentioning GitHub issue on pointer gestures

AWK: can probably be addressed in Understanding text

<gowerm> scribe: gowerm

trackbot, end meeting

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/Face2Face/EOWG Face2Face/
Succeeded: s/assign quotes to each understanding doc/once stable, add quotes to each understanding doc/
Default Present: AWK, MichaelC, Chuck, ShawnHenry(for_persona_quotes), JF, gowerm, alex, kirkwood, Katie_Haritos-Shea
Present: AWK MichaelC Chuck ShawnHenry(for_persona_quotes) JF gowerm alex kirkwood Katie_Haritos-Shea
Found Scribe: gowerm
Found Scribe: Detlev
Inferring ScribeNick: Detlev
Found Scribe: gowerm
Inferring ScribeNick: gowerm
Scribes: gowerm, Detlev
ScribeNicks: Detlev, gowerm
Found Date: 31 May 2018
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.)