W3C

– DRAFT –
WAI-Adapt Teleconference

27 Jan 2026

Attendees

Present
Abhinav, janina, Lionel_Wolberger, matatk, Russell
Regrets
-
Chair
janina
Scribe
janina, matatk, Lionel_Wolberger

Meeting minutes

Symbols

Russell: There's an AI-based project that Jutta is involved with, have mentioned before.
… There's a fellow called Hannes Ljusås who has developed a system for displaying Bliss symbols, and generating Bliss symbols using SVG.
… I've talked to him about this project, he's interested.
… The code for the display system has been open-sourced.
… It's a great system. It's built in layers. It has almost bytecode to generate each line segment in a symbol. Above that is characters. They're based exactly on the Unicode set.
… Because the Unicode encoding is not finalized, he's used his own set of codes, but they map 1:1 with the (proposed) Unicode character set.
… I think it's going to be very useful for us.

<Russell> https://github.com/hlridge/bliss-svg-builder/blob/master/docs/get-started/characters-bcodes.md

janina: Since you've been involved in Jutta's AI project, do you know its legal status? Is it intended to become law or regulation?

Russell: it's exploratory so far
… It's about can we use AI as a communication assistant

janina: I was wondering about the intent on the legal/policy/governance side

Russell: I've not heard anything on that in the discussions so far.

janina: Please could you socialize in the Bliss meeting that <ruby> is gathering consensus and that we think we can indicate everything we need via lang=zbl

<matatk> s/UI as a/AI as a/

matatk: Looks impressive; will look at how to integrate it

janina: Could we get Hannes to join the group? If he loves to write code, we could use that...

destinations

Abhinav: The merge is done

janina: Parts of the explainer are destined, we think, for RQTF's AI and Accessibility document
… I plan to revisit this in February

Abhinav: Matthew is working towards a best practices document

matatk: I can share a branch end of this week

matatk: Tasks: updating the existing explainer for destinations
… What we want to do, end up with a non-normative specification note track, a 'statement'
… high level- if you want to do X, here is how to do it
… I am copying the best parts of the explainer into this document

janina: +1 to making it a statement

matatk: We will have to check back in with COGA, as they were critical to this agenda

janina: COGA is in our timeline, likely just after we finish curating the list of destinations

Proposed DDs: https://github.com/w3c/adapt/issues?q=is%3Aissue%20label%3Aproposed-destination

matatk: COGA is likely interested in dynamic, parametrized destinations, such as "take me back to the start of this application process"

janina: We are not specifying the UI, we are providing what is needed to find these destinations

Lionel_Wolberger: We assessed three DDs and marked them as accepted or not, comments on the github issues

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Succeeded: s/@@@@@/Hannes Ljusås/

Succeeded: s/UI/AI

Failed: s/UI as a/AI as a/

All speakers: Abhinav, janina, Lionel_Wolberger, matatk, Russell

Active on IRC: Abhinav, janina, Lionel_Wolberger, matatk, Russell