RE: WCAG 3 Subgroup Update

There is also a severities subgroup that appears to be looking at similar questions in terms how scoring of tests impacts users and what score is sufficient.  I think it would be good to post some understanding of the relationship between the different subgroups in a public way as John is not the only one who has questions on this matter rather than keeping the details in private conversations.

Jonathan

From: Wilco Fiers <wilco.fiers@deque.com>
Sent: Friday, July 15, 2022 8:05 AM
To: John Foliot <john@foliot.ca>
Cc: Silver Task Force <public-silver@w3.org>; GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
Subject: Re: WCAG 3 Subgroup Update

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hey John,
Short answer; testing is deciding if something is correct or true. Scoring is taking results from testing and coming up with some aggregate, like a grade. Like if I wanted to know how energy efficient my house is, there are different tests I can do. Check the windows, walls, roof, that kind of thing. That gives me some results. Taking those results and coming up with an energy label or something like that is scoring.

They're related concepts, which we'll explore in more detail during TPAC. The subgroups are doing prep work for that, so that we'll have some people think through different areas of testing / scoring in advance, instead of having to do it on the spot.


If you have further questions, would you mind replying to me directly, or to group-ag-plan@w3.org<mailto:group-ag-plan@w3.org> instead. There are people on this mailing list who do not like receiving lengthy e-mail exchanges.

Kind regards,

On Thu, Jul 14, 2022 at 7:47 PM John Foliot <john@foliot.ca<mailto:john@foliot.ca>> wrote:
Hi Wilco,

Thanks for this.

One question: why are testing and scoring considered separate issues? And when did the Working Group decide to split the two topics into separate activities (minutes/Survey results)? (Please)

It would seem to me that the results of any test or test-type would be some kind of score (currently in WCAG 2.x that 'score' is either 100/100 or 0/100 - i.e. Pass or Fail) but it seems to me to be unusual to start looking at tests and test-types without considering how they will also resolve to a score, especially in consideration of the stated goal and context of Bronze, Silver and Gold levels of conformance.

This question has already come up in the context of mapping the 2.x SC to 3 (see my comments related to fault tolerance and spelling mistakes in Caption files here:
https://docs.google.com/document/d/1MGGgqgeL779aJu7iNuXQMHgJygV7l6GouM7--5ABJ5U/edit#heading=h.vx20z4iqr83a)

Thanks

JF

On Thu, Jul 14, 2022 at 12:24 PM Wilco Fiers <wilco.fiers@deque.com<mailto:wilco.fiers@deque.com>> wrote:
Hey folks,

We wanted to give you all an update on the subgroups that AG is in the process of starting up. We’ve gone through the survey responses, and based on people’s interest and indicated availability, we’ve settled on meeting times such that each subgroup has at least 4 participants. We have found a facilitator for most groups.. Those groups should try to start meeting next week. The subgroup wiki pages (https://github.com/w3c/silver/wiki#subgroups) have been updated with a (tentative) list of members. Those should receive an invitation from the facilitator soon.

The subgroups will be meeting at the following times:
Accessibility-supported: Tuesday 8am Eastern
Issue Severity: Wednesday 11am Eastern
Test Types & Terminology: Monday 8am Easern
Equity: Monday 8am Easern

Unfortunately (and quite predictably) we couldn’t find meeting times that worked for everyone. If you are interested in participating in a subgroup, but are not on the member list please reach out to group-ag-plan@w3.org<mailto:group-ag-plan@w3.org>. See the WCAG 3 Subgroup Handbook for details on participation (https://docs.google.com/document/d/1_caRiZaTQDmsd2Vq415sz4AIullNse-GeGtohUfg_5M/edit)

For the scoping group we were unable to find a meeting time such that it would have enough participants. We will continue to work to try and get this subgroup started, although it may be delayed.

--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force



--
John Foliot |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |
"I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"


--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force
[cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]