W3C

– DRAFT –
APA Weekly Teleconference

08 Oct 2025

Attendees

Present
Demelza, Eric_hind, Fazio, Fredrik, janina, JenStrickland, matatk, Neha, niklasegger, stevef
Regrets
Alisa_Smith, Gottfried_Zimmerman, Roy_Ruoxi_Ran
Chair
Matatk
Scribe
niklasegger, matatk

Meeting minutes

Agenda Review & Announcements

janina: One special item in the agenda

<JenStrickland> I also have an agenda item.

<JonCohn> pspresent+

<Fredrik> Isn't the whole vibe of Washingotn R-Disabling?

JenStrickland: I tagged you matatk in an issue, a question about issue templates

<JenStrickland> Here's the issue where I created the content: w3c/sustainableweb-wsg#158

matatk: Yes, there are templates. You've reminded me to do the APA A11Y Request template. Also, my colleague works right now on an HTML version of the FAST checklist

matatk: ... You can then fill in the necessary information and get back an GitHub issue

Fazio: Another news: Maturity Model is coming! Get ready for a CfC, please look at it and support it

TPAC 2025

<matatk> w3c/tpac2025-breakouts

matatk: Deadline for proposing breakouts is 22. October, two weeks from today

Prep for 'beyond IDREFs' discussion next week

<matatk> w3c/a11y-tracking#256

matatk: Reminder: Next week we have a discussion about the proposal: Augmenting ID Refs. More information in the linked issue above

<matatk> Alice's concerns on IDREFs: https://notes.igalia.com/XlsPwU5sQfuaWYHwhtBMtA

<matatk> explainer: https://github.com/webplatformco/explainers/blob/main/html-element-references/README.md

matatk: ... it is a massive but really informative thread. Please take a look at it, at the explainer and Alice's concern, so we have a good foundation for next weeks discussion! We need to find a way forward that is constructive for everyone concerned.

<Zakim> janina, you wanted to ask whether there's an actual proposal on the table yet?

matatk: One suggestions from my side is to break this whole thing into stages. This could help with determine who could do it and focusing the research

matatk: Short explanation of this issue: Webpages are nowadays really complex, often different components are developed by different teams and there are concerns, problems with the current situation with duplicate ids. This is an approach to tackle these issues

matatk: We will probably not achieve any big result next week. The goal of next week is, is to provide a space for people to voice their concerns

matatk: There are two proposals: Relative references and scoped IDs

matatk: An interesting question that Janina just raised is: If you call JS to move something in the DOM, should that auto update the selector somehow?

matatk: Please once again look at Alice's concern and the explainer as preparation for next week

<JenStrickland> I will email my IP address to you, matatk.

matatk: I will update the calender for next week

Spec review requests

Screen Orientation

<matatk> w3c/a11y-request#126

<matatk> https://www.w3.org/WAI/APA/wiki/Horizontal_Review#For_Specifications_2 - info on if you want to propose an APA response which will get filed as an issue in the spec's repo

niklasegger: Will you create a tracking issue for this one?

matatk: Let's see if others have input...

Eric_hind: I have a issue and will raise it in the spec repo

matatk: Unfortunately, there is no time left for more spec reviews. Any burning questions left?

(no questions)

matatk: Eric_hind if you have a big issue please follow the instructions of the wiki linked above and in case of a small issue you can directly raise it

Minutes manually created (not a transcript), formatted by scribe.perl version 246 (Wed Oct 1 15:02:24 2025 UTC).

Diagnostics

All speakers: Eric_hind, Fazio, janina, JenStrickland, matatk, niklasegger

Active on IRC: Demelza, Eric_hind, Fazio, Fredrik, janina, JenStrickland, JonCohn, matatk, Neha, niklasegger, stevef