25 Jul 2016

See also: IRC log


Lisa, Seeman, JohnRochford, DebbieDahl, Lisa_Seeman, Mike_Pluke, KurtM, Janina, Rich_Schwerdtfeger


<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

<Lisa_Seeman> agenda: this

<Lisa_Seeman> next item

<Lisa_Seeman> scribe: Mike_Pluke

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open

<JohnRochford> About action item #153, Mike says it is difficult to compare and map the ISO doc to the work we are doing

<JohnRochford> Mike: It's very comprehensive and high level.

<JohnRochford> Mike: One problem is we don't have the most up-to-date version of the ISO doc.

<JohnRochford> Mike: What I'm trying to determine is if there are issues addressed in the ISO doc that we have not addressed.

issue paper on user testing and ethics for cognative - with Neil - Leave Open

<thaddeus> + Thaddeus

Review user research on emotioal disabilities - Lisa has done

<Lisa_Seeman> next item

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

Lisa finished small action items

Table 3: Entering data, error prevention & recovery

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html

Changed: definition in the semantics - coga-explain
... definition in the semantics - logs (breadcrumb type information) - to make it interoperable

Could be in the header of the webpage - so exposed to the browser

Logs can have a name and multiple named steps, etc.

<Lisa_Seeman> <log name="booking trip"> <step> <name>buy ticket</name><actiontaken>bought ticket to NY return</actiontaken><view changepossible="yes">url </view><step>

<Lisa_Seeman> <step> <name>hotel</name><actiontaken>booked Sheraton single room</actiontaken><view changepossible="yes">url </view></step>

<Lisa_Seeman> <step> <name>car rental</name><view current changepossible="yes"/> </step>

<Lisa_Seeman> </log>

<Lisa_Seeman> Interactive controls are visually clear or visually clear controls are easily available that conform to the following:

<JohnRochford> John's question is "Do we expect coga explain will end up in AAA?"

Mike "The scope for when coga-explain may be required needs to be defined - to avoid it definitely being AAA"

<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

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/extension/index.html

If we have the log, do we still need feedback?

<EA> Does the log appear in a different place to the feedback?

Rich also says that feedback has a timely component

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)

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"

<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

Debbie questions whether necessary to specify different types of errors i.e. choosing a destination that is valid but not the wanted one

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

Need to be able to make the change throughout the duration of the "activity"

<Lisa_Seeman> The mecanisim should be easily availible though out the activity

<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."

<EA> I think you meant 'knows' but is this what you need to make it clear?

<EA> sorry microphone not working.

<EA> It is in the Terms

Text EA quoted should be in the success criteria - not in the terms

<EA> Thank you - bye

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/07/25 17:03:36 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Mike_Pluke
Inferring ScribeNick: Mike_Pluke

WARNING: No "Topic:" lines found.

Present: Lisa Seeman JohnRochford DebbieDahl Lisa_Seeman Mike_Pluke KurtM Janina Rich_Schwerdtfeger

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 25 Jul 2016
Guessing minutes URL: http://www.w3.org/2016/07/25-coga-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]