W3C

– DRAFT –
APA Weekly Teleconference

30 Oct 2024

Attendees

Present
Fazio, Fredrik, janina, janina_, JenStrickland, matatk, mike_beganyi, niklasegger
Regrets
Angela_Young, dfeltham, Dr_Keith
Chair
Matthew
Scribe
janina_, niklasegger

Meeting minutes

/join #rqtf

<matatk> s/\/join #rqtf//

Agenda Review & Announcements

New Charters Review

Publishing Maintenance Working Group Recharter

<Roy_Ruoxi> - charter: https://w3c.github.io/publ-maintenance-wg-charter/

<Roy_Ruoxi> - issue: w3c/strategy#481

Roy_Ruoxi: No new charter this week, but follow up to last week.

<matatk> Minutes from last week on this: https://www.w3.org/2024/10/23-apa-minutes#0795

matatk: I forgot to ask this question: Someone from the group told me they were expecting more future changes but we were still asked for the review. Due to the confusion, I wanted to ask the group again

Roy_Ruoxi: I think we already can review it now

janina: I volunteer to look at this charter, need a few days for this.

matatk: Due day is next week, so we need to keep this in our mind

HR A11y Review Comment Tracker

Allow any element to be the child of a custom element (parser weirdness permitting)

<Roy_Ruoxi> - issue: whatwg/html#10722

matatk: Seeing this for the first time, but I see Lea and Dominic in this thread with good points. I can't immediatly think of a show stopping issue here, still cautious if we lose information this way?

PaulG: I think it's the right idea and want to see this go on, but there will be of course future work for ARIA and browser vendors for the mapping

matatk: I think we have the beginning of a comment here. I will add our points to the GitHub issue thread

Gottfried: We need to keep ordered list, unordered list and description list in mind here

JenStrickland: Guidance on custom elements vs native elements is in my opinion important here. When to use what

Would also like to hear Steve F on this topic ...

<matatk> https://www.w3.org/TR/design-principles/ (maybe something in there about when to use custom elements)

matatk: Very good points here. To answer JenStrickland: I think there might be something in the web plattform design principles. I will look into this

matatk: I will assign myself to the tracking issue

Explicit Review Requests

Vision for W3C

<Roy_Ruoxi> - issue: w3c/a11y-request#93

<Roy_Ruoxi> - Note: https://www.w3.org/TR/2024/NOTE-w3c-vision-20241018/

Roy_Ruoxi: Important document, would like feedback on this one

matatk: Would any of us like to review it?

Fredrik: I will do it.

<JenStrickland> I'm already giving it a review for PWE, as well. Good coverage!

WebXR Gamepads Module Level 1

<Roy_Ruoxi> - issue: w3c/a11y-request#30

<Roy_Ruoxi> - tracking: https://www.w3.org/WAI/APA/wiki/WebXR_Gamepads_Module_-_Level_1

<Roy_Ruoxi> - ping: immersive-web/webxr-gamepads-module#61

<Roy_Ruoxi> - self-review: immersive-web/webxr-gamepads-module#55

Roy_Ruoxi: We reviewed it in 2022. They gave us new feedback recently

matatk: I'm happy to do this one, because I did the first review

The user must be able to disable use of the Vibration API

<matatk> Proposed issue: w3c/a11y-review#215

matatk: Another topic: When we do spec reviews, we take a good look at the documents, but this process takes sometimes a lot of time. There are situation where this is a sort bottleneck. I would like to address this. See my proposed idea: w3c/a11y-review#215

matatk: A template for creating issues already exists, we can use this. I will also create a wiki entry with guidance

<Fazio> +1 to Matthews comment

<PaulG> +1

<mike_beganyi> +1 also

<Gottfried> +1

<Roy_Ruoxi> +1

<JenStrickland> I'm struggling with absorbing all the content, so trusting y'all. I did hear a few things that sounded on-target. :)

<JenStrickland> +1

(matatk showing his VIbration API comment, asks if it is okay)

<niklasegger> +1

<Zakim> janina, you wanted to suggest inserting RFC2119

<matatk> Do you approve of the proposed APA comment on Vibration API?

<matatk> +1

<JenStrickland> +1

<niklasegger> +1

<janina> +1

<mike_beganyi> +1

<Roy_Ruoxi> +1

(matatk going over the issue template/process and explaining the steps)

<matatk> Here are i18n's instructions (which we will adopt and adapt for APA WG repos etc.): https://w3c.github.io/i18n-activity/guidelines/review-instructions.html#writeup-issue

mike_beganyi: Where do we give "official" feedback on comments like yours here (Vibration API)

matatk: Either here on the call or through Cfc. You can also comment on the list or through a comment/ thumps up on the tracking issue

New on TR

nothing new

CSS Update (Paul)

<PaulG> https://github.com/w3c/csswg-drafts/issues/4165, https://github.com/w3c/csswg-drafts/issues/10605, https://github.com/w3c/csswg-drafts/issues/9793, w3c/csswg-drafts#10674

PaulG: There are four issues, which haven't been discussed yet.

matatk: Any news on the TPAC issues?

PaulG: Nothing new

Actions check-in

mike_beganyi: I think I was assigned to an issue, but unfortunately I didn't get a proper notification

<matatk> w3c/a11y-request#92 - mike_beganyi

<JenStrickland> Reviewing w3c/csswg-drafts#10605 I do see a concern that if an image or video is loading and causes a page shift that is an accessibility issue, as well as an issue for web performance.

Other business

Be done

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

Diagnostics

Succeeded: s/present_/present+/

Succeeded: s/present_/present+/

Warning: ‘s//join #rqtf//’ interpreted as replacing ‘’ by ‘join #rqtf/’

Succeeded: s//join #rqtf//

Warning: ‘s/\/join #rqtf//’ interpreted as replacing ‘\’ by ‘join #rqtf/’

Failed: s/\/join #rqtf//

Maybe present: Gottfried, PaulG, Roy_Ruoxi

All speakers: Fredrik, Gottfried, janina, JenStrickland, matatk, mike_beganyi, PaulG, Roy_Ruoxi

Active on IRC: Fazio, Fredrik, Gottfried, janina, janina_, JenStrickland, matatk, mike_beganyi, niklasegger, PaulG, Roy_Ruoxi