Meeting minutes
Announcing special APA WG call tomorrow on Accessibility Compatibility Data
<matatk> https://
<matatk> https://
Lionel_Wolberger: I agree with Matt, anyone interested in baseline should attend
Lionel_Wolberger: another related link, Adrian's blog post https://
Symbols
<matatk> Explainer updates: w3c/
<gb> Pull Request 323 Symbols explainer post-workshop (by matatk)
matatk: Agreed (in https://
Lionel_Wolberger: This is a critical change for our 'shop front'
… can we also do our home page?
janina: No, as I need to first edit the APA home page, then do the Adapt Task Force
… let's focus on being ready for TPAC
<Russell> https://
<matatk> ^ workshop spreadsheet
<matatk> Also, symbols-related issues: https://
<matatk> Tool links from Russell: https://
<matatk> ... and https://
<matatk> ... also https://
<matatk> Russell: FontForge can't do what we want. Glyphs mostly can - though it's commercial software. Icomoon is expected to be completely supporting color SVG glyphs, but it doesn't yet.
matatk: Glyphs can maybe do what we need, but needs a license
Lionel_Wolberger: Is the mini2 license enough? Here is the compare page, https://
Russell: I will do a review of existing software and find a viable candidate
Annalu: I will have use cases this week as well.
Destinations
janina: Update from Lisa. The answer, is help only.
matatk: Help and contact?
matatk: Question, would linksets support not repeating the content on every page?
Lionel_Wolberger: We discussed using <link rel="linkset"> in the <head> to point to a centralized JSON linkset.
… This allows us to declare all Well Known Destinations from a single location.
… The linkset can include rel values like adapt-symbols, adapt-preferences, etc.
… Phil Archer recommended linksets, and they align well with our technical goals.
… To bridge the gap until user agents support linksets, we can use a simple JavaScript polyfill.
… The polyfill could fetch the linkset, parses it, and exposes destinations for use by scripts or UAs.
… This avoids repeating <link> tags on every page and supports modular deployment.
… we note that the IETF WKU (well known URLs) cannot support this use case
matatk: This approach is simple to implement
Talking about proposed destinations - e.g. this one that isn't: w3c/
<gb> Issue 311 related
Lionel_Wolberger: Decided, we will label 'accepted destination' for destinations that we accept
I made a label for this: https://
Abhinav: I would like to talk about how this concept can be used in Agentic contexts
… GenAI agents could use it to navigate to the login page
Lionel_Wolberger: Let's discuss next time
janina: Agentic is an AI type class