Meeting minutes
Introductions, administratrivia, logistics
<matatk> I will be out on the 8th of April, for the W3C AC meeting.
Well Known Destinations
<matatk> Breakouts Day submission - accepted! w3c/
<gb> Issue 9 Simplifying Site Navigation: A Standardized Approach for Accessible Destinations (by matatk) [session]
<matatk> gb, off
Lionel_Wolberger: Two meetings prior to the presentation
Abhinav: We did a previous breakout session
Lionel_Wolberger: Big change from last time, as we are using existing tech and do not need a spec
janina: The main message is, 'you can do this now!'
… we may be able to roll out first on W3C pages, or WAI pages
… 'eating your own dog food' approach
q/
… and we need documentation
Lionel_Wolberger: +1 to having a robust explainer
Abhinav: https://
… https://
<Abhinav> https://
<Abhinav> https://
<matatk> ^ sessions we presented last year (breakouts day 2024)
<matatk> the AC 2024 lightning talk is: https://
matatk: Reviewed strategy for presenting, which slides to re-use
… I could right click and show the HTML
… then outline next steps
Lionel_Wolberger: Feedback: no need for much on WAI-Adapt
… main first message is that we have made PROGRESS, and that we have a very workable way forward based on EXISTING SPECS
… I suggest bringing all the well-known icons onto one slide (currently search, home, cart, contact email). Suggest we add question mark in a circle ('help')
… lastly, suggest adding critical code snippets
<matatk> WKD explainer: https://
<matatk> Oops sorry no, that's out of date now; I have the new one in a branch!
<matatk> w3c/
Lionel_Wolberger: Regarding deploying on W3C I think it's a great idea
janina: I will promote this in WCAG as well, as a location for the accessibility statement
Lionel_Wolberger: (Discussed the heading order)
… on the explainer, add a heading for "Proof of Concept". Keep the sentence, 'UI is out of scope..."
Symbols
<matatk> Recap of Zero Project activities and outcomes: https://
matatk: The idea of 'localizing a symbol set' makes me think, we can address that issue
Russell: If we are going with this implementation based on Ruby with individuals using symbols embedded in their local symbol font
… the act of personalization is done by the local individual selecting the font
… example: An individual using ARASAAC with a particular cultural perspective.
<Zakim> matatk, you wanted to ask about levels of customisation, and process for deployment
Lionel_Wolberger: I see the following unassigned action items
… Set meeting with Jutta
matatk: Was thinking about the base set; the area-specific customizations; and the hyper (personal) customizations.
Lionel: Potential SVG conversion for ARASAAC as a step towards a font
matatk: Don't want to preclude something that we may very well want to support in future - building a font is hard; need a way to patch it?
Lionel: creating a sample font
janina: I will take the Jutta action