15:23:11 RRSAgent has joined #coga 15:23:11 logging to http://www.w3.org/2016/09/26-coga-irc 15:23:21 trackbot, start meeting 15:23:23 RRSAgent, make logs 389 15:23:25 Zakim, this will be 2642 15:23:25 ok, trackbot 15:23:26 Meeting: Cognitive Accessibility Task Force Teleconference 15:23:26 Date: 26 September 2016 15:23:34 rrsagent, make logs public 15:30:56 regrets Deborah Dahl, ayelet seeman 15:31:01 regrets: Deborah Dahl, ayelet seeman 15:36:23 agenda: this 15:36:24 agenda+ review SC, and timelines show status table ,sc todo list: https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/SC_todo_list, sc stus: https://rawgit.com/w3c/coga/master/extension/status.html, rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html 15:36:26 agenda+ review sc wording to get to pending 15:36:27 agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html agenda+ What have we missed for issues page 15:36:29 agenda+ be done 15:50:38 regrets: Deborah Dahl, ayelet seeman, John Rochford 15:54:44 kirkwood has joined #COGA 15:55:19 Thaddeus has joined #COGA 15:55:56 +Thaddeus presetn 15:56:04 +Thaddeus present 15:59:05 +kirkwood 16:00:10 Rich has joined #coga 16:02:13 Mike_Pluke has joined #coga 16:04:11 scribe: kirkwood 16:05:02 zakim, next item 16:05:02 agendum 1. "review SC, and timelines show status table ,sc todo list: https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/SC_todo_list, sc stus: 16:05:04 ... https://rawgit.com/w3c/coga/master/extension/status.html, rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html" taken up [from Lisa_Seeman] 16:05:35 https://rawgit.com/w3c/coga/master/extension/status.html, 16:05:51 Lisa: first thing is timeline, status and rewording doc. Some have been broken up. 16:06:29 Lisa: new document is status document 16:07:15 present + Mike_Pluke 16:09:09 https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/SC_todo_list 16:09:19 present + lisa 16:09:57 KurtM has joined #coga 16:13:29 maryjom has joined #coga 16:16:40 Sorry I should have mentioned that I can commit to making a Pull Request on my next SC task this week 16:18:27 EA has joined #coga 16:18:40 Mike: asking about user preferences 16:19:22 LS will work with JK and setup a meeting with Michael to move forward on testing for JK SC 16:21:50 No loss of data: The user can easily return to the same point in a task, without data loss, for a period of at least a week: 16:21:52 as the default, or 16:21:53 2. via a standardized system setting (for example, the user can choose an option that disables the storage of data) or 16:21:55 Mike: standardize information and user preference 16:21:55 3. as an use settable option that is available throughout the task. 16:23:14 Mike: services storing data in session and the restore of information. Standard system setting don’t let outside systems store data. It is a little unclear. 16:23:41 LS: could probably just say user set-able option 16:24:19 No loss of data: The user can easily return to the same point in a task, without data loss, for a period of at least a week, as the default, or via a user settable option that is available throughout the task. 16:24:36 LS: as a defaut it should be user settable 16:25:18 LS: does anyone disagree with getting this out the door? 16:25:26 LS: assuma a consensous 16:25:27 Timed text +1 16:25:46 LS: Timed text is ready to go 16:26:24 LS: Thaddeus are you ok with deadline, which is about a week? 16:26:37 Thaddeus: yes 16:27:01 LS: Kurt, how are your changes doing? 16:27:59 Kurt: sent an updated hyml file, sent you one in terms of modality and etsy timeframe for feedback. Could not find where the reference came from. How can you measure in terms of testing? 16:28:09 LS: you don’t want to say rapid feedback? 16:28:39 Kurt: how can you define rapid? for testing. 16:29:01 LS: could say immediate feedback 16:29:07 Kurt: good with that 16:30:00 LS: thinking we change to ‘main modality of the pplication’ or ‘primary modality of application’ 16:30:20 Kurt: think I agree with that thinking 16:31:27 Kurt’ let me take a look at the wording will make thos changes and send over as html 16:32:19 Mike: changing from rapid to immediate, seems untestable 16:33:07 Mke: 200 milliseconds people begin to wonder if a transaction went through 16:33:26 Mike; a lot of research went into that number in the past 16:33:39 LS: Kurt, are you comfortable with that? 16:35:25 Kurt: what about along the lines of feedback occurs in same timeframe as any error messaging 16:36:00 Mike: immediate should be quicker that 200 ms 16:37:02 Kurt: rountrip to server times that would be quick, but in browser that would be very slow 16:37:28 LS: if roundtrip to server it would be longer. 16:38:27 Mike: if you don’t get any feedback in 200 milliseconds the user should be alerted pssibly 16:38:37 Did you mean: 200 milliseconds etsy feedback 16:38:39 Search Results 16:38:40 TS 126 267 - V8.4.0 - Digital cellular telecommunications ... - ETSI 16:38:42 www.etsi.org/deliver/etsi_ts/126200_126299/126267/08.../ts_126267v080400p.pdf 16:38:43 Rich_ has joined #coga 16:38:43 ETSI. ETSI TS 126 267 V8.4.0 (2010-06). 1. 3GPP TS 26.267 version 8.4.0 Release 8. Reference ...... for the fast modulator mode (n = 0,…,15) and. )0000000000000040. 200. 560 ..... ms, which is the length of modulated feedback messages). 16:39:55 LS: so then it is reasonable you could say achieved within 200 ms unless there is technology delay, occsionally is acceptable. Occasional is not considered a violation 16:40:28 Kurt: I have a problem with testing of this if put a hard number on it. 16:41:17 Kurt: depends on external systems 16:42:51 Mkike: as the next possible activity 16:43:12 as the next as the next activity that affects the user 16:43:18 LS: as the next activity that effects the user 16:44:33 I need to leave the call early - Can commit to the deadline on my tasks 16:44:47 Can Commit 16:44:50 EA: one of the problems I sas the chunking had a testablity issue. I sent an email on that. I wasn’t quite sure what to do. I t just said testability in feedback. I wasn’t sure if should give precise details instead 16:45:22 EA: that was the one against COGA or WCAG included under techniquest 16:46:01 LS: one of the techniques below. Checking that the content confirsm with technique 16:46:29 EA: I have given all techniques below, common failures etc 16:46:58 LS: will those techniques be testable, will you be able to say decisively that they can do the technique? 16:48:22 LS: wan’t clear how to test how do you say this paragraph hss gone off topic 2.3.1? 16:49:06 EA: only way you could do that key words not there or change but might not be testable. 16:49:24 LS: could check that each sentence relates to keyword 16:49:49 EA: we have got this assumption that a key point is valid in one paragraph 16:50:20 LS: it should have an obvios relationshiip with keyword of a paragraph. Is that testable? 16:50:36 EA: I think it’s very hard 16:51:21 LS: could it be a clause of the sentence to check if everythin relates. A single point in the paragraph. 16:51:34 present+ Rich_Schwerdtfeger 16:51:50 EA: I think it is important but difficult to test. 16:52:17 LS: could we say keyword or key point in the paragraph? 16:52:56 LS: if it is not testable we can’t put it in 16:53:46 LS: I didn’t mean programatic keyword 16:54:38 EA: we are putting another layer on it may make it harder 16:54:58 LS: do you want to discuss it? 16:55:19 EA: I have familiar layout and need some assist 16:55:29 LS: send me some time in morning 16:55:38 EA: Wednesday morning ok? 16:55:49 LS: 10;30 or so 16:56:14 LS: your time 8:30 Wednesday morning 16:57:12 LS: need to mention feedback from WCAG, we need to make a case why its A or AA in benefits section. Without this it’s broken 16:57:58 LS: we are going to need to give justification of A or AA and it will then be clear on benefits. Each please check ouver the conformance level is justified 16:58:50 LS: next month we are going to make calls on Thursday. We are going to make it an hour later than usual. Is that ok? 16:59:02 LS: starting next week 16:59:12 q? 16:59:30 EA: when is the second one due by? 16:59:51 LS: moved to about a week and a day, everybody is talking about rewording 17:00:01 https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html 17:00:09 EA: have a got to apply that to the one I’ve already done? 17:00:13 LS: yes 17:00:27 LS: don’t hesitate to ping me on skype 17:00:48 EA: I was concerned about the chunking. 17:00:58 LS: changed modality of user and the content 17:01:07 EA: I’ll go ont the next one 17:01:27 LS: conformance change justification is important 17:02:13 LS: EO has volunteers to write up a bit about user case examples. As soon as we have something in green we’ll ask them to help to fill out. regardeing examples and justifications 17:02:14 Must drop for next meeting - thanks Lisa! 17:03:15 rrsagent, create minutes 17:03:15 I have made the request to generate http://www.w3.org/2016/09/26-coga-minutes.html Lisa_Seeman 17:03:22 zakim, please part 17:03:22 leaving. As of this point the attendees have been kirkwood, Rich_Schwerdtfeger 17:03:22 Zakim has left #coga 17:03:41 rrsagent, please part 17:03:41 I see no action items