W3C

– DRAFT –
Silver Task Force & Community Group

31 March 2023

Attendees

Present
Chuck, jeanne, kirkwood, Lauriat, Luis, Makoto, maryjom, Rachael
Regrets
-
Chair
-
Scribe
maryjom

Meeting minutes

<jeanne> working draft?

Next week in AG

<Rachael> https://www.w3.org/WAI/GL/wiki/Upcoming_agendas

jeanne: Wrong agenda above...

<Lauriat> https://lists.w3.org/Archives/Public/public-silver/2023Mar/0029.html

<Rachael> WCAG 3 Review of revised conformance section survey https://www.w3.org/2002/09/wbs/35422/WCAG3_conformance_March_23/

jeanne: Review of the revised conformance sections survey. Please make sure you do the survey before it closes later today.

jeanne: For WCAG 2.2 they are doing the parsing survey and issues survey.

<Rachael> Proposal to change Taskforce Authority Survey https://www.w3.org/2002/09/wbs/35422/authority-to-publish-23/

<Rachael> WCAG2ICT Second Content Review Survey https://www.w3.org/2002/09/wbs/35422/WCAG2ICT-second-content-review-by-AGWG/

jeanne: Encourage you also complete the two surveys for the April 11 call - WCAG2ICT content review and changing the Taskforce Authority

Rachael: The Conformance survey that we've been working on and trying to improve the content so it works better together. This is more of an editorial review.

Rachael: This is to approve the content for the next published draft of WCAG 3.

List of Methods for each Error Notification Outcome

<jeanne> Error NOtification

Rachael: we are all now moving on to working in the live document, which will not be scribed.

<Chuck> +1 reading aloud :-)

<Zakim> Lauriat, you wanted to note the scale of writing needed for this and how I hope we can manage that

<Zakim> jeanne, you wanted to suggest that we just reference existing specs and not repeat that

<Zakim> jeanne, you wanted to suggest a Method for the accessiiblity stack

<kirkwood> should how to resolve the error be part of the notification?

<kirkwood> +1

<Chuck> "It's hopeless, give up today, try again tomorrow"

<Rachael> When creating outcomes, there is an ongoing question about when to break apart outcomes and when to combine related requirements. The advantage of breaking outcomes apart is that separate outcomes raise awareness of needs and ensure critical parts are not hidden at lower levels of documentation. The disadvantage of creating separate outcomes is the sheer number of resulting outcomes which may feel overwhelming. Groups should remain aware

<Rachael> of this tension and document the rational for breaking outcomes apart.

<Chuck> +1 to Rachael's summary.

<Lauriat> Thank you! Copied in.

<Rachael> we are exploring rating scales so this may be a good exemplar

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

All speakers: jeanne, Rachael

Active on IRC: Chuck, jeanne, kirkwood, Lauriat, Luis, Makoto, maryjom, Rachael