Meeting minutes
Update team on presentation to Silver Taskforce of Errors User Needs Worksheet and Errors User Needs Summary
sarah: everyone really happy about the approach
… in the larger group
Review Scope and Timeline; discuss next steps
<sarahhorton> Scope: https://
Sarah: timeline
Review February Tasks; assign tasks
tasks for the month divided up into individually assignable pieces
https://
<sarahhorton> https://
Sarah: guidelines from the first public working draft
… that and the guidelines worksheet to model out guidelines
sukriti: are errors a subtopic of other guidelines or guidelines of their own?
Sarah: Can be either depending on the scenario
… came up in call last week
… contrasts
… should there be a different error contrast than general
… there could be a case where that is the requirement
… our scope is for error related guidelines for now
chris: related guidelines in the summary sheet
… cross mapping between different groups
… there are things in the user needs data such as persistent data
… thinking about the language of the guidelines and applicability
Todd: also for the timed guideline
… is there a non text contrast section as well?
chris: error icons for additional understanding
Sarah: subgroups that currently exist
… asking or compiling a list of things we're looking at
… content resources to use for developing guidelines
chris: need to be w3c or external?
sarah: need to stick with silver resources
chris: I can do that
sarah: next thing would be to go through the worksheet and add a column that is yes/no
… errors/ guideline?
… yes this is an errors guideline
yes/no/maybe
sarah: one way to do it would be to have 2 of us to do that
… get together and do it together
Sukriti: I can do it
… two columns and discuss where there is a disagreement
todd: can do that
sarah: content category, and other content to put in the guidelines outline for the end of the month
… come up with a template
<sarahhorton> https://
sarah: structured content description
sarah: working meeting not scheduled at the moment
chris: throwing a whole section in and seeing where the gaps are
sarah: if someone wants to host it, would work
todd: can host
… don't mind getting on the collaborative call
chris: doesn't have to be every week
sarah: do one on Friday?
chris: that works
sarah: 11 ET
todd: can do Fridays
sarah: can use the w3c room
sarah: Janina was explaining iOT error flows
Discuss ways to collect input and feedback, e.g., additional error flows
sarah: deliberate about getting feedback
… helpful to catch edge cases Janina mentioned