IRC log of coga on 2016-07-25
Timestamps are in UTC.
- 13:26:30 [RRSAgent]
- RRSAgent has joined #coga
- 13:26:30 [RRSAgent]
- logging to http://www.w3.org/2016/07/25-coga-irc
- 13:27:55 [Lisa_Seeman]
- 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 [Lisa_Seeman]
- agenda: this
- 13:28:18 [Lisa_Seeman]
- agenda+ review actions, and timelines
- 13:28:19 [Lisa_Seeman]
- agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html#table3 and logs
- 13:28:21 [Lisa_Seeman]
- agenda+ What have we missed for issues page
- 13:28:22 [Lisa_Seeman]
- agenda+ be done
- 14:20:25 [Lisa_Seeman_]
- Lisa_Seeman_ has joined #coga
- 15:29:40 [Lisa_Seeman_]
- Lisa_Seeman_ has joined #coga
- 15:33:46 [Lisa_Seeman]
- Lisa_Seeman has joined #coga
- 15:43:44 [JohnRochford]
- JohnRochford has joined #coga
- 15:56:26 [Lisa_Seeman]
- next item
- 16:01:02 [Mike_Pluke]
- Mike_Pluke has joined #coga
- 16:03:30 [Lisa_Seeman]
- scribe: Mike_Pluke
- 16:03:53 [ddahl]
- ddahl has joined #coga
- 16:04:01 [Lisa_Seeman]
- https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open
- 16:06:37 [JohnRochford]
- 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 [JohnRochford]
- Mike: It's very comprehensive and high level.
- 16:08:53 [JohnRochford]
- Mike: One problem is we don't have the most up-to-date version of the ISO doc.
- 16:09:16 [KurtM]
- KurtM has joined #coga
- 16:10:29 [JohnRochford]
- 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 [JohnRochford]
- present+
- 16:10:57 [Lisa_Seeman]
- present+ Lisa Seeman
- 16:11:08 [JohnRochford]
- present+ JohnRochford
- 16:11:34 [ddahl]
- present+ DebbieDahl
- 16:11:49 [Lisa_Seeman]
- present+ Lisa_Seeman
- 16:11:53 [Mike_Pluke]
- present+ Mike_Pluke
- 16:11:53 [KurtM]
- present+ KurtM
- 16:14:13 [Mike_Pluke]
- issue paper on user testing and ethics for cognative - with Neil - Leave Open
- 16:14:24 [thaddeus]
- thaddeus has joined #COGA
- 16:14:33 [thaddeus]
- + Thaddeus
- 16:14:47 [Mike_Pluke]
- Review user research on emotioal disabilities - Lisa has done
- 16:14:56 [Lisa_Seeman]
- next item
- 16:16:11 [Lisa_Seeman]
- https://rawgit.com/w3c/coga/master/gap-analysis/table.html
- 16:16:27 [Mike_Pluke]
- Lisa finished small action items
- 16:17:02 [EA]
- EA has joined #coga
- 16:17:02 [Mike_Pluke]
- Table 3: Entering data, error prevention & recovery
- 16:17:21 [Lisa_Seeman]
- https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html
- 16:18:08 [JohnRochford]
- q+
- 16:18:36 [Mike_Pluke]
- Changed: definition in the semantics - coga-explain
- 16:19:48 [Mike_Pluke]
- Changed: definition in the semantics - logs (breadcrumb type information) - to make it interoperable
- 16:20:10 [Mike_Pluke]
- Could be in the header of the webpage - so exposed to the browser
- 16:21:17 [Mike_Pluke]
- Logs can have a name and multiple named steps, etc.
- 16:21:18 [Lisa_Seeman]
- <log name="booking trip"> <step> <name>buy ticket</name><actiontaken>bought ticket to NY return</actiontaken><view changepossible="yes">url </view><step>
- 16:21:20 [Lisa_Seeman]
- <step> <name>hotel</name><actiontaken>booked Sheraton single room</actiontaken><view changepossible="yes">url </view></step>
- 16:21:21 [Lisa_Seeman]
- <step> <name>car rental</name><view current changepossible="yes"/> </step>
- 16:21:23 [Lisa_Seeman]
- </log>
- 16:22:47 [Lisa_Seeman]
- q?
- 16:22:56 [Lisa_Seeman]
- Ack John
- 16:24:08 [Lisa_Seeman]
- Interactive controls are visually clear or visually clear controls are easily available that conform to the following:
- 16:24:47 [JohnRochford]
- John's question is "Do we expect coga explain will end up in AAA?"
- 16:27:50 [janina]
- present+ Janina
- 16:28:10 [JohnRochford]
- q+
- 16:29:21 [Mike_Pluke]
- Mike "The scope for when coga-explain may be required needs to be defined - to avoid it definitely being AAA"
- 16:29:33 [Lisa_Seeman]
- 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 [Lisa_Seeman]
- https://rawgit.com/w3c/coga/master/extension/index.html
- 16:30:32 [Rich]
- Rich has joined #coga
- 16:31:53 [Lisa_Seeman]
- q?
- 16:32:02 [Lisa_Seeman]
- ack johnr
- 16:32:06 [Rich]
- present+ Rich_Schwerdtfeger
- 16:37:25 [Mike_Pluke]
- If we have the log, do we still need feedback?
- 16:37:31 [Lisa_Seeman]
- q?
- 16:37:59 [EA]
- Does the log appear in a different place to the feedback?
- 16:38:29 [Mike_Pluke]
- Rich also says that feedback has a timely component
- 16:39:48 [Mike_Pluke]
- 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 [Mike_Pluke]
- 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 [ddahl]
- 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 [Lisa_Seeman]
- q?
- 16:44:42 [Lisa_Seeman]
- ack dd
- 16:44:42 [Zakim]
- 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 [Zakim]
- ... application)
- 16:46:07 [Mike_Pluke]
- 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 [Mike_Pluke]
- 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 [Mike_Pluke]
- Need to be able to make the change throughout the duration of the "activity"
- 16:50:04 [Lisa_Seeman]
- The mecanisim should be easily availible though out the activity
- 16:52:38 [EA]
- 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 [EA]
- I think you meant 'knows' but is this what you need to make it clear?
- 16:58:26 [EA]
- sorry microphone not working.
- 16:59:35 [EA]
- It is in the Terms
- 17:01:54 [Mike_Pluke]
- Text EA quoted should be in the success criteria - not in the terms
- 17:02:55 [EA]
- Thank you - bye
- 17:03:05 [ddahl]
- ddahl has left #coga
- 17:03:23 [Lisa_Seeman]
- rrsagent, make logs public
- 17:03:30 [Lisa_Seeman]
- rrsagent, create minutes
- 17:03:30 [RRSAgent]
- I have made the request to generate http://www.w3.org/2016/07/25-coga-minutes.html Lisa_Seeman
- 17:15:19 [Rich]
- what about Arnaud?
- 19:11:39 [Rich]
- Rich has joined #coga
- 19:15:06 [Lisa_Seeman_]
- Lisa_Seeman_ has joined #coga
- 20:03:05 [Rich]
- Rich has joined #coga
- 20:57:01 [Rich]
- Rich has joined #coga
- 21:38:31 [Rich]
- Rich has joined #coga