W3C

– DRAFT –
APA Weekly Teleconference

06 August 2025

Attendees

Present
chiace, Demelza, Fredrik, janina, JenStrickland, JonCohn, matatk, Neha, Roy_Ruoxi, steveF, tsaulter
Regrets
Dr_Keith, Paul
Chair
-
Scribe
Fredrik, janina

Meeting minutes

<janina> Date 06 Aug 2025

Agenda Review & Announcements

matatk: A few things somewhat drumrollable.

matatk: A certifiably quite cool rechartering of APA has preceeded this meeting. Whoop woop!

matatk: We are racing ahead as unusual.

janina: I am pleased beyond gobsmackment that the charter sailed through without the slightest squeak of concern or opposition. That is a tribute to Matthew's getting our horiyontal review work better organized, the development, and so forth. Kudos to each and everyone!

matatk: An update on the horizontal review: we have a11y-request as a repo on Github where official review requests go (we don't use those ones until we're really sure we want to post things, also not for the results of the review because of a new system coming up) - most request threads most ofus aren't going to touch...

janina: There are ticks that have to be set in teh horizontal review, and they are processed through these types of Github repos.

matatk: THe other type of thing that we need to track is the rvarious discussion threads cropping up on any kind of repo on Github where peoplemight say "we need some a11y input on this" for instance. In those instances they attach a label to their thread and we get told about it. We used to get told about it through a11y-review.

matatk: That side is to track where we have been brought in to comment or where we want to comment.

matatk: Said repo was a11y-review but is now a11y-tracking.

matatk: There is also a repo that Roy has set up to track the a11y of a spec through its entire life, called a11y-longitudinal-tracking.

matatk: Any confusion on the repos should be reasonably mitigated by redirects on Github.

matatk: Finally, a reminder that Lola Odelola is giving a talk on the 20th of August (in two weeks) which will be very interesting. It will bridge the gap betweeen the baseline featured set that is highly marketed safe-to-use borwser features for web developers and assistive technologies. Lola will come and describe that work and we will have a

discussion about it.

matatk: Look in the APA calendar for links to the project information - there are links aplenty.

TPAC 2025

matatk: Just a reminder that the fudn for applying for support if you are an IE closes this week.

matatk: You can register for TPAC already.

<matatk> https://www.w3.org/2025/11/TPAC/

janina: I'm having trouble with the informational data relating to the hotel and transportation that the W3C is pointing us to. Thsi matters gereatly for my getting my submission for funding support in on time and in correct shape.

<Roy_Ruoxi> https://www.w3.org/2025/11/TPAC/venue.html

matatk: There is a very helpful team, with an e-mail address on teh botom of each TPAC page, who may be able to assist in rather many of the issues here. The team can resolve most things and are really on it.

<JenStrickland> Here's the URL to apply for funding: https://www.w3.org/2025/11/TPAC/registration.html#funds

matatk: Scheduling: I'm working with the scheduling team on some new planning.

matatk: There is alos a place to propose breakout sessions now.

<matatk> Breakouts: https://www.w3.org/2025/11/TPAC/breakouts.html

New charters

Roy_Ruoxi: Nothing.

New on TR

<matatk> https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/

matatk: The Vision for the W3C has been published as a W3C statement. The AC voted in support of this. This is the highest level of maturity in the statement track, by the way.

matatk: When you get to statement, it means that the whole of the W3C is behind this work.

matatk: It is rather a short document, maybe even shorter than the blog post announcing it.

Spec review requests

IMSC Text Profile 1.3

<matatk> w3c/a11y-request#116

matatk: THere's jst a pign on it. Some assignemtns to it were gotten last week. Just a reminder that they asked for ther review to be completed until 16 September (the changes are really small, see the comment or in the changelog in the document).

<matatk> Reminder of horizontal review process: https://www.w3.org/WAI/APA/wiki/Horizontal_Review#For_Specifications_2

CSS UI 4 - interestfor et al

<matatk> w3c/a11y-request#118

matatk: It's about hwo the UI stuff is rendered.

matatk: Specifically about new properties; that's the specific ask for APA

matatk: Notes the Explainer that accompanies this pub

matatk: On popovers and how the interaction works

matatk: In part this is from the Open UI project

matatk: Interest attribute -- standardizing what has been introduced ad hoc by devs

matatk: Common example is hover over a github issue that provides info on that issue

matatk: One can avoid actually opening the issue because the popover provides info you need in so many instances

matatk: TAG had a conversation on this and a positive outcome

matatk: Notes, Mat, Paul, and Dr Keith assigned

Comment review requests

matatk: WebNN

WebNN Accessibility Considerations

<matatk> w3c/a11y-tracking#244

matatk: We've discussed ... Response looks good to me

<matatk> I left some comments: webmachinelearning/webnn#869 (comment)

matatk: They're waiting -- actually not sure

janina: Doesn't appear it's to us for some action/step?

matatk: No.

matatk: Nice to see they created a PR for it

Anchor positioning advice

<matatk> w3c/a11y-tracking#230

matatk: Notes Neha has added example and updated

matatk: Thanks! We should try it out

matatk: Good progress!

CSS Carousels

<matatk> w3c/a11y-tracking#242

matatk: Have been of interest to mmany incl TAG

matatk: Not an element

matatk: attributes some of which may be of concern ...

matatk: Inert is one

matatk: Scrollmarkers another

matatk: Seems an over-reach in the case of Scroll markers

matatk: Would be nice to have a declarative approach

matatk: Tab Atkins has proposed Cascading Attribute Sheets as declarative response

matatk: seems neat

matatk: We'll see and we'll track, of course

matatk: TAG is working on a comment trackable on this issue; probably this week

<matatk> Info on Cascading Attribute Sheets: https://gist.github.com/tabatkins/4074abaf486af5b3f7ac289737e216e4

JenStrickland: Wondering whether we're imposing too much on the user

JenStrickland: That devs will unintentionally introduce a11y barriers

matatk: God point of deterministic -- Could be a disadvantage

matatk: The concern about inadvertent is exactly why we didn't care for Inert

matatk: Think the Cascading attribu can help because you have to actually write it

matatk: Also notes this repo:

<matatk> Gaps in the web platform: w3ctag/gaps

matatk: It's super interesting stuff!

TPAC Support due Friday

matatk: Two kinds:

matatk: IE qualify for TPAC fee waiver

matatk: Other relates to travel expenses

matatk: Can always ping support team for any concerns!

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

Diagnostics

Succeeded: s/neet/neat/

All speakers: janina, JenStrickland, matatk, Roy_Ruoxi

Active on IRC: chiace, Demelza, Fredrik, janina, JenStrickland, JonCohn, matatk, Neha, Roy_Ruoxi, steveF, tsaulter