W3C

- DRAFT -

Silver Errors Subgroup

02 Dec 2020

Attendees

Present
sarahhorton, ToddLibby, CharlesHall, Sukriti_, SuzanneTaylor
Regrets
Chair
sarahhorton
Scribe
Sukriti

Contents


<sarahhorton> scribe: Sukriti

<scribe> scribe:Sukriti

CH: the ability to resume activity without hearing is going to be different than resuming activity with anyone else on the list

SH: user turns of wifi, system displays same page. What unique needs would someone without hearing have that they would need to overcome this error?

CH: The info that is being added to each functional need is to address the higher level and not each individual user need?

SH: The individual needs are ones specific to user groups

CH: How to they relate to common user needs?

SH: User needs a notification is the common need. The individual need is the one for specific groups - for the notification to be accessible
... intent is to surface functional needs pertaining to the error

ST: More of a brainstorming exercise than formal

SH: Getting all the ideas out there. After we have everything, we will refine and make choice

CH: Should there be a document convention to indicate that?

SH: If it's helpful for establishing associations, we can do that. Ultimately, we want the statements that surface the needs
... At some point we need methods and how-tos etc.
... This document is a source for the deliverable, probably not a deliverable

ST: Add **RN** to enable others to join at any time
... How to we mark the ones that have been reviewed?

SC: Add reviewed + initials on the ones that have been

SH: Can change the ones that have been reviewed by at least one person to "REVIEWED"
... We're sharing the document with the task force and can ask people to look at it
... Should we share now or wait until we have more polished

ST: Waiting would be better

SH: Share screenshots of errors in the meantime
... error flows in the wild

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/12/02 18:02:25 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Default Present: sarahhorton, ToddLibby, CharlesHall, Sukriti_, SuzanneTaylor
Present: sarahhorton ToddLibby CharlesHall Sukriti_ SuzanneTaylor
No ScribeNick specified.  Guessing ScribeNick: Sukriti_
Found Scribe: Sukriti
Found Scribe: Sukriti

WARNING: No "Topic:" lines found.


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


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


[End of scribe.perl diagnostic output]