Meeting minutes
Agenda Review & Announcements
<janina> https://
<janina> https://
Janina: For interesting A11y tools, on LaTeX - a Rust based replacement is on the way called TYPST. It will support valid HTML.
Janina: This may be worth following around HTML markup support for A11y. Just FYI.
New on TR
Spec review requests
matatk: No meeting next week as Matthew and Janini are away.
Input events
<matatk> w3c/
<matatk> Due: 2024-12-19
matatk: Input events require some clarifications. It will be closed soon, waiting for responses around editing.
WebRTC API
<matatk> w3c/
<matatk> Due: 2025-01-31
matatk: Web RTC - had no issues with it (issue 98 - RTT). We will let this issue go and close it.
WebCodecs
<matatk> w3c/
<matatk> Due: 2025-02-28
<Fredrik> By the way, it#s "clear audio".
matatk: Web codecs, issue 97 around routing/stream splitting. Would like to keep open but not required. Maybe file new issue with new use case concerns would be useful - 2nd screen in the MAUR as clean audio.
<janina> http://
webauthn-3
<matatk> w3c/
<matatk> Due: 2025-03-31
matatk: Web authentication 3 due end March. API for public key credentials. Not known how high or low level this is. Or is it low level and A11y considerations need to be pushed down? There are A11y considerations in the spec.
<matatk> Accessibility Considerations: https://
<matatk> Changes since last version: https://
matatk: Review of delta since last version also available
<Roy_Ruoxi> review history: w3c/
matatk: Need APA review for these two sections. Volunteers?
Fredrick: Will volunteer to do the reviews
Fredrik: Will volunteer to do the reviews.
Dr_Keith: Will also volunteer and cross check with Fredrik
Dubbing and Audio description Profiles of TTML2
<Roy_Ruoxi> - issue: w3c/
<Roy_Ruoxi> - ping: w3c/
<Roy_Ruoxi> https://
Roy_Ruoxi: Audio Description profiles was reviewed and to be processed but is now blocked by missing sign off. Suggest closing off to allow process to continue and we make a new issue.
<matatk> Follow-ups noted at TPAC: https://
matatk: We propose to follow up in a new thread - no serious concerns raised.
Roy_Ruoxi: will leave transition process comment on this.
Comment review requests
[css-overflow-5] Focus order of generated controls
<matatk> source: w3c/csswg-drafts#10912
<matatk> tracking: w3c/
matatk: For this, it was about scrolling, controls, asking how it works (CSS scrolling)- not clear.
<matatk> We have an update on the scope of this CSS question, and how it relates to the wider project of CSS carousels and scrolling...
<matatk> Explainer for CSS carousel (mentions scroll buttons): https://
<matatk> TAG design review thread for CSS Scroll Buttons: w3ctag/
matatk: Wider project with CSS to make decent CSS based carousels for a11y. TBD about wider attempt to improve scrolling.
<matatk> About Explainers: https://
Matatk: The CSS explainer notes that they could focus but don't have to. And how it fits into the wider project related to carousels and generalized interaction.
PaulG: Noted that order based issue was closed and makes sense. But the context of when they want to implement their new proposal isn't clear.
<matatk> Related (I think): CSS inert: w3ctag/
PaulG: Other concerns around inert and searchability
matatk: Will pass on these concerns to the CSS group.
<PaulG> https://
matatk: next steps are to ask questions to the CSS group based on what-if scenarios
Other business
<matatk> Digital Accessibility User Requirements: https://
<matatk> https://
matatk: Clean audio quick review in media accessibility doc