Meeting minutes
agenda
Agenda Review & Announcements
Enhancing IDREFs
<matatk> whatwg/
matatk: adding to the ability to reference elements by an id
<matatk> For context: gaps in the web platform: https://
matatk: would like everyone to have a look at this thread. we might need to add accessibility requirements. some concerns have been raised around one of the popular suggestions. We need to get people to think about it, so we can contribute ideas.
<matatk> APA-focused tracking issue (public, but APA-focused comments): w3c/
JenStrickland: good to see this kind of open discussion is happening and that accessibility is already being considered
JenStrickland: it is good to see this type of problem solving and creating possible solutions
matatk: to make accessibility work, you have to have certain guarantees. And there are a lot of from tech architecture group members, a lot of accessibility people on here as well
<chiace> 1+
JenStrickland: do we have assistive tech vendors involved. we need to make sure vendors like Freedom Scientific and other AT need to be involved.
PaulG; sounds like the issue won’t be felt hard on AT. The browser vendor will need to populate the accessibility tree.
chiace: we do a bit of research about AT but more from an AI perspective
matatk: what would we like the agenda items to be for a discussion. 1) will it be a smooth transition for AT. How would you deal with content changes? Opacity of selector to a developer.
matatk: we might want to have a breakout at TPAC on this. chiace will think if there is another agenda to add.
matatk: obviously we are concerned about accessibility, but we are trying to provide a more neutral area for discussion.
matatk: we would like to do this more, finding out about things earlier and providing input early. Then we can flag accessibility when we think it is crucial.
TPAC 2025
matatk: deadline for breakout proposals is 22nd of October
<matatk> https://
janina: epub has asked for our joint meeting to occur ahead of TPAC. any sensitivity to the date, I’d like to know
JenStrickland: travelers to Japan: if you take any medications make sure you have the proper paperwork to bring that medication into Japan.
<JenStrickland> Information regarding Japan and medications: https://
<JenStrickland> See also: https://
<matatk> Visit Japan Web: https://
matatk: go thru the Visit Japan site before you go to Japan. It is worth doing in advance. Most people will need to fill it out.
<Fazio> https://
Fazio: WhatsApp group link for TPAC, helpful to connect and talk to others
Issue tracking
New Charters
MEIG
<matatk> w3c/
matatk: Media and entertainment interest group - we have a good relationship with them. I don’t see anything concerning here.
janina: the would love us to update the MAUR, but we don’t have the time.
JSON-LD WG
<matatk> w3c/
matatk: this is the charter we are reviewing. I don’t see anything hugely concerning. They do mention accessibility. The do have a new standards like YAML mapping.
matatk: does anyone have any concerns?
janina: i think we are good (no concerns)
New on TR
Semantic Sensor Network Ontology - 2023 Edition
<Roy_Ruoxi> - tracker: w3c/
<Roy_Ruoxi> - spec: https://
matatk: we can come back to this one
Spec Reviews
matatk: CSS UI one that Paul looked at. Next one is on geolocation. I have some privacy concerns I will file separately. Jen looked from an a11y perspective. We are okay with this.
Screen Orientation
<matatk> w3c/
<matatk> Previous review outputs: https://
matatk: we’ve looked at screen orientation before. api exposes what orientation the screen is in and gives you events that you can handle. we have previous review inputs
matatk: first thing we want to do is check that our accessibility concerns are addressed. does anybody want to have a look at this particular one. timeline is mid-october. anyone want to volunetter to review? niklasegger and Eric_hind volunteered to review.
DAPT
<matatk> w3c/
matatk: dubbing and audio profiles for ttml (is what I think DAPT stands for). this review is due on 18 of October.
We have janina and frederick assigned
Issue Tracking
Incubation: Scoped Focusgroup
<matatk> w3c/
matatk: Scoped Focus Group proposal from OpenUI. Jeffrey added teh a11y tag.
<matatk> explainer from Open UI: https://
matatk: about focus management, trying to reduce the need for roving tab index code. creating a way for the browser to handle this instead of the developer having to write this in javascript. all sounds like a reasonable goal to me.
matatk: they are corresponding to APG patterns
PaulG: I’ll look at the explainer. I think there is a big miss on orientation. I’ll dig into this.
janina: for a non-visual user, you don’t want the screen to reorient itself just because you picked up the device
PaulG: there are situations where in responsive something might be a tab list turns into an accordion, because it is responsive, it needs to change.