W3C

– DRAFT –
Silver Errors Subgroup

17 February 2021

Attendees

Present
sarahhorton, Sukriti, Todd
Regrets
-
Chair
sarahhorton
Scribe
Sukriti

Meeting minutes

Review and discuss coding in Errors User Needs Worksheet

sarah: update the group on guidelines we're thinking about

sarah: confirm user needs to address with guidelines to present at the end of the month

<Crispy> +Present

https://docs.google.com/spreadsheets/d/1BEzSKUsoMQZAwLY5uM5T4Jk7vqKruQT8EaheijQJ7nk/edit#gid=14365122

sarah: whatever we include as a user need is specific to errors
… we might have a different level of requirements
… for example color contrasts
… clear language is a requirement overall
… yes - all about errors and needs its own guidelines
… another category. This is an a11y need, but not an errors need
… yes, yes-adjacent, yes-imperative (matters overall, but more for errors)

crispy: could say that error messages in general need to be more prominent
… but need to be careful of scope of our group

sarah: next task would be to think about critical errors
… guidelines worksheet - at the top is the guidelines and outcomes
… critical errors in the sheet are currently vague
… can be more specific in the sheet
… i.e. the guidelines sheet

crispy: next steps
… go through the assigned items

sarah: all to edit critical errors
… in different columns

Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

Diagnostics

Maybe present: crispy, sarah