W3C

– DRAFT –
APA Weekly Teleconference

23 Jul 2025

Attendees

Present
Fazio, Fredrik, Gottfried, janina, JenStrickland, JonCohn, matatk, mike_beganyi, niklasegger, PaulG
Regrets
Gottfried_Zimmerman
Chair
Matthew
Scribe
JenStrickland, Gottfried, matatk

Meeting minutes

Introductions amongst the group for new member, Tiffany.

<JenStrickland> My internet is out and I'm on a hotspot. I'm not getting a strong enough signal to hear what people are saying, so I can't scribe after all.

<Gottfried> I can take over, Jennifer.

<Fazio> +1 great group

Agenda Review & Announcements

matatk: Upcoming presentation from Lola et al on Accessibility Compatibility Data

<Fazio> I will be presenting on Maturity Model at AAATE

Gottfried: AAATE conference in Cyprus

https://aaate2025.eu/

<Fazio> https://aaate2025.eu/world-wide-web-consortium-w3c-accessibility-maturity-model/

matatk: Vote on APA re-charter, decision hopefully next week by AC
… Our current charter expires next month.
… Hopefully no problem for invited experts.

TPAC 2025

https://www.w3.org/2025/11/TPAC/registration.html

matatk: Registration is open. Fee waver for invited experts. Also W3C fund for inviting experts for other costs.

w3c/tpac2025-breakouts

matatk: Call for breakout sessions. Apply if you have something new to say since last TPAC.
… Time slots on Wed and other days this time.

https://www.w3.org/2025/11/TPAC/schedule.html

<Fazio> We don't have any Maturity Model Meetings scheduled

Fazio: APA sessions?

matatk: There is some working time scheduled, we (APA) might use it.
… We did not ask for a group meeting for us, but we can discuss on proposing a breakout.

Comment review requests (requiring attention)

Add hover/focus/long-press triggering delays to CSS

w3c/a11y-review#205

matatk: We hadn't looked at it in detail, but now closed. They changed its name.
… Addition to a pop-over feature.
… Any concerns?

PaulG: Hover delays are reasonable.

matatk: Better way to do what you can already so.
… We can close it.

Comment review requests (in progress)

CSS Overflow Navigation Controls (Carousels)

source: w3ctag/design-reviews#1037

tracking: w3c/a11y-review#242

matatk: TAG is working on a comment on this issue.
… Accessibility community raised concerns.
… They made the CSS inert property value the same as in HTML.
… Other concerning things.
… We might want to ask for some more specific parts.

Connect HTML spec up to new CSS `interactivity` property

source: whatwg/html#10956

tracking: w3c/a11y-review#231

matatk: Will this allow to accidentally break the uninert of subtrees?

Here's a comment that may answer the question about un-inerting: whatwg/html#10956 (comment)

matatk: Can somebody else look at this?

<JenStrickland> matatk I can't find my comment on it.

matatk: This is must about making CSS and HTML behave the same on inertness.
… Please look at tracking issues in APA repository, and discuss them first here among us. Later, we can post them to the mailing list.

JenStrickland: I will take a look at the issue of uninerting
… Looking at it quickly, inertness seems to be determined by the host language. How can accessibility concerns be taken care of?
… Can somebody like Steve look at this?

matatk: It depends whether the inert attribute takes precedence.

<PaulG> https://github.com/whatwg/html/pull/10956#discussion_r2096188289

<PaulG> "host language" is HTML

JenStrickland: As long as HTML is prioritized over CSS, seems okay.

CSS Update (Paul)

No updates

matatk: Accessibility guidance on anchor positioning - please contribute on this

w3c/a11y-review#230

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

Succeeded: s/inert/uninert

Maybe present: source, tracking

All speakers: Fazio, Gottfried, JenStrickland, matatk, PaulG, source, tracking

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