W3C

– DRAFT –
AGF-2024-10-28

28 October 2024

Attendees

Present
alastairc, bruce_bailey, JJ, maryjom, mbgower, shawn
Regrets
-
Chair
Chuck
Scribe
mbgower, alastairc

Meeting minutes

scribe

Task Force Updates

JJ: I sent an email with updates when I couldn't make the last meeting. We are almost finished discussing all the 56 A and AA criteria.
… We have generated some index.html files to share with the world
… We will then focus on the low-variation SCs, and then move on the medium-variation.

<Zakim> shawn, you wanted to discuss mobile comment

<shawn> w3c/wai-website#692

shawn: Would be good to update the WAI pages, in the github issue
… Kevin and JJ to action.

michaelg: Aiming to do CFC for changes to 2.2, going out in the next week or so.
… mostly style updates, but a few clarifications of defintions. Should not cause re-interpretations.

<Zakim> shawn, you wanted to ask

shawn: just to let you know, I'll be asking in the next few weeks for an overview on how that is going, and what else is needed going forward.

maryjom: Before my update, I opened a new issue on WCAG 2.2 about a definition, it might impact the CFC.
… a note that isn't marked up as a note.

michaelg

michaelg: oh, the definition about [missed], but it does appear to be a note.

maryjom: My status - I'm doing project planning for out next phase, which is the AAA criteria. Getting a project plan in place.
… I may have a co-facilitator, will say more later. Also, will be working on an explainer for WCAG2ICT. Topics of proper use, what it is and isn't.
… taken a little hiatus, but will get going again soon.

Chuck6: That facilitator conversation, I'm planning on that going through so I can step back a bit on WCAG2ICT.

<Zakim> shawn, you wanted to note next steps and explainer

shawn: We should also update the WCAG2ICT info page to work on the AAA criteria.
… that's great, I just had missed that.

maryjom: We also need to update the co-facilitator bit as well.

shawn: Could I be in-the-loop on the explainer? Need to consider if it goes in the WAI space or TR, or where it goes?

<Zakim> JJ, you wanted to add meeting minutes link to AG Facilitators meeting events in W3C calendar

JJ: Could we add the meeting minutes / URL to the event?
… for this meeting.

Chuck6: Not sure if it's restricted, will see if there's a box for the minutes, then I can add going forward.
… suggestion taken.

<Zakim> bruce_bailey, you wanted to discuss issue number wrt AAA notes

bruce_bailey: Do you have the Id for the issue?

kevin: Re: The explainer, that will be in TR space as a group note. I'll find the PR for it. We can chat later.

<Zakim> JJ, you wanted to ask about subgroup polling

shawn: Is that something different to the policy discussion?

alastairc: Different thing, which hasn't started yet.

JJ: There's a survey/poll going for WCAG3 sub-groups, how's that going?

<kevin> Update to WCAG3 Explainer PR

Chuck6: Got the results, am correlating now, I'll be announcing that tomorrow on the AG call.

Add discussion when best to meet objective - by author or best by user agent #325 w3c/coga#325

Chuck6: [Round robin], no additions.

Chuck6: Shawn sent an email about issue 325 on the COGA repo, wasn't sure what to do with that.

shawn: Came up in a WAI CC meeting, and thought it was relevant here. Did anyone have any input on the discussion?

shawn: The issue is for COGA, but it's wider than that.

Chuck6: We (chairs+kevin) had a discussion with people from the browser vendors, and we'll have quarterly meetings with them.

shawn: Slightly different thing, not only want to have browsers involved in WCAG3, but also we'd like to see if we could encourage / facilitate the browsers addressing some things now. (e.g., focus apearance)

Chuck6: For issue 325, not sure what it means for that?

shawn: Just whether there are existing discussions or things to point towards -- and might want to add links to that issue

Chuck6: Only that we've come across certain outcomes that might be better addressed by user-agents, but nothing definitive yet.

michaelg: Focus-appearance was a sticking point for sure, we got push-back on that, and it was hard to write a rule to cover all the different places to test.

JJ: On the browser topic, considering the new guidelines are broader, could it include OS level things?
… particularly for mobile/ICT.

<Zakim> bruce_bailey, you wanted to ask about IRC dropping

bruce_bailey: IRC continues to drop, any progress?

kevin: haven't got enough data to work out when/what is happening. Happy to continue taking emails for that purpose.

Minutes manually created (not a transcript), formatted by scribe.perl version 238 (Fri Oct 18 20:51:13 2024 UTC).

Diagnostics

Succeeded: s/ and if there's anything else needed/ and what else is needed going forward

Succeeded: s/but we're also eager to have browsers involved in WCAG3/ not only want to have browsers involved in WCAG3

Succeeded: s/point towards./point towards -- and might want to add links to that issue

Succeeded: s/ facilitate the browsers addressing some things now./ facilitate the browsers addressing some things now. (e.g., focus apearance)

Maybe present: Chuck6, kevin, michaelg

All speakers: alastairc, bruce_bailey, Chuck6, JJ, kevin, maryjom, michaelg, shawn

Active on IRC: alastairc, bruce_bailey, Chuck6, JJ, kevin, maryjom, mbgower, shawn