15:33:50 RRSAgent has joined #ag 15:33:50 logging to http://www.w3.org/2017/10/19-ag-irc 15:33:52 RRSAgent, make logs public 15:33:55 Meeting: Accessibility Guidelines Working Group Teleconference 15:33:55 Date: 19 October 2017 15:34:10 zakim, agenda? 15:34:10 I see 1 item remaining on the agenda: 15:34:11 2. Survey https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/ [from Joshue108] 15:48:24 alastairc has joined #ag 15:52:20 interaccess has joined #ag 15:57:56 present+ Joshue108 15:59:07 jimal has joined #ag 16:02:21 Glenda has joined #ag 16:02:28 present+ alastairc 16:02:32 present+ 16:03:12 present+ glenda 16:03:13 present+ 16:03:15 present+ 16:04:21 KimD has joined #ag 16:05:24 steverep has joined #ag 16:06:09 Scribe: Glenda 16:06:34 Zakim, who is here? 16:06:34 Present: jallan, JakeAbma, interaccess, bruce_bailey, Roy, Laura, jamesn, jasonjgw, Kathy, MikeGower, kirkwood, Makoto, KimD, Greg_Lowney, Mike_Elledge, Brooks, steverep, JF, 16:06:37 ... Katie_Haritos-Shea, Glenda, david-macdonald, marcjohlic, Detlev, Joshue108, alastairc, shadi__ 16:06:37 On IRC I see steverep, KimD, Glenda, jimal, Joshue108, alastairc, RRSAgent, Brooks, david-macdonald, marcjohlic, laura, shadi__, kirkwood, Roy, Ryladog, Zakim, MichaelC, jasonjgw, 16:06:37 ... yatil, trackbot 16:06:43 Zakim, next item 16:06:44 I do not see any more non-closed or non-skipped agenda items, Glenda 16:06:52 present+ Laura 16:07:02 Zakim, take up item 3 16:07:02 I only see 2 items on the agenda 16:07:20 Zakim, take up item 1 16:07:21 agendum 1. "Changes to Understanding document structure?" taken up [from Joshue108] 16:07:23 TOPIC: Response to comment on 2.4.11 Character Key Shortcuts #501 16:07:47 present+ 16:07:47 https://github.com/w3c/wcag21/issues/501 16:07:56 JF has joined #ag 16:08:04 present+ JF 16:08:09 present+ 16:08:34 https://github.com/w3c/wcag21/pull/512 16:09:09 Present+ 16:09:29 q? 16:09:45 Reviewing item 3 on the survey https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/ Response to comment on 2.4.11 Character Key Shortcuts #501 16:09:52 AWK has joined #ag 16:10:05 See: https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results#xnew2 16:10:07 rrsagent, draft minutes 16:10:07 I have made the request to generate http://www.w3.org/2017/10/19-ag-minutes.html AWK 16:11:15 11 accept as proposed with 3 comments requesting changes 16:12:01 zakim, ping me in 5 mins 16:12:01 ok, Joshue108 16:12:15 AWK: my suggestion is a rephrasing. “I think that this one should be handled more in line with the HTML5 spec for keyboard shortcuts. 16:12:15 If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content @@to activate or focus a control that is not currently focused@@, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key.” 16:12:40 Q+ 16:12:54 ack JF 16:13:34 JF: prefer that we use the wording “modifier key” 16:14:46 https://www.w3.org/2002/09/wbs/66524/20170920_survey/results#xq4 16:15:10 AWK: the character key question and modifier key is handled in the definiiton. We could make it clearer. But I think we should deal with that separately. 16:15:35 q? 16:15:44 Joshue: Can everyone live with this? 16:16:08 David: There are 3 proposals. One from David, one from Steve/Detlev, one from AWK 16:16:45 Q+ 16:17:01 +1 to andrew proposal 16:17:02 Joshue108, you asked to be pinged at this time 16:17:39 Original: If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key. 16:17:40 Detlev’s suggestion: would suggest to change the text from 16:17:40 "unless the character key is only active when a control has focus" 16:17:41 to 16:17:42 "unless the keyboard shortcut is only active when a control has focus" 16:18:02 Detlev's: If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key, unless the keyboard shortcut is only active when a control has focus 16:18:15 unless the character key is only active when a control has focus. 16:18:29 Steve's: If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key, unless the keyboard shortcut is only active when a particular user interface component has focus 16:18:40 AWK's: If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content @@to activate or focus a control that is not currently focused@@, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key. 16:19:34 +1 to Andrew's formulation. 16:19:43 q+ to say the current pull has my proposal in it 16:19:53 present+steverep 16:20:23 ack JF 16:21:16 JF: be consistent and use “control” or “user interface component”. Also have concerned about what a non-character key is. Will need a definition. 16:21:45 q+ 16:21:48 ack steve 16:21:48 steverep, you wanted to say the current pull has my proposal in it 16:21:55 Current pull request is http://rawgit.com/w3c/wcag21/resolve-issue-501/guidelines/#character-key-shortcuts 16:21:56 Joshue: I agree on consistency. Prefer “control”. 16:22:45 If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content @@to activate or focus a control that is not currently focused@@, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key, unless the keyboard shortcut is only active when a particular control component has focus. 16:22:59 Q+ 16:23:22 ack jason 16:23:51 Present+ Katie_Haritos-Shea 16:23:51 or If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content @@to activate or focus a control that is not currently focused@@, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key, unless the keyboard shortcut is only active when a particular user interface component has focus. 16:23:52 Jason: we use the term “user interface component” more consistenly then we use the word “control” 16:23:58 +AWK 16:24:36 John, what if we replaced "one non-character key" with "one key that is not a character key"? 16:24:39 character key definition: http://rawgit.com/w3c/wcag21/resolve-issue-501/guidelines/#dfn-character-keys 16:25:24 ack JF 16:25:28 q+ 16:26:12 JF: 26 references to user interface component and 30+ references to control. We need to tighten that up. We are using both terms. We need to standardize. 16:26:50 ack awk 16:28:23 AWK: the word “control” is in the definition of “user interface component”. So, we can look at this as a different item. Let’s focus on the proposed SC text that Josh has just written (see next). 16:28:24 s/30+ references/36 references 16:29:36 AWK: reconsider the contrstuction of my proposal. easier to read and easier to parse. 16:30:01 Joshue: can steve and detlev live with AWK’s proposal 16:30:05 If a keyboard shortcut consisting entirely of one or more character keys is implemented by the content to activate or focus a control that is not currently focused, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key. 16:30:18 Should Andrew's say "...to activate or ++give++ focus ++to++ a control that --is not-- ++does not++ currently have focus..."? 16:30:28 Steve: Yes. I can live with AWK’s proposal. 16:31:02 Q? 16:31:13 +1 16:31:14 Q+ 16:31:17 uses "focus" as a verb in mine, like in the HTML5 spec 16:31:20 Joshue: straw poll, who can live with AWK’s proposal? 16:31:21 +1 16:31:23 +1 16:31:25 +1 with a little clean up 16:31:27 +1 16:31:31 ack JF 16:32:33 JF: real problem is single key shortcuts. so the mechanism to turn it off, I can support that. But the remapping to multiple key shortcut that includes a modifier and another key. I’m not sure this is being conveyed. 16:32:56 Sorry, i have to depart now, I'll check the minutes later tonight. 16:34:23 then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key. (should be “at least one non-character key and a modifer key). 16:34:40 JF: need a modifer key plus 16:35:13 https://en.wikipedia.org/wiki/Control_character 16:35:27 modifier key for access key is controlled by the browser 16:36:35 single key (hot key) in a web application is controlled by the author in javascript ... not anything like accesskey 16:36:40 q+ to say Single character short cuts are not accesskey 16:36:41 ack me 16:36:41 Joshue, you wanted to say Single character short cuts are not accesskey 16:37:37 @JF, your concern is not with my text, but with the original SC text 16:38:01 JF: my concern with AWK’s language is that I could map the single character shortcut key of “L” to “CTRL”. It needs to require at least 2 keys (one being a modifier). 16:38:16 Joshue: need to leave this open, need to do more research, I think 16:39:01 AWK: I’m not seeing the issue that JF is raising is part of what we are trying to address here. There is a cascade problem here. 16:39:53 q+ 16:40:08 AWK: we need to address James comment first. Then we can address JF’s issue. One at a time. 16:41:06 +1 Josh 16:41:09 q- 16:42:16 Joshue: we need to have James and JF discuss this on Tuesday 16:42:43 RESOLUTION: leave open until Tuesday so JF and James can discuss and find a solution 16:42:53 I had to step out for a bit, back now 16:42:55 q+ to point out a possible loophole in AWK's proposal if the control is not immediately focusable? 16:42:59 agenda? 16:44:08 TOPIC: Device Sensors 16:44:54 https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results 16:45:08 https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results 16:46:25 1.4.12 User Interface Component Contrast (Minimum) #490 should be up next: https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results#xnew3 16:46:37 s/TOPIC: Device Sensors/ 16:47:03 AWK: TOPIC: UIC Contrast 16:47:12 TOPIC: UIC Contrast 16:47:35 david-macdonald has joined #ag 16:47:42 AWK: 5 people agree. 8 say not to accept this change. This will be a really hard one. 16:48:10 AWK: my suggestion is we discuss this at TPAC 16:48:13 q+ 16:48:23 Q+ 16:48:23 q+ 16:48:30 ack ste 16:48:30 steverep, you wanted to point out a possible loophole in AWK's proposal if the control is not immediately focusable? 16:48:50 ack jas 16:49:41 Jason: this is complex, will need to discuss this with colleagues more. 16:49:42 ack JF 16:50:30 JF: I support James in 3 to 1 being sufficient. 16:50:45 The need is real. LVTF reached out to Gordon Legge, Distinguished low vision researcher from the University of Minnesota. His recommendation is in my survey response. He summed it up by saying, "Bottom line: Contrast requirements for form controls should be equivalent to contrast requirements for text..." 16:50:45 ack dav 16:51:57 David: 2 sides and both have valid concerns. Testing burden on this would be high. Concerned about 3 way contrast for focus indicator. 16:52:24 Q+ to say many techniques to adjust focus indicator 16:52:31 David: probably need to take this up at TPAC 16:52:43 ack jim 16:52:43 jimal, you wanted to say many techniques to adjust focus indicator 16:53:23 q+ to say that this also covers selection color, such as in a listbox 16:53:29 ack AWK 16:53:29 AWK, you wanted to say that this also covers selection color, such as in a listbox 16:53:35 Jim: The 3 way contrast, there is always outline offset, to move it 3 pixels away, then you really are just dealing with a 2 color contrast (not 3). Or dashed lines, can get you to only need to be concerned about 2 colors. 16:54:16 q+ to say there are many many ways to avoid 3-way, and those may need normative changes to convey properly 16:54:40 If an author touches it, then they need to do it right. If they don't, then it's a browser issue and they are off the hook. 16:54:59 Jim: if the author didn’t make a change, then there is an exception. If they do make their own components, they need to make it visible. 16:55:04 ack steve 16:55:04 steverep, you wanted to say there are many many ways to avoid 3-way, and those may need normative changes to convey properly 16:56:03 Steve: There are so many ways in CSS to make things more distinguishable. You can completely avoid the 3 way contrast problem. We just need to work on how to avoide the 3 way contrast problem. 16:57:30 RESOLUTION: Leave UIC Contrast discussion for TPAC 16:57:34 TOPIC: Commit for Need an "AND" rather than "OR" in Purpose of controls #405 16:57:53 https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results#xcorrect 16:58:16 present+ david-macdonald 16:58:55 11 support, 2 suggest changes, 2 want more time or do not accept 16:59:17 https://github.com/w3c/wcag21/pull/406/files 16:59:21 q+ 16:59:57 Q+ 17:00:22 AWK: this is a simple change, and if we focus on the “OR” to “AND” 17:00:50 JF: I was involved in the writing of this SC. Intent all along was to say “AND” 17:01:20 Jason: agreeing with JF. Other issues are all separate from what this particular question. Looks like there is good support. 17:01:37 AWK: the other comments are important, but we will deal with the separately. 17:01:42 +1 17:01:55 RESOLUTION: Accept as proposed. Will ssend out CFC on this! 17:02:01 present+ marcjohlic 17:02:22 rrsagent, make minutes 17:02:22 I have made the request to generate http://www.w3.org/2017/10/19-ag-minutes.html Glenda 17:02:53 rrsagent, make logs public 17:03:05 trackbot end meeting 17:03:05 Zakim, list attendees 17:03:05 As of this point the attendees have been jallan, JakeAbma, interaccess, bruce_bailey, Roy, Laura, jamesn, jasonjgw, Kathy, MikeGower, kirkwood, Makoto, KimD, Greg_Lowney, 17:03:08 ... Mike_Elledge, Brooks, steverep, JF, Katie_Haritos-Shea, Glenda, david-macdonald, marcjohlic, Detlev, Joshue108, alastairc, shadi__, MichaelC, jimal, AWK 17:03:13 trackbot, end meeting 17:03:13 RRSAgent, please draft minutes 17:03:13 I have made the request to generate http://www.w3.org/2017/10/19-ag-minutes.html trackbot 17:03:14 RRSAgent, bye 17:03:14 I see no action items 17:03:14 Zakim, list attendees 17:03:14 As of this point the attendees have been jallan, JakeAbma, interaccess, bruce_bailey, Roy, Laura, jamesn, jasonjgw, Kathy, MikeGower, kirkwood, Makoto, KimD, Greg_Lowney,