Meeting minutes
DD
matatk: One PR merged, a second in process with feedback provided
Abhinav: Will followup
matatk: Asks Abhinav if anything particular to discuss?
Abhinav: no
matatk: Notes upcoming TPAC planning ...
matatk: Expect we'll propose a breakout to show where we are
matatk: Are there any cross group we want?
matatk: We should consider for a few weeks, but not very long
Abhinav: Recalls we were going to show to COGA
matatk: Maybe how many COGA present?
matatk: People will be expecting these kinds of conversations; we will be ready by then
janina: I think both symbols and DDs are close enough architecturally (particularly DDs) that they are done, so we don't need cross-group meetings. We are cleaning up our demos and docs, so we can show how to use it. So now we are evangelising, looking for implementations.
… No specific standards stuff other than maybe a registry for symbols.
… To keep the momentum going, we need to think what we did last TPAC and see how things have changed. Need to not spin wheels.
… Socialising this and encouraging people to implement will be a heavy lift. We want to concentrate on that, not tell people at TPAC that we will be doing stuff.
… Re COGA, we could meet with them, they have interest in the list of destinations. But even that list may change
… and it could change after TPAC.
matatk: Mostly agree though we need to figure out sub sites.
janina: What do we need to do, and we could invite Lisa/COGA to this call, should do that sooner rather than later.
matatk: we have subsites and context dependent destinations
matatk: we should have small scale implementations to show
matatk: would allow for expirimentation and sanity checking with others
janina: I think we want to be in WCAG3 as in 'this is how you do it' - definitely accessibility statement and we need to get that into WCAG3 if we possibly can. That door won't be open forever.
… now is a good time to get new features in to WCAG.
… because it's a major release. 3.1 would be harder. The architectural implications would be harder.
… We didn't plan for it but it is a great opportunity and would be really unfortunate if we lost it. We will have more opportunities if we are part of WCAG. We should feel some urgency around this.
matatk: +1
janina: That probably means showing something to the WCAG chairs first, and then maybe to the group on one of their calls.
Symbols
Russell: Asks if anything while I was away?
matatk: Regretably not!
Russell: Have update regarding font; working as we concieve
Russell: Progress from Hannes Ljusås in Sweden; he's created a bliss font using unicode private
Russell: Using SVGs
Russell: Have asked if he would do a demo for us
Russell: Believe he's programmatically creating them, he's not a font person
Russell: believe using node.js and paper.js
matatk: Didn't we see this in a repo? Something similar?
Russell: Yes, but don't think with the same components
Russell: He's programmatically generating as opposed to using font design sw
Russell: Believe his interest is similar to diacritics but in Bliss
Russell: It's about indicators, still controversial with Michael
Russell: So it's close to what we need, but not precisely
Russell: Asks if 10 June would be OK?
matatk: Works!
Here are the upcoming Adapt calls: https://
matatk: If programatically creatable we have more opportunities, like a web app
matatk: thinking aloud how to take advantage of a programmatic fonts approach
Russell: Recall we have Global Symbols; and vendors support symbols other than their own so map as we concieve mapping
Russell: continues thinking aloud of possibilities ...
Rusell: not sure his font stuff is github, but confident it's floss
Russell: he's also working toward unicode inclusion for Bliss; he knows and works with Michael
Russell: Even if an independent thinker
matatk: Notes our approach is already implemented by this work! We're filling in
[discussion on mechanics of a demo next week]
matatk: Let us know when confirmed