– DRAFT –
AGWG-2025-12-16

<MURATA> +present

<Jennie_Delisi> * This is the group's way of showing wanting to keep Chuck around - if nobody scribes....he has to stay?

Documentation own scriboing will be posted

<Laura_Carlson> https://www.w3.org/WAI/GL/wiki/Scribing_Commands_and_Related_Info

Chuck: Any introductions?

<alastairc> Noting this is our second Makoto (Murata) we have another one called Makoto Ueki.

Murata is first time at the meeting - welcome!

Chuck: Announcements: Last meeting today in 2025
… thanks to all

Rachael: There will be a CfC over the COGA Issues pages

Hidde: wanted to double check, we'll also start the CFC for publication of WCAG-EM 2.0 as a draft note this week

draft note publication

WCAG 2.x Issues https://lists.w3.org/Archives/Public/w3c-wai-gl/2025OctDec/0064.html

Chuck: WCAG 2.X issues

mbgower: Not enough issues right now, probably next Friday
… new items will be introduced first meeting 2026, then there will be ample time to review
… meetings are on Friday 11:00 each Friday EST - next on January 9th
… still looking to co-facilitator fot WCAG 2.X issues task force

<kenneth> https://www.w3.org/groups/tf/wcag2x-backlog/calendar/ (will be extending the recurrence into 2026 soon)

Chuck: any questions about TF?

Subgroup Preparation

Chuck: soft reset to reset work done by TFs - next round is planned via survey to register interest to participate

<alastairc> https://docs.google.com/spreadsheets/d/1dXGNNBReQgjHSDNJ02hA9sbb5R17mpN7YnDyC2GDzCI/edit?gid=0#gid=0

Chuck: also updated handbook

Alastair: Going to subgroups

<ljoakley8> i missed the survey, how can I get added to a group?

alastairc: people were allocated to groups, balanced out a bit

alastairc: we can add names here (for those who missed survey)
… specified time slots for groups

image subgroup pacific-friendly time
… meeting times for subgroups are available via the link above

<ljoakley8> Can the spreadsheet url be chared in chat?

<Chuck> https://docs.google.com/spreadsheets/d/1dXGNNBReQgjHSDNJ02hA9sbb5R17mpN7YnDyC2GDzCI/edit?gid=0#gid=0

<ljoakley8> thank you

alastairc: (reads out subgroups and time slots)
… conformance subgroup is a special case, shorter, only 8 weeks - hopefully can be closed b< Feb / March

alastairc: Anyone who did fill in survey but can't make group?
… those who didn't fill out survey - who wants to join subgroups (preferably those with low attendance)

<Glenda> I would like to be in User Orientation please.

Illai: missed survey - can error & help or structure group

alastairc: put Illai under errors & task

<ljoakley8> Please add me to the sub group Input and Focus

<Adam_Page> I’d like to join “Input and focus, interactive components” please

alastairc: if people use multiple groups, that's fine, but work will happen during main meetings, so you should have prime group
… better not swap group - overhead for catching up to see where the group stands, can slow down group

<Zakim> ShawnT, you wanted to ask about outside participation?

ShawnT: sign language - a developer would want to participate - can someone from outside enter?

kevin: Can participate if he/she becomes invited expert - ping Kevin

alastairc: General thing: if you know someone with expertise, let chairs know - needed on voice input for example - then get in touch

Poornima: Could continue participate if times fit in error subgroup

alastairc: people in top line are facilitating the group
… select a co-facilitator to help co-ordinare

John Kirkwood: Should be in conformance subgroup

alastairc_ We aim to have not too many

alastairc: The main aim of subgroups to come up with a proposal that will then come to the main group
… so no one sidelined

<MURATA> I’m afraid I’m too sleepy to stay awake, so I’ll drop off now. Thank you.

kirkwood: This (conformance) is my area of expertise

<alastairc> https://docs.google.com/document/d/1WkYBc_9PowZRcxp1ld13jkA2pHd-vvmeBf9sZzUDjJQ/edit?tab=t.0#heading=h.gjdgxs

alastairc: (explains what subgroups are doing)

<Rachael> Also, a new folder for next year with all the content we are reviewing today https://drive.google.com/drive/u/0/folders/1OoZzR8FgtsqHYLdYrMjBVY34hQEJkd8d

alastairc: for details see link above

alastairc: work on content, come up with proposals, to enable parallel work

<AWK> Is there a different document for the conformance subgroup?

alastairc: 4 hrs each week incl. meeting time
… like go to the folder for each subgroup
… work based on the structure of WCAG 3 document

this link goes to the doc with links to all subgroups https://drive.google.com/drive/u/0/folders/1OoZzR8FgtsqHYLdYrMjBVY34hQEJkd8d

alastairc: take what is in the current draft, update it, flesh it out
… for not non-guideline things for policy notes conformance - you should come back with a PR (pull request) or explain why a PR is not a good idea
… going from developing to refining, and hopefully to mature
… for guideline content, start from the editor's draft, create a brach and a PR to that

for non-guidelines work , the scope is less refined to we need to define what is in and out of scope
… check that subgroup participants have all they need (docs, permissions)
… keep minutes during the meetings

also people who join asynchronously should be able to stay up-to-date
… we will have regular status updates
… all run from the W3C calendar
… you can also keep notes in a separate tab of your subgroup working document
… no one is required to use Guthub, but one sub each group should be able to work with Github
… assuming 8 weeks chunk

come earlier or later so not all come in at the same time for review
… define the order you go through requirements; keep in mind user needs as documented
… one scope and documentation is set, look at issues, examples edge cases to refine requirements
… start of informative documents
… around week for bring back as progress update to the group so group can react and point out what might be missing or going wrong
… around week 8 we can then look at a PR to discuss
… for non-guidelines work, this is aimed at defining goals, look at previous documentation, setting out scope - agree on scope - is it reasonable
… another difference is it is not quite as easy, will need more discussion

alastairc: Any questions

kirkwood: Can you clarify what the expectation of the final product of the group will be?

alastairc: PR on updated content of editor's draft
… eg, wording updated, some tests defined, beginnings of informal documentation

Rachael: Output will be content for review by main group: PR, document, presentation on the topics the group is working on

kirkwood: Topics are changing?

Rachael: work is based on the guidelines of the ed draft - other issues are for conformance and policy, for example
… subgoup work has been successful - ability to split and bring back to main group has been successful over last 2 years
… lets continue this way

<kirkwood> great thank you

<kevin> Massive +1 to how well sub-groups are working!!!

SydneyColeman: Can other people participate?

alastairc: If others can join that is fine, they need to become WG members / invited experts
… the goal of the subgroup is to bring back work to main group, so there should be no issue about representation

Rachael: Add people at people pf beginning of cycle

SydneyColeman: We have experts on media (Youtube) - will discuss how to participate

alastairc: Will habe breakout rooms set up for the rest of the meeting

<tayef> I'm assuming if I'm not in a subgroup I can drop this call?

<Rachael> To all: Thank you for all you have contributed this year. We hope you have a rest filled break and look forward to making progress next year.

<ShawnT> If I have a question, can I ask it in here?