Silver Conformance Options Subgroup

12 May 2022


Azlan, GreggVan, janina, jeanne, maryjom, shadi

Meeting minutes

<janina> Date 12 May 2022

Agenda Review & Administrative Items

GreggVan: have pulled the document into a Word doc and will share his updates

Continued Discussion https://raw.githack.com/w3c/silver/use-cases-apr22-js/use-cases/index.html

jeanne: Have made the changes requested 28th April

<jeanne> https://raw.githack.com/w3c/silver/use-cases-apr22-js/use-cases/index.html#situation-3

<GreggVan> +1

GreggVan: Clarifying with "normative" is a good improvement to technical standards on example 3.1

jeanne: [continues to read through the amendments as requested 28th April]

GreggVan: all steps in the process should be accessible not just the submit part

suggest referencing WCAG 2.1 & 2.2 for word-smithing

jeanne: WIll make it clearer that all steps in the process must be accessible

shadi: Commenting on Jeanne's amendments. With regards to critical errors are we getting too detailed? What is the right balance for level of detail?

Agrees that a generic statement and letting the group work out the specifics can be better.

janina: we will have to carefully consider that over time and across different disability perspectives

maryjom: Exactly - being more generic might be more helpful at this point

janina: Examples rather than an exhaustive list

GreggVan: Suggests "a few of the many examples..."

greggvan comments on use cases document

addition of "equivalent facilitation and limitations on application" to the problem statement

also "... more technical in nature and can and should be addressed in WGAC and need to be addressed by policy/regulation setters or others..."

Under approach and structure addition of " ...but not limited to..."

"How accompanying guidance" amended to How guidance documents that accompany technical standards...(including advice to policy setting bodies)"

<Zakim> jeanne, you wanted to talk about database

jeanne: minor point to keep in mind the direction we want to put informative and normative into the database to be able to bring it all up together

GreggVan: thats great but a tool which cannot be the standard. will update to include "tools" as well as documents

Key Terminology: first bullet point added "directly" to read "providing content dorectly to others"

Under example 1.2 deleted all except the last bullet of How technical standards might contribute to addressing this situation

To resume this topic next week

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).