Meeting minutes
Agenda Review & Announcements
matatk: We've got loads of new and traditional people. No Janina though, since she's AFK on vaycay.
matatk: Along a sort of reasonable list, there will be introductions galore.
TPAC 2024 Planning
<matatk> https://
matatk That's the page where we list all our TPAC meetings. Fairly light this time.
matatkMost meetings are on the Friday. Four there and one or two each of the other days.
matatk On Monday, there will be a meeting with CSS, full of different issues.
matatk We are mong other things working on speech and so forth
matatk Tuesday is APA time, TF work and so forth.
matatk Wednesday is breakouts day. Lots of things we might want ot attend. Some things we may have proposed ourselves. David in particular.
Fazio AI Accessibility Auditing Tools including a demonstration.
matatk The Advisory committee meeting tends to be Wednesday morning. The AC is the body of people who can vot3e on stuff the W3C does.
<Fazio> AI Auditing Tool Demo Breakout w3c/
matatk Thurday we are meeting with AGWG on the morning and then also late morning we are meeeting with WHATWG. We will be talking with WHATWG primarily about Symbols and well-known destinations, both with Adapt We will also cover anythign about pronunciation.
matatk Friday we have a few things (this is all in the wiki, don't worry about the truncated infos here, all you want to know is there(: first APA WG working time; then late in the morning a joint meeting with Timed Text and Media and Entertainment IG (looking at how we could update MAUR); 1400-1600 is ARIAWG - watch out for updates - one thing may
be ththe authoring practices and some proposals from us; and the last thing on Friday is Publishing Maintenance WG. Check out hte minutes from last week for more on that last one.
matatkAs I was going through this page and creating it I noticed that ehre were a lot of meetings which may be interesting to APA members to ttend.
matatkThere is a meeting on Tue morning between CSS, OpenUI and WHATWG. OpenUI are working on making native elements more flexible to avoid the creation of custom emlements. The platform should be better for people to use out of the box as it were.
matatkThe other thing is a meeting between ARIAWG and Immersive Web WG. That one might be interesting to anyone with a yen for XR.
matatkIf you are an ivited expert to this working group you can attend remotely for free.
matatkYou get to attend the meetings where the group you are a member of are present, if you are an invited expert of the APAWG for instance.
matatk There is information about this in more detail:
<matatk> https://
matatk The remote participation is fantabulous and highly recommended.
Task Force & Deliverables Updates
matatk Skipping ahead since we have other things coming up.
New Charters Review
Roy: We've got two new charters!
CSS Working Group Charter
<Roy> - charter: https://
<Roy> - issue: w3c/
roy: CSS working group
roy: Lots of publications, but everything looks good to me.
PaulG: They have so much work in front o fthem and they do a lot of good work.
PaulG: There is a small pecentage we will need to track.
RDF Datasets Canonicalization and Hash WG recharter
<Roy> - charter: https://
<Roy> - issue: w3c/
Roy: RDF Datasets WG
Roy: That's some low leveldata stuff.
roy: From my perspective, I would let them go do their thing.
matatk: Some context: charters tell us the scope of what groups are doing, usually for two years. We're more interested in how the work gets done (whether it supports or pormotes a11y for instance).
Explicit Review Requests
WebXR Device API
<Roy> - issue: w3c/
<Roy> - tracking: https://
<Roy> - spec: https://
<Roy> - a11y explainer at: https://
Roy: WebXR Device API
Roy: We have already tracked this document since 2019. Last time we reviewed this document was 2022.
Roy: They want an a11y review.
Roy: There was no a11y considerations in the document as fars I could find.
matatk This is areally big one. It should have an a11y considerations section. We should write some kind of a "have you considered this"-section as well.
matatk: Fredrik and I will be doing this.
CSS Update (Paul)
PaulG: One interesting update.
<PaulG> w3c/
<matatk> ^ Add hover/focus/long-press triggering delays to CSS
PaulG: The OP is suggesting adding something to CSS to handle delays in popovers. Some dynamic content disclosures were to be easier to code.
PaulG: This feature would make the timing available so that you don't have to script it. Tooltips are used as an example.
PaulG: If someone wants a tooltip to appear after a smal delay for instance.
PaulG: There would be things moved from JS to CSS. Seems an interesting use case. Adn some support is there as well.
PaulG: Fun to keep an eye on.
matatk: I've added the a11y/tracker label so it shows up in our dashboard.
matatk: We will talk more on this.
matatk: That will be all for today. Thanks everyone here and note here.