15:33:24 RRSAgent has joined #coga 15:33:24 logging to http://www.w3.org/2017/05/22-coga-irc 15:44:06 agenda: this 15:44:08 agenda+ actions: https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open 15:44:09 agenda+ TPAC 15:44:11 agenda+ wording calls - review SC, and timelines status: https://rawgit.com/w3c/coga/master/extension/status.html, 15:44:12 other usefull links rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html 15:44:14 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:44:16 agenda+ plain lang http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0103.html 15:44:17 agenda+ help and support http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0098.html https://github.com/w3c/wcag21/issues/32 15:44:19 agenda+ Supplement : https://docs.google.com/document/d/19CvGpbNn1MecK9iRO7MOhafCaVjIajyV2BjNz2OZZZY/edit# 15:44:20 agenda+ What have we missed for issues page agenda+ be done 15:50:02 JohnRochford has joined #coga 15:50:22 present+ JohnRochford 15:56:55 4x now, WebEx has hung up and called me back 16:05:34 Mike_Pluke has joined #coga 16:05:55 kirkwood has joined #COGA 16:06:40 scribe: Mike_Pluke 16:06:48 zakim, next item 16:06:48 agendum 3. "accessible authentication" taken up [from lisa] 16:07:15 topic: tpac 16:07:34 https://www.w3.org/2017/11/TPAC/ 16:09:29 TPAC is in San Francisco. Mike can't make it, John Rochford might be able to. John Kirkwood and Thaddeus can. 16:11:07 kirkwood_ has joined #COGA 16:13:32 https://github.com/w3c/wcag21/issues/23 16:16:10 Mike queried whether our new proposed SC would replace the existing AAA SCs as several techniques were already associated to these SCs 16:20:28 Jan has joined #coga 16:20:53 lets get what we have to coga end f this week and propos it in 3 weeks to wcag 16:22:33 http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0095.html 16:23:11 kirkwood has joined #COGA 16:23:13 Provide words or phrases or abbreviations that are the most-common form to refer to the concept 16:23:38 Plain language - Suggesting a tool that can present the most commonly used words from a language. 16:24:00 google ingram in a common tool 16:24:19 Most famous tool and Google engram? 16:25:00 Google Ngram articles: https://www.google.com/search?q=google+ngram&oq=google+n&aqs=chrome.0.69i59j0j69i60l3j69i57.2247j0j7&sourceid=chrome&ie=UTF-8 16:29:52 scribe: JohnRochford 16:29:57 Jan: Help SC is not in great shape because we can find the research we need. 16:31:07 Jan: Recent search found new abstract requirements reveals a length of 100 words. 16:31:32 https://github.com/w3c/wcag21/issues/32 http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0098.html 16:32:31 Help and support: comprehension support is available via: 16:32:33 =Charts, tables, or graphics to summarize [complex numerical information]; 16:32:34 =Summaries of [long documents]; 16:32:36 =Emphasis of key words in [long documents]; 16:32:37 =Instructions for [non-standard controls]; 16:32:39 =Information about a user's position in multi-step forms; 16:32:39 present+ 16:32:40 =Alternative terms for relative and cardinal directions; 16:32:42 =Non-numerical versions of numerical values. 16:32:59 present+ 16:33:37 Jan: What do we think about emphasizing keywords rather than document length? 16:34:16 Lisa: Help SC is now more testable than it was. 16:34:58 Michael: If you have to have a summary for every little thing, the working group will reject. 16:35:51 Michael: Last I saw was 300 words, which won't catch too many web pages. 16:36:54 note that content that does not have 16:36:54 Lisa: Should we have scope statements or exceptions? 16:37:54 Michael: Each bullet could be its own SC, but we are trying to make things easier by combining. 16:39:44 Michael: A complex SC wording for a minor increase in scope may not get through the AG working group. 16:40:36 Michael: Perhaps we could define what complex wording is. 16:41:06 Jan: People do not know how they could define what complex wording is. 16:42:27 Michael: Word length is very variable across languages. 16:43:06 Mike said the above, not Michael. 16:43:50 Jan: Do we have a research basis for the terminology/wording we are using? 16:45:09 Michael: The lower the author burden, the fewer requests for research backing there will be. 16:46:56 present+ 16:48:01 Michael: I'm trying to simplify the SC for acceptance by the AG working group. 16:49:05 Help and support: comprehension support is available via one of the following 16:49:15 Michael: The more complex the wording of an SC, the less likely it will be accepted. 16:52:38 Michael: Maybe it should be "at least one of the following". 16:53:12 Jan: The complexity of the text would determine how many could be done. 16:55:40 Michael: We could say only one is required, but authors could follow as many as they want. 16:59:31 I'm signing off. 17:12:02 https://github.com/ayelet-seeman/coga.personalisation 17:38:52 rrsagent, make logs public 17:39:08 rrsagent, create minutes 17:39:08 I have made the request to generate http://www.w3.org/2017/05/22-coga-minutes.html lisa 17:39:42 zakim, please part 17:39:42 leaving. As of this point the attendees have been JohnRochford, kirkwood, lisa, Mike_Pluke, janina, MichaelC 17:39:42 Zakim has left #coga 17:40:01 rrsagent, please part 17:40:01 I see no action items