Meeting minutes
<SteveF> janina Regrets for today
Agenda Review & Announcements
matatk: No mention of IRC. None at all.
matatk: With respect to the calendar invites that get sent out, we are putting specific issues to discuss into the invites as accurately as possible before the calls. We try to do this first thing in the morning US Eastern Time Mondays. This is to set expectations as opposed to discussing the meta aspects of the issues.
<niklasegger> +1
<Dr_Keith> +1
<Eric_hind> +1
<Demelza> +1
<Fredrik> +1
<Roy_Ruoxi> +1
<nehaj> +1
<gautierchomel> +1
<janina> +1 -- Even shows in console based mutt email!
matatk: We have a long standing thing with the web interface which doesn't put the agenda at the top. But you can when you get into the meetings. And not in the e-mails either, apparantely. We are, however, going to use these listings more. Thanks for keeping up with this!
APA Re-chartering
matatk: The rechartering which we are doing....
matatk: Roy is looking for the link to our draft charter...
<Roy_Ruoxi> https://
<Roy_Ruoxi> github branch
matatk: The charter gives us the ability to do work within the W3C and lists the deliverables which are expected of us. Not just the review stuff, but all the deliverables of the TFs as well, which have expected, though longer, timescales.
matatk: By the end of January, we need to have updated the deliverables from each task force. If any TF is expecting to deliver something within the next two years, we need to know about it.
matatk: We are talking to the TFs of course, lots of TF people are on the call today. Send an e-mail to the chairs, make some noise, to make sure the deliverable you think should be there gets put into the charter.
matatk: It's really important to keep our TF homepages up to date. Now is a very good time to update the TF homepages.
matatk: Has IRC issues (not at all related to above).
matatk: This is a good time to remind people about reporting about bugs in the IRC client. Which totally wasn't done before.
janina: If you havew normative deliverables, which you said you would deliver from your task force but didn't, this has to be explained. It is not hard, but it has to be done.
Spec review requests
matatk: On this one, it's the same three we had beefore. For Input Events, we have a draft comment.
matatk: The idea of drafting commetns is for us to highlight issues we have found. On this occasion we have got a comment but haven't found any issues.
Input events
<matatk> w3c/
<matatk> Due: 2024-12-19
<matatk> Draft comment issue: w3c/
matatk: I'll read it out as well, not just post the link.
matatk: (Reading out the draft comment.)
matatk: Does anyone have an opinion, comment, or other somesuch to share on that comment?
<janina> +1 to the draft!
The draft is not daft.
<Eric_hind> +1
<Demelza> +1
<Fredrik> +1
<gautierchomel> +1
matatk: We also have these other two reviews in progress.
WebRTC API
<matatk> w3c/
<matatk> Due: 2025-01-31
matatk: This is the WebRTC API, the changes specifically.
WebCodecs
<matatk> w3c/
<matatk> Due: 2025-02-28
matatk: There isnt much to mention about the WebCodecs. It's due fofr end of February.
dewisevice.
matatk: I'm working on a draft for a use case collection for the WebCodec wishes we have. Just very simple. Please just e-mail the APA list. That will help us get our collection of use cases together.
matatk: Any use cases?
Fredrik: Sometimes mood music can make it hard to isolate specific voices. Maybe good to filter frequency-wise.
matatk: Plese shout any use cases you have on hand around this or any barriers you have encountered with audio on the web in terms of rerouting, spolitting and so on.
janina: It is sometimes really hard to hear speech synthesizers when there is media playing at the same time. Beinga ble to split AT sounds out to another device s extremely helpful. Hearing different things from different devices affects the perception immensely.
<Dr_Keith> https://
<Dr_Keith> VB-CABLE is a virtual audio device working as virtual audio cable. All audio coming in the CABLE input is simply forwarded to the CABLE output. Used to route sounds to specific devices and software
matatk: That would e all for that, then.
<janina> For Apple: https://
<janina> On Linux: Jack, but Speech-Dispatcher doesn't play nice with jack
matatk: The point of collecting the use cases is, because this is going to go wider than WebCodecs - it will toucn on a lot of things, the collection of usecases will help us map which specs may be affected in the first place, then we can popose what changes we would want to see in those specs to support the user needs expressed.
<janina> On Linux also Pulse Audio, now subsumed in Pipewire
Comment review requests
matatk: No new ones this week, but we'll not want to loose track of this particular one.
[css-overflow-5] Focus order of generated controls
source: w3c/csswg-drafts#10912
tracking: w3c/
matatk: As I mentioned in the agenda, there are a couple of things to unpack here.
matatk: It wasn't clear how big a change they were wanting to make in the keyboard interaction.
matatk: There are some comments on this tracking issue. We had some thoughts when we discussed it. Paul had some interest in it as well and contributed to the discussions in the imnutes.
Eric_hind: I'd be happy to look at this.
matatk: The first thing to do is to let someone independently look at this thread and see what the proposal is here.
CSS Update
PaulG: I don't have a strong opinion about the scrolling issue other than it would be a real disservice if it replaced existing functionality.
matatk: Could you note these concerns on the APA thread we discussed?
matatk: There aren't necessarily deadlines here but the sooner we can get this done the better.
Other business
RQTF's CTAUR doc was published! https://
<janina> On WAI-Announce: https://
matatk: Have a look at the blog post about the CTAUR announcement!
janina: A reminder for the Friday meeting on the Special Music Meeting. One hour ahead of this hour, but on Friday.
janina: Same Zoom coordinates.