Meeting minutes
<PaulG> Stepping away for a minute. But I have an agenda topic. Jun 2 pronunciation meeting presentation from Dan Tripp on data-ssml NVDA plugin https://
Agenda Review & Announcements
gautierchomel: I will have less time for this meeting, as I'm now co-chair for a group. Still want to join as often as possible
Recap of Adapt TF Symbols workshop
matatk: (about the link above) Some material we produced in a workshop run by ADAPT. Progressing the work of bringing symbols to the web, was the goal of this workshop.
matatk: Essentially the goal is to bring these concepts and the Bliss symbols to the web. We are now expecting to achieve the goals with existing HTML standars as the Bliss alphabet is going into unicode, which is a key part
matatk: There are still some concerns with rendering for example, however we already have some ideas how to tackle them, for example using Ruby for this specific concern.
matatk: We are going to revise all of our prototypes, our explainer and our vertical slice. For this we are working with many (Bliss) experts
matatk: If we have important development news, we will point you to it / keep you up to date
matatk: You can also join the ADAPT group, if you are interested
New on TR
Roy_Ruoxi: Nothing new this week
Spec review requests
Horizontal Review Request for DID v1.1
<matatk> w3c/
<matatk> Due: 2025-05-25
<Roy_Ruoxi> our tracker
matatk: We got a few weeks with this spec. Quite low level, however very interesting. We already reviewed the original spec
matatk: Oh, niklasegger reviewed this. I think we can close this one
Web Neural Network API
<matatk> w3c/
<matatk> Due: 2025-06-20
<Roy_Ruoxi> w3c/
matatk: Thank you Chiara for reviewing this one. She had a few suggestions for improvement
matatk: The first sugesstion with the introduction may not really be applicable as it might be sufficiently low level. The output as far as the spec is concerned is not going straight to human
matatk: Maybe a point the spec should add to the accessibility section, similar to your feedback on 2.1.8 Image Captioning
matatk: (2.1.11 Emotion Analysis) Really important point you have here and we should definitely highlight this issue. Key issue about bias
<PaulG> https://
matatk: Overall, the are a couple of things we can do. We can think of which one of these we would like to add to an accessibility consideration section, probably all of them. However, we still need to think about the last to points, as we are not sure what to propose here
PaulG: The specs (see link above) should be in sync.
Fredrik: There are some highly political and philosophical questions. Should you highlight sarcasm? Should you highlight sarcasm? (Support to Paul's point about people being left behind who can't see an uncanny AI-Image, not know to take this image not literally. For people to be fully included this information needs to be conveyed)
Pronunciation TF
<PaulG> https://
PaulG: Dan wrote a plugin and showed in this YouTub-Video that AT can pick this up and it can be used to enhance pronunciation (data-ssml property)
Comment review requests
CSS Update (Paul)
<Neha> exit