13:52:40 RRSAgent has joined #coga 13:52:40 logging to http://www.w3.org/2017/09/21-coga-irc 13:52:42 RRSAgent, make logs 389 13:52:42 Zakim has joined #coga 13:52:44 Meeting: Cognitive Accessibility Task Force Teleconference 13:52:44 Date: 21 September 2017 13:53:03 agenda: https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Sep/0022.html 13:53:07 chair: Jan_McSorley 13:53:21 regrets: Lisa_Seeman-Kestenbaum, Mike_Pluke 13:53:37 agenda+ Techniques for WCAG 2.1 support 13:53:46 agenda+ Comments on the Education and outreach document 13:57:11 scribeOptions: -final 14:00:32 JohnRochford has joined #coga 14:00:40 AndyHeath has joined #coga 14:01:42 present+ MichaelC, John_Kirkwood, John_Rochford 14:02:37 present+ Andy_Heath 14:03:59 present+ Jan_McSorley 14:04:07 present+ 14:04:21 rrsagent, make log world 14:04:44 present+ JohnRochford 14:04:46 Jan has joined #coga 14:06:28 scribe: MichaelC 14:07:18 zakim, next item 14:07:18 agendum 1. "Techniques for WCAG 2.1 support" taken up [from MichaelC] 14:07:29 https://docs.google.com/document/d/1YiknHDDDdKBdwVTEpxwUpyCaQL_tnpp9CfDlFjCq16E/edit# - Techniques 14:07:51 jms: ^ for techniques info 14:08:01 https://docs.google.com/document/d/13hmoaVU563kTio1EZD5mbNxcc0k924qVdZZwWckcbu0/edit# - understandings document 14:08:15 ^ for understanding material with some info about techniques 14:08:30 LS says we should look at WCAG 2.0 techniques for examples of techniques 14:08:41 https://www.w3.org/TR/WCAG20-TECHS/ 14:10:57 sample technique in the Timeouts (2) in above doc 14:11:48 when to use, description, examples, test, related techniques 14:12:21 I´m unclear if there is enough technical info 14:12:29 should we get feedback from developers? 14:14:00 is this enough? 14:14:11 can we ask AG participants for feedback? 14:14:15 mc: sounds ok 14:14:25 hard to say if this is technical 14:14:31 the SC is inherently not super technical 14:14:45 but the technique not clear about what it says to do beyond the SC wording 14:15:01 jms: maybe we can hash through the authentication technique 14:15:15 and get a feel for what makes a technical technique 14:16:25 jr: we pulled some of this from the Understanding doc 14:17:03 jms: let´s go back to top, accessible authentication 14:17:44 https://docs.google.com/document/d/13hmoaVU563kTio1EZD5mbNxcc0k924qVdZZwWckcbu0/edit 14:18:07 in Understanding, there are 3 techniques proposed 14:18:21 That URL is the understanding doc for the Accessible Authentication SC 14:18:26 so we need to create a full technique for each, for now just one 14:20:18 Actually, that URL is for all SC 14:21:01 JR, can you nominate a part of the Understanding to nominate as a technique? 14:21:25 jr: ¨essential steps which don´t rely on transcribing¨ 14:22:51 mc: that´s general understanding content, might need reflection in techniques, but we should look at the techniques section fornow 14:23:48 Pietro has joined #coga 14:23:54 Present+ 14:24:12 jr: a lot of that come from the original issue paper 14:24:27 mc: suggest we start with the first one, the others need to be translated into technique language 14:26:14 Michael: Techniques should be fairly granular for example, "allowing use of hardware tokens" 14:26:45 jr: if we get granular, we can´t write every possibility 14:27:34 mc: we don´t have to document every possibility 14:27:41 techniques aren´t required to conform to SC 14:27:54 we document the common ones we can think of, to provide guidance 14:28:10 should be very concrete for the ones we write up 14:29:47 ah: there are a lot of possibilities, too many for us to manage 14:29:58 mc: don´t need to write everything, can add more later 14:30:09 can document just titles for now, and flesh them out later 14:30:29 suggest we identify a couple per SC that have biggest bang-for-buck in implementation, or in understanding of the SC 14:30:58 laura has joined #coga 14:31:08 laura has left #coga 14:31:27 jms: having a link sent, simplifying title 14:31:51 jk: don´t simplify important stuff out 14:32:04 jr: other techniques cover other situations 14:33:14 jms: metadata is what? 14:34:08 mc: least important, it´s about technology technique applies to and whether it´s positive or failure technique 14:41:25 jms: need some documentation of the technique sections and how to use them 14:41:27 https://rawgit.com/w3c/wcag/refactoring/wcag20/sources/refactoring/technique-template.html 14:42:24 mc: will do documentation when I get the techniques set up for WCAG 2.1 14:42:41 above is template with some instructions I set up a year ago, that Lisa copied from to set up templates in the google doc 14:43:16 j[k|r]: would help to have a walk-through example along with the instructions 14:44:03 neilmilliken has joined #coga 14:45:37 mc: note the applicability (when to use) is mostly tautological, it´s something we had in the 2.0 techniques 14:47:58 jms: now for description, we want to look back at the Understanding draft for content that describes this technique 14:53:33 sorry for joining late what is the link to the document 14:55:31 14:55:34 https://docs.google.com/document/d/1YiknHDDDdKBdwVTEpxwUpyCaQL_tnpp9CfDlFjCq16E/edit# 15:03:05 Jan is going to write up a step-by-step guide, based on the work done this morning. There are a couple of sections left that need to be completed on the 1st authentication technique. Jan, Michael, and John Rochford will exchange emails to complete these sections and finish up the instructions. 15:14:56 EA has joined #coga 15:32:25 trackbot, end meeting 15:32:25 Zakim, list attendees 15:32:25 As of this point the attendees have been MichaelC, John_Kirkwood, John_Rochford, Andy_Heath, Jan_McSorley, kirkwood, JohnRochford, Pietro 15:32:33 RRSAgent, please draft minutes 15:32:33 I have made the request to generate http://www.w3.org/2017/09/21-coga-minutes.html trackbot 15:32:34 RRSAgent, bye 15:32:34 I see no action items