13:26:30 RRSAgent has joined #coga 13:26:30 logging to http://www.w3.org/2016/07/25-coga-irc 13:27:55 agenda: thisagenda+ review actions, and timelines agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html#table3 and logsagenda+ What have we missed for issues page agenda+ be done 13:28:16 agenda: this 13:28:18 agenda+ review actions, and timelines 13:28:19 agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html#table3 and logs 13:28:21 agenda+ What have we missed for issues page 13:28:22 agenda+ be done 14:20:25 Lisa_Seeman_ has joined #coga 15:29:40 Lisa_Seeman_ has joined #coga 15:33:46 Lisa_Seeman has joined #coga 15:43:44 JohnRochford has joined #coga 15:56:26 next item 16:01:02 Mike_Pluke has joined #coga 16:03:30 scribe: Mike_Pluke 16:03:53 ddahl has joined #coga 16:04:01 https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open 16:06:37 About action item #153, Mike says it is difficult to compare and map the ISO doc to the work we are doing 16:07:11 Mike: It's very comprehensive and high level. 16:08:53 Mike: One problem is we don't have the most up-to-date version of the ISO doc. 16:09:16 KurtM has joined #coga 16:10:29 Mike: What I'm trying to determine is if there are issues addressed in the ISO doc that we have not addressed. 16:10:51 present+ 16:10:57 present+ Lisa Seeman 16:11:08 present+ JohnRochford 16:11:34 present+ DebbieDahl 16:11:49 present+ Lisa_Seeman 16:11:53 present+ Mike_Pluke 16:11:53 present+ KurtM 16:14:13 issue paper on user testing and ethics for cognative - with Neil - Leave Open 16:14:24 thaddeus has joined #COGA 16:14:33 + Thaddeus 16:14:47 Review user research on emotioal disabilities - Lisa has done 16:14:56 next item 16:16:11 https://rawgit.com/w3c/coga/master/gap-analysis/table.html 16:16:27 Lisa finished small action items 16:17:02 EA has joined #coga 16:17:02 Table 3: Entering data, error prevention & recovery 16:17:21 https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html 16:18:08 q+ 16:18:36 Changed: definition in the semantics - coga-explain 16:19:48 Changed: definition in the semantics - logs (breadcrumb type information) - to make it interoperable 16:20:10 Could be in the header of the webpage - so exposed to the browser 16:21:17 Logs can have a name and multiple named steps, etc. 16:21:18 buy ticketbought ticket to NY returnurl 16:21:20 hotelbooked Sheraton single roomurl 16:21:21 car rental 16:21:23 16:22:47 q? 16:22:56 Ack John 16:24:08 Interactive controls are visually clear or visually clear controls are easily available that conform to the following: 16:24:47 John's question is "Do we expect coga explain will end up in AAA?" 16:27:50 present+ Janina 16:28:10 q+ 16:29:21 Mike "The scope for when coga-explain may be required needs to be defined - to avoid it definitely being AAA" 16:29:33 https://rawgit.com/w3c/coga/master/extension/index.html#interactive-controls-are-visually-clear-or-visually-clear-controls-are-easily-available-that-conform-to-the-following 16:29:47 https://rawgit.com/w3c/coga/master/extension/index.html 16:30:32 Rich has joined #coga 16:31:53 q? 16:32:02 ack johnr 16:32:06 present+ Rich_Schwerdtfeger 16:37:25 If we have the log, do we still need feedback? 16:37:31 q? 16:37:59 Does the log appear in a different place to the feedback? 16:38:29 Rich also says that feedback has a timely component 16:39:48 Having the log does not avoid the need to consider feedback as a separate topic (even though it may be linked to the logging function) 16:41:19 Moved onto "I need to know what mistake I made and how to correct a mistake. It does not scare me I need to make the correction easily" 16:43:05 q+ to ask if we want to distinguish between system detectable mistakes and mistakes that only the user can detect (e.g. I picked wrong departure city in air travel application) 16:44:39 q? 16:44:42 ack dd 16:44:42 ddahl, you wanted to ask if we want to distinguish between system detectable mistakes and mistakes that only the user can detect (e.g. I picked wrong departure city in air travel 16:44:45 ... application) 16:46:07 Debbie questions whether necessary to specify different types of errors i.e. choosing a destination that is valid but not the wanted one 16:48:21 3.3.1 refers to mistakes that the system can detect (i.e. invalid). Need to be able to identify your error and be able to go back and change without losing other information already entered 16:49:27 Need to be able to make the change throughout the duration of the "activity" 16:50:04 The mecanisim should be easily availible though out the activity 16:52:38 Under terms you have this statement "clearly indicated success or failure confirm that after a user action the user known that the action was successful or not. Applications should also let the user know what just happened and where they are in a process." 16:53:31 I think you meant 'knows' but is this what you need to make it clear? 16:58:26 sorry microphone not working. 16:59:35 It is in the Terms 17:01:54 Text EA quoted should be in the success criteria - not in the terms 17:02:55 Thank you - bye 17:03:05 ddahl has left #coga 17:03:23 rrsagent, make logs public 17:03:30 rrsagent, create minutes 17:03:30 I have made the request to generate http://www.w3.org/2016/07/25-coga-minutes.html Lisa_Seeman 17:15:19 what about Arnaud? 19:11:39 Rich has joined #coga 19:15:06 Lisa_Seeman_ has joined #coga 20:03:05 Rich has joined #coga 20:57:01 Rich has joined #coga 21:38:31 Rich has joined #coga