15:20:37 RRSAgent has joined #ag 15:20:37 logging to http://www.w3.org/2017/08/10-ag-irc 15:20:39 RRSAgent, make logs public 15:20:39 Zakim has joined #ag 15:20:41 Zakim, this will be WAI_WCAG 15:20:41 ok, trackbot 15:20:42 Meeting: Accessibility Guidelines Working Group Teleconference 15:20:42 Date: 10 August 2017 15:20:48 zakim, who is here? 15:20:48 Present: (no one) 15:20:49 On IRC I see RRSAgent, AWK, alastairc, laura, kirkwood, shadi, MichaelC, lisa, allanj, trackbot, yatil-focus, jasonjgw 15:20:51 +AWK 15:20:53 +AWK 15:20:56 zakim, who is here? 15:20:56 Present: AWK 15:20:57 On IRC I see RRSAgent, AWK, alastairc, laura, kirkwood, shadi, MichaelC, lisa, allanj, trackbot, yatil-focus, jasonjgw 15:21:02 Zakim, agenda? 15:21:02 I see nothing on the agenda 15:21:55 agenda+ Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11) 15:22:21 agenda+ Timeouts - Issue 14 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1 15:22:46 agenda+ Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 15:23:51 agenda+ reminders (Fill out survey, "present+" yourself in the meeting, TPAC registration/flight/hotel, find a time to scribe) 15:24:01 Zakim, agenda order is 4,1,2,3 15:24:01 ok, AWK 15:25:08 regrets+ Detlev, KathyW, Mike_Pluke, EA_Draffan 15:25:21 chriscm has joined #ag 15:26:58 interaccess has joined #ag 15:27:09 trackbot, start meeting 15:27:12 RRSAgent, make logs public 15:27:15 Zakim, this will be WAI_WCAG 15:27:15 Meeting: Accessibility Guidelines Working Group Teleconference 15:27:15 Date: 10 August 2017 15:27:16 ok, trackbot 15:27:34 Chair: Joshue 15:27:41 agenda? 15:28:15 AllanJ_ has joined #ag 15:29:05 KimD has joined #ag 15:29:21 Present+ KimD 15:29:52 scott has joined #ag 15:31:14 present+ alastairc 15:31:40 present+ 15:32:01 present+ 15:32:20 present+ Joshue108 15:32:54 present+ 15:33:07 david-macdonald has joined #ag 15:33:27 +AWK 15:33:35 JF has joined #AG 15:33:45 Present+ JF 15:33:50 Pietro has joined #ag 15:34:25 Rachael has joined #ag 15:34:31 present+ Rachael 15:34:37 Present+ 15:34:38 Alex has joined #ag 15:34:55 scribe: Alex 15:35:08 Scribe: Alex 15:35:39 present+ 15:36:03 present+ 15:37:11 zakim, take up item 1 15:37:11 agendum 1. "Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11)" taken up [from AWK] 15:37:25 zakim, agenda? 15:37:25 I see 4 items remaining on the agenda: 15:37:26 4. reminders (Fill out survey, "present+" yourself in the meeting, TPAC registration/flight/hotel, find a time to scribe) [from AWK] 15:37:26 1. Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11) [from AWK] 15:37:26 2. Timeouts - Issue 14 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1 [from AWK] 15:37:26 3. Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 [from AWK] 15:37:30 present+ David-MacDonald 15:38:26 awk please go through the entire survey 15:38:49 present+ Laura 15:38:50 present+ 15:38:53 awk please use present + at meeting 15:39:06 TPAC 6-10 NOVEMBER 2017 15:39:17 https://www.w3.org/2017/11/TPAC/ 15:39:18 awk please RSVP for TPAC 15:39:41 awk make your hotel booking sooner rather than later 15:39:44 Glenda has joined #ag 15:39:47 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:40:03 awk please sign up for scribing at TPAC 15:40:11 zakim, take up item 3 15:40:11 agendum 3. "Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13" taken up [from AWK] 15:41:09 q+ 15:41:13 Q+ 15:42:19 lisa Michael's issues that can be resolve 15:43:02 ack li 15:43:34 marcjohlic has joined #ag 15:43:36 lisa let's look at AA first 15:43:59 lisa hope Alex will be ok if he sees the technique 15:44:31 josh what do you mean by convention? 15:45:26 lisa button has to have a name that tells when the button does 15:45:37 q? 15:45:45 lisa will help autofill 15:47:11 zakim, ping me in 20 minutes 15:47:11 ok, Joshue108 15:47:25 lisa let's go over the conditional approval comments first 15:47:37 ack jf 15:47:42 ack l 15:48:12 The 2 objections were from MichaelG and Alex, both to do with including a schema/listing with the SC. 15:48:42 jf author is supposed to use a fixed taxonomy 15:49:46 jf you can use many different ways to meet the AA 15:50:06 jf fixed taxonomy is aimed for AAA 15:51:18 josh most comments are concerned about binding nature. A use case would be helpful. 15:52:50 jason this is more about question for the working group. concern about internationalization 15:53:07 present+ 15:53:11 jason, would this work for AT? 15:53:15 Q+ to address Jason's question 15:53:31 q+ 15:53:31 thanks for that Alastair. 15:54:38 jason seems more sensible to work on autocomplete 15:55:08 ack jf 15:55:08 JF, you wanted to address Jason's question 15:55:41 JF having author provide machine readable lookup table is optimal 15:56:05 JF but that is for AAA for now, because tech is not ready 15:56:34 q+ 15:56:37 JF use of ARIA is the easiest way to get there 15:57:14 JF since we don't have it, let's get some human readable way to help at AA 15:58:06 ack lisa 15:58:07 josh Mike and Alex have concerns 15:59:23 lisa tried to harmonize and achieve internationalization 15:59:39 I sent some examples which could turn into techniques to the COGA list: https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Aug/0010.html 15:59:50 Common Concept: (First Name) 16:00:00 Technique(s) for AA: (using @title) (Hebrew Example) 16:00:03 lisa we will work on techniques as we go 16:00:10 (using Microformats) 16:00:21 (using COGA Semantics) 16:00:38 of those 3, only the second and third would be sufficient for AAA 16:00:51 lisa let's put it in draft to see how it works for different language 16:02:11 alastair internationalization is an issue 16:02:32 s/alastair internationalization is an issue/alastair internationalization is an issue for the descriptions, not the tokens 16:03:47 jf we are introduce are things to look at 16:04:43 AL: I'll have to see the techniques. 16:05:12 q+ 16:05:30 ack jas 16:05:36 example using autocorrect for Postal Code: 16:05:39 josh let me take the temperature 16:06:09 jason i partly agree with john 16:07:11 jason the AA SC may present issues with internationalization 16:07:12 Joshue108, you asked to be pinged at this time 16:07:19 jason you are arguing over techneuqes 16:07:20 Q+ 16:07:28 jason prefer to hold off AA and work on the AAA 16:08:00 auto corect is one example of what is availible now 16:08:06 jason not sure this is ready for 2.1 16:08:12 widely availible 16:08:34 ack dav 16:08:58 david i see jason's concern but also sees the opposite 16:09:13 ack jf 16:09:28 jf we have a chicken and egg problem 16:10:17 jf proposing the human readable solution help break the problem 16:10:21 q+ 16:10:30 ack awk 16:11:09 awk support the idea, but the list is really long 16:11:11 I agree that the list needs to be trimmed significantly 16:11:19 q+ 16:11:28 awk can you shorten it 16:11:28 ack lisa 16:11:53 lisa only to include things in autocorrect 16:12:06 I think James asked they align, i.e. if there is overlap then use the HTML term. 16:12:30 josh i'm hearing support. techniques can be added 16:13:04 Before I would agree to this going in the draft I would need to see the editor's note that accompanies it 16:13:13 josh i think this is ready 16:13:15 BRB I +1 inclusion at AA and AAA with at risk note editor 16:13:16 Q+ 16:13:28 +1 16:13:31 +1 I am comfortable with this going forwarrd 16:13:34 ack jf 16:13:39 +1 16:13:40 +1 16:13:41 +1 16:13:53 jf will trying to get things ready 16:14:16 +1 with editors note - and more focussed list 16:14:24 0 I still have concerns about whether it makes sense to be broadly implemented. 16:14:39 awk want to see the editor's note 16:15:19 -1 for now 16:15:23 The techniques are important, but the principle that the techniques follow is that it is feasible at AA, so we don't need to specify techniques first. 16:15:58 +1 with editor's note 16:16:01 josh we have largely positive 16:16:32 +1 assuming editor's note is clarified before the end of the CFC 16:16:43 -1 16:16:58 +1 16:17:02 +1 16:17:10 Is this related to you wishing to Alex. 16:17:10 +1 16:17:10 Alex needs to see techniques 16:17:22 I posted some initial examples, perhaps Alex can look through later? 16:17:36 i also posted an example Postal Code: 16:17:42 i will look after the call 16:17:49 thanks Alex 16:17:58 michael we can pull thing after cfc 16:18:05 michael but we can't add 16:18:14 @Lisa: I think it's really cool that this came together. Good work. 16:18:37 thank you Chris, and everyone else who helped 16:19:22 michael please comment on CFC for objection 16:20:07 Lisa, would it be a good idea to put the list of terms in a google doc / sheet for group editing? 16:20:07 jf will have the note for Tuesday 16:20:45 @JF Marty McFly could! Come on man. 16:21:33 RESOLUTION: Accepted as proposed for the AA Personalization item, with an objection from Alex. 16:22:15 @alastair I'm down with that (google doc spreadsheet) 16:22:28 michael we ought to have separate cfc 16:22:51 josh thank you 16:23:40 can we separate? I thought the AAA one needed a bit of change. 16:24:08 ok 16:24:16 lisa can we edit after august 16:24:21 michael yes 16:24:21 +1 16:24:52 lisa we can remove region 16:25:41 +1 as well 16:25:45 +1 16:25:46 alastair can live with it 16:26:05 +1 16:26:16 +1 or -1 on AAA going to CFC 16:26:16 +1 16:26:16 +1 16:26:22 0 16:26:24 +1 16:26:32 +1 16:26:36 0 same concerns about whether it can be broadly implemented 16:26:48 +1 16:26:59 +1 16:27:17 +1 16:27:46 Thanks all the folks who helped with this 16:27:59 RESOLUTION: presonalization AAA accepted 16:29:22 awk who is caller 3 16:29:57 gowerm has joined #ag 16:30:00 present+ MikeGower 16:30:09 zakim, agenda? 16:30:09 I see 4 items remaining on the agenda: 16:30:10 4. reminders (Fill out survey, "present+" yourself in the meeting, TPAC registration/flight/hotel, find a time to scribe) [from AWK] 16:30:10 1. Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11) [from AWK] 16:30:10 2. Timeouts - Issue 14 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1 [from AWK] 16:30:10 3. Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 [from AWK] 16:30:42 SCribe: Laura 16:30:51 zakim, close item 3 16:30:51 agendum 3, Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13, closed 16:30:53 zakim, close item 4 16:30:54 I see 3 items remaining on the agenda; the next one is 16:30:54 4. reminders (Fill out survey, "present+" yourself in the meeting, TPAC registration/flight/hotel, find a time to scribe) [from AWK] 16:30:54 agendum 4, reminders (Fill out survey, "present+" yourself in the meeting, TPAC registration/flight/hotel, find a time to scribe), closed 16:30:55 I see 2 items remaining on the agenda; the next one is 16:30:56 1. Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11) [from AWK] 16:31:15 Josh: Good discussion on this. 16:31:27 q+ to discuss changes 16:31:40 …Steve has a new wording. 16:32:03 ack awk 16:32:03 AWK, you wanted to discuss changes 16:32:26 awk: I think all issues are resolved. 16:32:50 … the word popup is removed. 16:33:06 AWK updated Popup Visibility in survey. 16:33:47 …uses when content apears. 16:34:11 …triggred by a UI component. 16:36:13 q? 16:38:21 q+ 16:38:47 ack alex 16:41:21 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. 16:41:45 ……we don’t spec how. 16:42:04 alex: agree will most of this. 16:42:19 …3rd condition unnecessary. 16:42:34 …3rd condition unnecessary. 16:42:44 q? 16:42:53 q+ 16:43:42 q+ 16:43:47 …why wouldn’t 231 apply? 16:43:56 q- 16:44:07 present+ glenda 16:44:12 ack david 16:44:21 awk: explains. 16:44:27 alex: okay. 16:44:34 q? 16:44:47 david: I don’t mind the extra reminder. 16:45:13 josh: do people feel this is ready? 16:45:15 q+ 16:45:15 +1 I suggested a minor wording change, but happy in principle 16:45:18 q+ 16:45:24 +1 16:45:36 ack kim 16:46:46 kim: question custom tooltips 16:47:12 awk: lots of options to dismiss them. 16:47:39 …shouldn’t be an issue 16:47:59 kim: thinking about the layers. 16:48:08 ..should be okay. 16:48:17 ack gow 16:48:33 Need to indicate in the understanding document that activating a button that triggers a tooltip would be a fine way to dismiss the additional content 16:48:37 mg: understanding docs should mention 321 16:48:49 AWK did you see my most recent suggestion? Starting it "For content that becomes visible" 16:48:49 q? 16:49:02 Need to go into detail about where 2.1.1 / 3.2.1 / and this SC interact. 16:49:11 +1 ready 16:49:12 josh: hearing no objections. 16:49:15 +1 16:49:15 +1 16:49:18 +1 16:49:19 +1 16:49:30 +1 16:49:32 +1 16:49:45 +1 16:50:02 awk: steve had some objections. But I think he will be ok. 16:50:30 laura: +1 16:50:58 I can help you drop another? 16:51:24 RESOLUTION: Popup Visibility accepted for CFC 16:51:40 q+ 16:51:50 Zakim, next item 16:51:50 agendum 1. "Popup Visibility - #75 (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11)" taken up [from AWK] 16:52:19 TOPIC: Time Outs 16:52:33 Chaohai Ding 16:52:43 Current SC: Where data can be lost due to timeouts, users are warned at the start of a process about the length of inactivity that generates the timeout, unless the data is preserved for a minimum of 24 hours of user inactivity. 16:52:51 zakim, take up item 2 16:52:51 agendum 2. "Timeouts - Issue 14 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1" taken up [from AWK] 16:52:54 he has not been well unfortunatly so I am helping out\ 16:53:04 https://rawgit.com/w3c/wcag21/timeouts_ISSUE-14/guidelines/sc/21/timeouts.html 16:53:11 awk: AA 16:53:36 …Michael Elledge minor edit and wordsmithing 16:54:18 +1 16:54:19 MG: for forms time outs may be an issue 16:54:24 Kim has joined #ag 16:54:36 …outside the control of the author. 16:54:51 … worry about how "user inactivity" is measured. 16:55:14 …how does an author tell? 16:55:20 Mike: Where data can be lost due to user inactivity, users are warned at the start of a process about the length of inactivity that generates the timeout, unless the data is preserved for a minimum of 24 hours of user inactivity. 16:55:41 …rationale for 20 hours in the current 2.0 spec, that I find it disheartening to talk about extending it even more. Half of that time would be reasonable. 16:55:55 q+ 16:56:02 Q+ 16:56:03 ack lisa 16:56:09 …24 seems abritrary. 16:57:11 lisa: it can easily take people longer than 24 hours. 16:57:49 …people may need to continue the next day. 16:58:16 …does not require a calculation. 16:58:45 ack david 16:58:48 …a lot of COGA rationale for this. 16:59:14 inactivity? 16:59:39 …maybe add the word “Server” to time outs 17:00:30 AC maybe use inactivity. 17:01:41 Lisa: will change to user inactivity. 17:01:58 awk: should write the note for this one too. 17:02:52 JF: have some concerns that we haven’t talked about. 17:03:21 awk: we wil talk ablut this on tuesday. 17:03:33 zakim, who is on the phone? 17:03:33 Present: AWK, KimD, alastairc, jasonjgw, chriscm, Joshue108, scott, JF, Rachael, Pietro, shadi, David-MacDonald, Laura, lisa, kirkwood, MikeGower, glenda 17:03:33 Present+ 17:05:28 rrsagent, make minutes 17:05:28 I have made the request to generate http://www.w3.org/2017/08/10-ag-minutes.html laura 17:08:22 s/we wil talk ablut this on tuesday./we will talk about this on tuesday./ 17:08:36 rrsagent, make minutes 17:08:36 I have made the request to generate http://www.w3.org/2017/08/10-ag-minutes.html laura 17:12:29 laura has left #ag 18:06:18 KimD has left #ag 22:06:49 alastairc has joined #ag