<scribe> scribe: Suzanne

zakin, take up next

Review Errors Sub-Group Project Definition and discuss where we are; update project definition as needed

sarah: reads through project definition and scope at https://www.w3.org/WAI/GL/task-forces/silver/wiki/Error_Handling

Todd & Suzanne: agree the definition looks fine

Sarah: A second meeting has been scheduled, which will be an open office hours meeting, where you can join and work together informally
... The workshop meeting is at 8-10 AM EST (New York), 1-3 PM GMT (London), and 6:30-8:30PM IST (India)
... On Thursdays starting Dec 3

Review progress in Error Flows Inventory Google Doc and assign unassigned To-Dos for remaining Error Flows

<sarahhorton> https://docs.google.com/document/d/1Fix0uwC0vODgiKl09lMF77FMdd52u64KG9_-N86r4UE/edit#heading=h.uk0e1opoh642

<sarahhorton> https://drive.google.com/drive/folders/1PR8NaFm4x9lmEtYUxHGSZYdQaen9XtDf

Sarah: Please check that you can access these links. Feel free to add additional documents in the folder.
... When writing error flows, the structure of user needs can be "User needs ... so that ..." if you find it helpful, but we can also normalize this later, so don't worry too much about it
... If you think of a new error flow, go ahead and add it to the errors flows list

Group: Discusses making the highlighting in the errors flows doc fully accessible
... choses **RN** as a search tag to go with a bold highlight with light yellow background

Todd: Offers to take on Visual CAPTCHA error flow

Discuss next steps and sketch out timeline through Dec 31, 2020

Introduce new document, Relevant Concepts, to collect guiding concepts and principles to guide our work developing error-related guidelines

Sarah: The group has been bringing up a variety of concepts from reading, review work, etc
... We can collect these concepts here: https://docs.google.com/document/d/1Vb4wp_UgQNU0HHyxgvXOty8opnFd1cy_CH6FvKcEgXY/edit#heading=h.hqlxjdipa91h
... heuristics could help support and provide rationals for the work

Discuss next steps and sketch out timeline through Dec 31, 2020

Group: Discusses Sarah's idea of spreading out leadership responsibilities

Suzanne: trying to stay worker bee in W3C work

Todd: Might be interested down the road

Group Discusses: We would like our work in some state of being done around the time when the WCAG 3.0 first public working draft feedback starts to need to be processed. After helping with that, we might resume work on errors to adjust this work to any changes in format.

Sarah: Can we complete the Error Flows work by the 9th? Then Sarah will take the next week to process, then we'll meet to discuss, and we'll target a very rough draft of SC by the end of December.

Group: agrees

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/On Wednesdays/On Thursdays starting Dec 3/
Default Present: sarahhorton, ToddLibby, SuzanneTaylor
Present: sarahhorton ToddLibby SuzanneTaylor
Regrets: Charles
No ScribeNick specified.  Guessing ScribeNick: SuzanneTaylor
Found Scribe: Suzanne

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

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


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)