15:36:27 <RRSAgent> RRSAgent has joined #coga
15:36:27 <RRSAgent> logging to http://www.w3.org/2016/08/01-coga-irc
15:38:42 <Lisa_Seeman> agenda: this
15:38:43 <Lisa_Seeman> agenda+  review actions, and timelines
15:38:45 <Lisa_Seeman> agenda+  Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html#table3
15:38:46 <Lisa_Seeman> agenda+ What have we missed for issues page
15:38:48 <Lisa_Seeman> agenda+ be done
15:45:00 <JohnRochford> JohnRochford has joined #coga
15:46:37 <jkirkwood> jkirkwood has joined #coga
15:48:28 <Lisa_Seeman> are people able to log into webex?
15:48:38 <Lisa_Seeman> i am getting the meeting is not availible
15:54:18 <jkirkwood> sorry don’t have (can’t locate) webex password
16:03:24 <ddahl> ddahl has joined #coga
16:08:08 <Lisa_Seeman> scribe JohnRochford
16:09:04 <jkirkwood> present+ kirkwood
16:09:08 <Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open
16:09:10 <Lisa_Seeman> next
16:09:14 <Lisa_Seeman> next item
16:09:28 <Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open
16:10:08 <JohnRochford> present +JohnRochford
16:10:26 <ddahl> present+ Debbie_Dahl
16:13:39 <JohnRochford> ddahl: discussing chat features, and conversations with bots or humans
16:15:25 <JohnRochford> ddahl: In response to a question from JohnR, says that, as long as everything is handled properly, it should not matter whether the agent is a bot or a human.
16:16:16 <JohnRochford> ddahl: Though we do know that bots aren't being paid to get people quickly off of chat.
16:17:25 <JohnRochford> Lisa: Sometimes speech is not the easiest process, and text is easier. With text, you can take it at your own speed rather than listening to people who are speaking without pause.
16:19:19 <JohnRochford> Lisa: Perhaps the most important domains that this is most important are health and safety.
16:19:25 <Lisa_Seeman> next item
16:19:34 <Lisa_Seeman> next item
16:20:01 <Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html
16:21:24 <JohnRochford> Lisa: We are looking at Table 3.
16:22:30 <Lisa_Seeman> q?
16:22:32 <JohnRochford> Lisa: Example of minimizing errors is that it should not matter what format a user enters a date.
16:25:47 <richardschwerdtfeger> richardschwerdtfeger has joined #coga
16:25:59 <ddahl> q+ to ask about mistake correction vs. mistake prevention
16:26:57 <JohnRochford> Lisa: Will correct, in the table, "... with unwanted loss of data ..." to "without unwanted loss of data ...".
16:30:41 <richardschwerdtfeger> present+ Rich_Schwerdtfeger
16:32:43 <KurtM> KurtM has joined #coga
16:33:27 <JohnRochford> ddahl: should we say something in row 2 like "if there is not an easy way to prevent mistakes, then there should be an easy way to correct mistakes".
16:35:13 <JohnRochford> Lisa: Requirement is to use known techniques to prevent errors.
16:35:46 <JohnRochford> q+
16:36:18 <Lisa_Seeman> q?
16:36:24 <Lisa_Seeman> ack dd
16:36:24 <Zakim> ddahl, you wanted to ask about mistake correction vs. mistake prevention
16:38:20 <Lisa_Seeman> ack john
16:39:02 <JohnRochford> John: There should not be conditional relationship between prevention and correction. Easy correction of mistakes should always be available.
16:39:39 <JohnRochford> ddahl: It's implicit in the requirement that prevention is preferable.
16:40:27 <JohnRochford> q?
16:41:25 <JohnRochford> Lisa: Perhaps we could add techniques for improving or assuring user confidence.
16:42:19 <JohnRochford> KurtM: For a user to get a summary of where they are in a process (could be confidence building).
16:43:16 <JohnRochford> Lisa: About the process-logging idea, we haven't included what's left to complete.
16:43:35 <richardschwerdtfeger> q+
16:44:24 <Lisa_Seeman> q?
16:44:31 <Lisa_Seeman> ack rich
16:44:55 <richardschwerdtfeger> q-
16:46:30 <JohnRochford> Lisa: Need to add to log proposal: done, pending, current
16:46:39 <Lisa_Seeman> add log: done, pending , current
16:47:19 <Lisa_Seeman> statis
16:47:32 <richardschwerdtfeger> s/statis/status/
16:47:56 <JohnRochford> Lisa: status would be done, pending, current
16:49:21 <Lisa_Seeman> q?
16:51:06 <JohnRochford> Lisa: There should be communication, for each user action, about whether or not it was successful.
16:51:27 <JohnRochford> ddahl: I don't think we want to bombard users with success messages.
16:51:48 <JohnRochford> ddahl: There should be judgement about how much confirmation should be done.
16:53:08 <JohnRochford> KurtM: Perhaps an assistant or caregiver could review info (from log, for example).
16:53:22 <JohnRochford> Lisa: Yes, with user permission.
16:53:45 <JohnRochford> Lisa: I really like that.
16:54:55 <jkirkwood> was JohnK: “Perhaps an assistant or caregiver could review info (from log, for example).”
16:55:10 <Lisa_Seeman> q?
16:55:32 <JohnRochford> JohnK, I apologize for guessing your voice incorrectly.
16:56:11 <jkirkwood> ;) no problem!
16:57:00 <Lisa_Seeman> 3.1.1 Timed event are not used except for the situations listed below.§
16:57:02 <Lisa_Seeman> (See COGA Techniques 2.9.1 )
16:57:03 <Lisa_Seeman>     Sessions time out after 20 hours have elapsed
16:57:05 <Lisa_Seeman>     Where security may be at risk a session can time out after half an hour of disuse
16:57:06 <Lisa_Seeman>     Where financial or sensitive information is at risk the time out can be shorter
16:57:08 <Lisa_Seeman>     Timing is essential to the function of the content - such as some tests.
16:57:09 <Lisa_Seeman> Where there is an exception, the content must conform to WCAG 2.2.1 Timing Adjustable, so long as
16:57:11 <Lisa_Seeman>     The function to turn off, adjust or extend the timing are controlled by simple action and labeled with simple text.
16:57:12 <Lisa_Seeman>     A user settable time minimum must be provided to complete any controlling action. Note that all user setting must be easy to set and use standardized techniques when available.
16:57:14 <Lisa_Seeman>     The user can be made aware of the time out limits, including the length of the warning - this condition may be deleted
16:57:15 <Lisa_Seeman>     The user can easily return to the same point in a task, without data loss.
16:57:17 <Lisa_Seeman>         as the default
16:57:18 <Lisa_Seeman>         standardized system setting (example the user can set that the data is not stored)
16:57:20 <Lisa_Seeman>         option to set user preference that has a conformance interface and is directly available at each stage of the task.
16:59:04 <Lisa_Seeman> q?
16:59:42 <ddahl> ddahl has left #coga
17:00:24 <Lisa_Seeman> rrsagent, make logs public
17:00:33 <Lisa_Seeman> rrsagent, create minutes
17:00:33 <RRSAgent> I have made the request to generate http://www.w3.org/2016/08/01-coga-minutes.html Lisa_Seeman
17:01:03 <Lisa_Seeman> zakim, please part
17:01:03 <Zakim> leaving.  As of this point the attendees have been JohnRochford, Lisa, Seeman, DebbieDahl, Lisa_Seeman, Mike_Pluke, KurtM, Thaddeus, Janina, Rich_Schwerdtfeger, kirkwood,
17:01:03 <Zakim> Zakim has left #coga
17:01:06 <Zakim> ... Debbie_Dahl
17:01:15 <Lisa_Seeman> rrsagent, please part
17:01:15 <RRSAgent> I see no action items