Re: WCAG 2.x issues task force

Hey Alastair,
Thank you for the clarifications. I do have concerns about moving WCAG 2
decisions to a separate mailing list. It's important the working group
stays informed and connected to the work its task forces do. It's not
really a group decision if most of the group is not informed about it. We
can have this conversation once the process document is shared with AG for
review.

On Fri, Nov 10, 2023 at 6:42 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Wilco,
>
>
>
> > Does this mean you're planning not to share updated to informative
> documents with the working group for review anymore?
>
>
>
> No, it means this is becoming the method of sharing with the working group
> for review.
>
>
>
> Anyone in the AGWG can join that list and participate and/or review
> things. You can be fairly hands-off and just keep an eye on the email list
> for updates, or you can get stuck in on a particular issue, or join the
> meetings.
>
>
>
>
>
> > Is that a decision that was already made, or will the group have a vote
> on it?
>
>
>
> It is an outcome of the decision the group made, which was to move the
> focus to WCAG 3. As part of that we have closed the Silver TF and are
> opening a WCAG 2.x issues TF.
>
>
>
>
>
> >  Also, would this also be true for other task forces with informative
> documents like ACT? I recall that we surveyed a similar proposal a few
> months back, and that the group wasn't in support of that.
>
>
>
> We’ll take it on a case by case basis. For this TF Michael, Bruce and I
> will document the proposed process and put that up for review.
>
>
>
> As a taster (we haven’t finished yet), there are likely to be 3 categories
> of changes:
>
>    - Requested input: People are likely to have comments.
>    - Consideration: People are unlikely to have comments, but you never
>    know.
>    - FYI: Editorial things.
>
>
>
> So everything will be sent around, but we’ll try and prioritise which
> issues are most likely to have comments/discussion.
>
>
>
> Everything will be trackable and transparent. From the meetings we’ll have
> some form of minutes, e.g.
>
> https://lists.w3.org/Archives/Public/public-wcag2-issues/2023Nov/0002.html
>
>
>
> And we’ll use a github project to move things between statues and track
> what’s worked on and done:
>
> https://github.com/orgs/w3c/projects/56/views/1?layout=board
>
>
>
> You’ll notice there are columns for “Drafted” (ready for TF approval) and
> “Ready for approval”, which is for the wider AGWG. The mechanism for that
> wider approval is likely to be a combination of the email notifications to
> the new list, and github.
>
>
>
> All AG members are welcome to join the TF (i.e. the meetings), but we
> wanted to make sure than any AG member could follow along asynchronously,
> thus the invite to the list.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
>
>
>
>
> On Wed, Nov 8, 2023 at 5:09 PM Alastair Campbell <acampbell@nomensa.com>
> wrote:
>
> Hi everyone,
>
>
>
> TL;DR: If you want to know-of / approve changes to WCAG 2.x informative
> documents, join the new email list
> <https://lists.w3.org/Archives/Public/public-wcag2-issues/>!
>
>
>
> We are setting up the WCAG 2.x Task Force (TF) and want to make sure
> everyone with an interest can participate.
>
>
>
> The TF will be responsible for updating WCAG 2.x information, primarily
> the informative documents (understanding and technique documents). Things
> like errata may be worked on, but will require approval from the whole
> group.
>
>
>
> We are anticipating that there will be a core group of people actively
> working on issues and attending a weekly meeting, and some people who wish
> to be kept informed.
>
>
>
> To separate emails from the WCAG3 work, we will keep notifications and
> approvals in github and on a separate email list:
>
> https://lists.w3.org/Archives/Public/public-wcag2-issues/
>
>
>
> So the main action now is: If you wish to be informed of changes to WCAG 2
> documents then please join that list.
>
>
>
> We are still defining the approval process but it will likely be github
> focused with regular notifications to this wcag2-issues email list for
> substantive changes.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>
>
>
>
>
>
> --
>
> *Wilco Fiers*
>
> Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator
> ACT Task Force
>
>
>


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