<sarahhorton> https://gist.github.com/xero/2d6e4b061b4ecbeb9f99

Sarah did subcommittee introduction

<sarahhorton> take up item 1

Sarah introduced herself

<sarahhorton> Sheri introduced herself

Chris (handle: Crispy) introduced himself

Suzanne introduced herself

Stacy introduced herself

Stacey* introduced herself (sorry for misspelling your name)

Todd introduced himself

<srayos> Thanks, Sheri! No problem.

Fredrick introduced himself

- Ways of working

Sarah shared her thinking on the where and how of meetings - today is a kickoff, suggested working meetings with homework and collective steps to move forward

longer meetings periodically

plan B is shorter meetings but will ultimately move more slowly

Sarah prefers plan A

Plan C - ad hoc meetings, more async work

Sarah suggested discuss then vote

Sheri suggested we need to be cognizant of timezones for scheduling regular meetings

Sarah clarified IRC wouldn't be used for design workshops, too hard to scribe

Plan B would use IRC

Sheri reminded people that we can split up scribing responsibilities if it gets too onorous

Chris preferred plan B

Sarah suggested there could also be a hybrid - the occasional longer design sessions with other regular shorter meetings. Sarah commented that progress seems to be excruciatingly slow with Plan B

Fredrick asked if there was going to be a mailing list

Sarah said she would check with Jeanne

Vote

<sarahhorton> Plan A — design workshops Plan B — working meetings Plan C — asynchronous Plan D — Plan A + B

<srayos> Plan D sounds effective, with consideration for time zones

<Crispy> +1 Plan D

<st> +1 Plan D

<ToddLibby> +1 Plan D

+ 1 Plan D

Plan D carried the vote, Sarah pointed out we can tweak it if it doesn't work

Sarah will take a stab at setting up meetings with shifting timezones to give everyone the most opportunity to attend

Next topic: how to collaborate/communicate

Sara proposed setting up a basecamp project

Sarah*

<Crispy> Wiki: https://www.w3.org/WAI/GL/task-forces/silver/wiki/Error_Handling#Conference_Call

Sarah will send out a basecamp cheatsheet with features to avoid due to accessibility issues

Use the wiki page, not google docs

wiki, basecamp, IRC, zoom

are the primary communication channels

Crispy volunteered to do a write up on the wiki

Sheri asked if our work should be "Feedback" and not "error handling"

Sarah said she would put Sheri's question as the first question at the next meeting

<sarahhorton> purpose: define guidelines related to errors and create content to support them using the WCAG 3 framework.

Homework - think about that purpose and what it means

next topic - planning the plan (meta planning)

Sarah proposed the plan should be design-focused

Sarah will put together a proposal for the plan for the next meeting

Stacey - what do we see as an error?

<srayos> That's a broad term... definitely poor instructions (required, format, etc...)

Sheri thinks that future proofing this is the trickiest part

Christian asked if people had reviewed the WCAG 3 framework

<srayos> Also placement, using only color to identify errors, modals that do not announce/do not close/ do not scale at zoom

<srayos> Perhaps we can break into errors by error type for small bites of the elephant?

<st> https://www.w3.org/WAI/GL/task-forces/silver/wiki/Creating_Guidelines,_Methods,_and_Supporting_Documents

Sarah suggested people review the FPWD for Silver to think about how we fit into that framework

<st> https://docs.google.com/document/d/1sInhvjkvq5WASlOrEMfshAZSVQB8kM1clRWfGXfVEFI/edit

part of our role is to be a guinea pig for the framework and suggest changes if needed

<sarahhorton> Draft of WCAG 3 FPWD (in progress): https://w3c.github.io/silver/guidelines/

<sarahhorton> ACTION: Crispy to update wiki with communication and collaboration mplan

<sarahhorton> ACTION: sarahhorton to schedule workshop meetings and group meetings

<sarahhorton> ACTION: sarahhorton to review Basecamp VPAT and document issues and workarounds

<sarahhorton> ACTION: sarahhorton to draft project charter

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/excrutingly slow in this model/excruciatingly slow with Plan B/
Succeeded: s/take up item 2/excruciatingly slow with Plan B/
Succeeded: s/take up item 2//
Succeeded: s/excruciatingly slow with Plan B//
Succeeded: s/take up item 3//
Succeeded: s/take up item 4//
Succeeded: s/take up item 5//
Succeeded: s/Sheri, do you want me to finish up?//
Present: sarahhorton ToddLibby Suzanne-Taylor Sheri_B-H_ Crispy srayos TimBoland
Regrets: AparnaPasi
No ScribeNick specified.  Guessing ScribeNick: Sheri_B-H_
Inferring Scribes: Sheri_B-H_

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: crispy sarahhorton

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