W3C

– DRAFT –
APA Weekly Teleconference

21 May 2025

Attendees

Present
Ananya, Dr_Keith, Fredrik, Gottfried, janina, matatk, Neha, niklasegger
Regrets
Chiara_Cerretti, Gautier_Chomel, Paul_Grenier
Chair
Matthew
Scribe
niklasegger

Meeting minutes

<janina> Meeting?

Agenda Review & Announcements

(New member, short round of introductions)

(Welcome to the group Ananya)

Reminder: Demo of data-ssml attribute for pronunciation (2025-06-02)

<matatk> https://www.w3.org/events/meetings/03fa8f75-a761-43ba-a0d7-e98171d31a63/20250602T110000/

matatk: Rebooted the Pronunciation TF for new approaches. One of them is data-ssml, a demo is now available, see link above for more information.

<janina> DAISY and Epub requirements gathering:

<janina> Draft: https://daisy.github.io/reading-apps-ux-reqs/requirements/draft/#user-requirements

<janina> Issues: https://github.com/daisy/reading-apps-ux-reqs/issues

matatk: ... as APA members you should be able to join this meeting, if you have problems get in contact with me

Charter

<Fredrik> I'll drink to that reboot!

janina: With respect to ADAPT, I think it might useful to toss in one sentence talking about symbols, because we have a whole new approach.

janina: Probably a CfC next week, only smaller changes expected like the ADAPT sentence

<janina> DRAFT RESOLUTION: Proceed with current Charter draft with minimal "Deliverables" edits

RESOLUTION: Proceed with current Charter draft with minimal "Deliverables" edits

TPAC 2025

matatk: Mid-November 2025, in Kobe (Japan)

matatk: We will be asking all taskforce who they want to talk to and. what about in the following months

matatk: Show and tell about our current projects

New on TR

Spec review requests

<matatk> Reviewing Janina's proposed comment on Audio Session API: w3c/a11y-review#232

<Fredrik> q_

matatk: Are we fine with Janina's proposed comment? Any questions?

Fredrik: My only concern: It should not only address TTS / Screenreader, to specific.

janina: I will do an editorial change so more general ATs are considered

matatk: The spec mentions the interaction between the audio that's coming out of the browser and the underlying platforms. So you can hear for example a personal assistant over the browser sounds. I think the spec should give clearer examples for this. Also, they need to include their privacy section

janina: I'm happy to take these considerations into a redraft.

<Zakim> Gottfried, you wanted to propose a "politeness" system for audio such as with aria role "alert".

Neha: (Question about Fredrik's point, what exactly he meant, resulting in Janina explaining "earcons", so a short, distinctive sound that is used to symbolize a particular event or convey other information.)

<Zakim> matatk, you wanted to mention ariaNotify API

<matatk> ariaNotify explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md

matatk: This discussion reminds me of ariaNotify. From the abstract "We propose an imperative notification API designed to replace the usage of ARIA live regions in scenarios where a visual "live region" isn't necessary."

Comment review requests

[css-anchor-position-1] Improve accessibility guidance

<matatk> source: w3c/csswg-drafts#10311

<matatk> tracking: w3c/a11y-review#230

matatk: Popups may appear outside the viewport, so you have to write custom JS to fix that. Anchor position is a new CSS solution to tackle this problem

matatk: Someone wants to contribute to this, so improving the accessibility section of this document. Should work together with Paul for this one

Neha: I will do it

matatk: Perfect, I will assign you

CSS Update (Paul)

Actions check-in

Other business

(end of meeting)

Summary of resolutions

  1. Proceed with current Charter draft with minimal "Deliverables" edits
Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

All speakers: Fredrik, janina, matatk, Neha

Active on IRC: Ananya, Dr_Keith, Fredrik, Gottfried, janina, matatk, Neha, niklasegger