15:27:39 RRSAgent has joined #coga 15:27:39 logging to http://www.w3.org/2017/06/19-coga-irc 15:44:08 kirkwood has joined #COGA 15:56:40 agenda: this 15:56:42 agenda+ review SC, and timelines show status table.sc status: https://rawgit.com/w3c/coga/master/extension/status.html, rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html agenda+ review sc wording to get to pending 15:56:43 agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, issues: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA 15:56:45 agenda+ accessible authentication 15:56:47 agenda+ personlization 15:56:48 agenda+ the supplement, moving forward 15:56:50 agenda+ What have we missed for issues page 15:56:51 agenda+ be done 16:01:18 scribe: kirkwood 16:01:43 present+ 16:02:09 JohnRochford has joined #coga 16:02:57 zakim, next item 16:02:57 agendum 1. "review SC, and timelines show status table.sc status: https://rawgit.com/w3c/coga/master/extension/status.html, rewording 16:02:59 ... https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html agenda+ review sc wording to get to pending" taken up [from lisa] 16:03:46 LS: next thing to put forward is personalization, next week afer accessbile authetification 16:03:53 zakim, next item 16:03:53 agendum 1 was just opened, lisa 16:04:03 zakim, close item 1 16:04:03 agendum 1, review SC, and timelines show status table.sc status: https://rawgit.com/w3c/coga/master/extension/status.html, rewording 16:04:05 ... https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html agenda+ review sc wording to get to pending, closed 16:04:05 I see 6 items remaining on the agenda; the next one is 16:04:05 2. Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, issues: 16:04:05 ... https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA [from lisa] 16:04:11 zakim, next item 16:04:12 agendum 2. "Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, issues: 16:04:14 ... https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA" taken up [from lisa] 16:04:29 zakim, close item 2 16:04:29 agendum 2, Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, issues: 16:04:31 ... https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA, closed 16:04:31 I see 5 items remaining on the agenda; the next one is 16:04:31 3. accessible authentication [from lisa] 16:04:37 zakim, next item 16:04:37 agendum 3. "accessible authentication" taken up [from lisa] 16:04:55 this is the one to get to, accessbile authentication 16:05:05 https://www.w3.org/2002/09/wbs/35422/COGA_Auth/results 16:05:10 LS: sent out a survey 16:05:27 LS: these are the survey results above 16:05:36 https://github.com/w3c/wcag21/issues/23 16:05:43 LS: issue 23 16:06:12 LS: one of the comments the new wording didn’t support all comments discussed in github 16:06:27 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Jun/0045.html 16:07:03 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Jun/0040.html 16:07:13 Mike_Pluke has joined #coga 16:07:22 LS: this is the thread regarding authentification, that was emeail to the summary that was said 16:07:27 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Jun/0045.html 16:07:31 https://github.com/w3c/wcag21/issues/23 16:07:36 https://www.w3.org/2002/09/wbs/35422/COGA_Auth/results 16:07:41 LS: putting links in for Mike 16:08:06 LS: survey results and comments and issues and tried to sum up what was wrtitten 16:08:22 LS: the link to archive 40 is the summary 16:09:01 LS: they wanted us to reach out to check if authentication, to writie to the web authentication people and check with them if they are comfortable with it 16:09:24 LS: John might want to respond to email earlier today 16:09:38 JR: to address feed back that givien? 16:10:01 LS: step one setup a call with athentication people to make sure not creating a problem. 16:10:40 LS: sent an email and think CC’d COGa if didn’t can write a repsonse and cc COGA to setup a call to make sure everyone is comfortable with the wording 16:11:14 LS: have you consulted experts?, they asked. then they will have a comfort level from an athentication andd security point of view 16:11:38 LS: need to get that happening before thursday 16:12:19 LS: another comment people didn’t feel every issue in the github comments had been addressed 16:13:21 JR: quite significant and not a simple answer 16:14:02 LS: tried to respond on call know lots of people use two step but its not usable by a lot of people 16:14:50 LS: like lots of places use catcha, don’t think thats legitimate as long as alternative 16:15:38 present+ 16:16:02 LS: not sure about the four characters with dyslexia 16:16:20 JR: not sure if four characters would work 16:17:31 JR: not sure how four characters could be an ok exception, where does four come from why not 5 or 3 16:18:39 LS: I would imagine dyslexic could use four, 16:18:57 action: johnrochford ansewer the four comment 16:18:57 Created ACTION-219 - Ansewer the four comment [on John Rochford - due 2017-06-26]. 16:18:58 LS: John could I ask you why not happy with four characters in github comments 16:19:37 JR: regarding commentary, what i’m worred about is my repsones not good for group. Mike could i run responses by you 16:19:42 Mike; yes 16:20:33 Mike’: with cognitive disability virtueall every authentication will fail one or another of our bullets on there. may be no conceivable alternatives I’m guessing out of this 16:20:42 LS: i don’t understand that 16:21:24 MP: what is alternative method that doesn’t break rules 16:21:30 LS: the link 16:21:41 LS: the link would be two step authetivation 16:22:31 JR: yes that is one 16:22:43 LS: that is the latnative 16:23:02 LS: that is the alternative 16:23:41 LS: a smart card, login through facebook, can do two step athentication, there a lots of alternatives available 16:24:21 LS: we are not trying to catch everyone, but these are alternatvies 16:25:11 LS: John and Mike if you could go through repsones on github that would be important 16:25:26 JR: what is the due date? 16:25:41 LS: if we don’t get in on Thursday won’t get through 16:25:58 MP: tomorrow I’m available 16:26:22 JR: I will address everythinkg i can today and I’ll send it to you 16:26:39 JR: should i respond to each comment or a master response? 16:27:25 LS: however you prefer, just make sure if you respond, make sure you tag with and @ sign so they will be told in comments 16:27:47 LS: looking over the survey will be very helpful 16:28:07 JR: survey you are referring to the questionnaire? 16:28:11 LS: yes 16:29:23 JR: if Mike and I can do the plan we talked about I expect the responses will be there tomorrow. The day before it will be addressed 16:30:15 LS: it is on the agenda for tomorrow not sure if on agenda for Thursday. If we can get it on for tomorrows meeting 16:30:45 MP: i can try and take a look this evening 16:32:41 MP: not clear what comment refers to, sounds like it needs to be reworded. 16:35:27 JR: there is a lot of feedback and worried about getting through it by tomorrow 16:35:54 LS: i’ll try repsonding to Alastair and if you want to join in that wold be fine 16:37:23 JR: can you see if you can get accessible authentivcation in thursday agens and a meeting with wb authetication group 16:37:26 action: lisa to try and set up the meeting with web authetifcation 16:37:27 Created ACTION-220 - Try and set up the meeting with web authetifcation [on Lisa Seeman-Kestenbaum - due 2017-06-26]. 16:38:12 LS: I’m going to try and respond to Alaisatars [inauudibele] and on email strings 16:39:22 LS: two other small things there was request for an aexcetpoin for places that interferes with legislation, any problems with that. Seems completely reasonable 16:39:36 LS: does anyone have a problem with that? 16:40:04 JR: i would think ti would be an exception 16:40:13 JR: what is the excetption? 16:40:31 JR: an example would be what? 16:41:23 LS: banking for example maybe has a character requerement of some number of characters 16:41:35 JR: thats ok if we need to do it to get through 16:41:42 Essential steps of an authentication process, which rely upon recalling or copying information, have alternative essential steps, and an authentication-credentials reset process, which do not rely upon recalling and copying information. 16:42:05 LS: think it should be an or intstead of and 16:42:11 yes 16:42:22 Is that ok with everyone? 16:42:39 should: Essential steps of an authentication process, which rely upon recalling or copying information, have alternative essential steps, OR an authentication-credentials reset process, which do not rely upon recalling and copying information. 16:43:42 Pietro has joined #coga 16:43:55 MP: it should be AND but it could be repeated. It would be rather wordy but possibly clearer 16:44:16 Essential steps of an authentication process, which rely upon recalling or copying information, have alternative essential steps which do not rely upon recalling and copying information, OR an authentication-credentials reset process, which do not rely upon recalling and copying information. 16:44:17 LS: will repeat to be unambiguos 16:44:41 Present+ Pietro 16:44:50 WebEx link is not working 16:45:07 Pietro I had difficulty too 16:46:27 Essential steps of an authentication process, which rely upon recalling or copying information, have one of the following: 16:46:28 -alternative essential steps which do not rely upon recalling and copying information, OR 16:46:30 - an authentication-credentials reset process, which do not rely upon recalling and copying information. 16:47:25 present+ 16:47:47 LS: i wll change, and put in github is that what we want tod do 16:47:56 present+ Mike_Pluke 16:47:58 MP: yes 16:48:13 I got WebEx by https://mit.webex.com/mw3200/mywebex/default.do?siteurl=mit 16:48:14 and I will add the exception for legislation 16:48:53 exception for law 16:48:54 LS: I’ll do that before tomorrow and add the excetion regarding law 16:49:07 legal requirement\ 16:49:46 LS: change to legal requirments 16:50:10 LS: reminding everyonw to fill on survey, if they see critical mass saying ready to go than the push to do that 16:50:41 LS: the questionnaire regarding to accessbile authentication 16:51:29 MP: maybe we should get acc ross that text has chenged and need to update responses 16:52:03 JR: asking about standard versus high risk login activity and haven’t addressed 16:52:25 LS: he wants us to address dangerous sensitive user data 16:52:59 LS: commentor wants us to exlude places with highr risk material 16:53:30 MP: we are sort of addressing this 16:54:17 MP: high risk is subjective 16:55:31 LS: there are smart cards, that is something they could provide regarding the big companies 16:56:42 JR: the other thing talked about is that copying and pasting also, how do we do that? 16:57:16 LS: could be bulooth authentification, or have link copy the number or press link 16:57:32 bulooth/bluetoooth 16:58:13 LS: while Mke on call Thursday 3pm uk. Endo of July switch calls then. 16:59:27 LS; keep this time through June and July and after July change call to 10 am EST on Thursday 17:00:55 LS: I really encourage you to join in on WCAG calls 17:03:51 rrsagent, make logs public 17:04:05 rrsagent, create minutes 17:04:05 I have made the request to generate http://www.w3.org/2017/06/19-coga-minutes.html lisa 17:04:16 https://docs.google.com/document/d/1MTZFb53lwSDLd8Z2ILvc-u5fBKUGEOoNOSrVxXu-PHo/edit#