Meeting minutes
<janina> * agenda+ Symbols
Introduction, logistics, updates as needed
Well Known Destinations
janina: Spoke with Rachael and Lisa; Rachael is keen for us to pursue this work. Lisa suggests starting with previous destinations supported by original prototype.
matatk: have begun the action. Merged the current explainers.
Also, Rachael supports Accessibility Statement destination
matatk: In that action I will have updated explainers (now that the pre-TPAC explainers are tagged properly)
… COGA would like a method to indicate the type of resource. E.g., COGA sees different types of help as distinct
… example, human help vs chatbot help
What about something like: Help_Personal; Help_Contextual, Help_General
Lionel_Wolberger: Let's return to the primary use case here
… as a WWW user, I have in mind a well known destination, such as "login". On visiting a site, with Adapt report/specification in place
<Zakim> janina, you wanted to comment on user benefit of wkd
Lionel_Wolberger: I will have a method to invoke that will lead me to the "login", whether on 'huge-etailer.com' or 'joes-bagels.com'
janina: With an adjustment. The driving COGA use case is to minimize distractions.
… the modern WWW is loaded with things that distract people with cognitive disabilities
… it would help to highlight the focus task, and graying out the distractions
… login is one. Finding the help you need is another.
… and accessibility statement is highly desirable.
… COGA brings our focus to distractions. Those users literally cannot login, due to the distractions
matatk: Distractions and navigation.
matatk: ... are two distinct use cases. Some implementations may help with both at the same time
… filtering out items in a document fragment is another challenge
… distractions, we have found in the course of running this task force, are subjective
… I suggest, if we address distractions, we keep in mind these challenges when we approach that topic
… I believe the TF turned towards navigation in response to these challenges
<Zakim> matatk, you wanted to ask about distractions
ack, janina
janina: In large part, agree
I think this may be the feature Janina is referring to wrt Safari: https://
janina: Both are similar, just different ways of getting at it
Lionel_Wolberger: I appreciate the deep thinking behind your seeing them as two paths to the same goal. Maybe the way I stated it was too implementation-based, and not classic use case language.
… But that said, I don't find them similar. I love the challenge of limiting distractions, or implementing simplification - it's one of the first things I got excited about when joining this TF. And since then we've seen things like ChatGPT do summaries of content.
… But I find them very different use cases. I didn't recall that we turned to navigation because we couldn't solve distraction; I just thought that being able to reliably get to these destinations, rapidly, is the key part. There is a commonly held idea that there's a vocabulary developing for areas the site should have (e.g. log in,
accessibility statement, account, ...)
janina: I do not disagree, it's just how we talk about it. I am stressing, don't just talk about it as navigation.
… talking about it from the POV of distraction implies that you have a <span> in mind
… a target on the page, the region on the page
Lionel_Wolberger: +1
Symbols
Russel: Looked into taking ARASAAC and converting it into a font, using a tool
… these bitmaps are large and rather complicated in order to tell what they are
… emojis are optimized for rendering in small sizes
… I started by exploring converting to SVG
… tried the bitmaps, as bitmap fonts are supported
… a typical ARASAAC symbol is 500px high, while a bitmap font is much smaller
… Ruby: We see a challenge I would call, 'double ruby'
Russel: Encoding: Instead of using the Bliss and Unicode encoding, I am considering
… using the private use area
… I believe there is a registry tracking 'private use area' usage, I do not believe it is being maintained
We should most certainly not create an occidental solution!
<Zakim> matatk, you wanted to ask about SVG conversion; talk about touch points; comment on 240
matatk: Would like to hear more about the SVG conversion. Noting, the WHAT-WG people were highly confident that highly sophisticated SVGs can become fonts.
… so we need to look closer at what happened there
matatk: Touchpoints: Let's keep in mind those cases that are more challenging like plurals, conjugations. I believe we have a list
matatk: We are getting feedback on Issue 240, comment from i18n-WG
matatk: Private usage area: I suspect our unicode advocates will not find this approach as suitable
<Zakim> janina, you wanted to note the need for details as one touchpoint
janina: higher resolution: clarifying that ARASAAC needs more resolution than emojis may be a critical touchpoint to the font conversation
russell: Intriguing that BLISS is amenable to lower resolutions, but ARASAAC is not
… Private use area: I am suggesting we could use Private use Area code points rather than Bliss IDs
… I have argued against Bliss encoding as this seems like a particular 'spelling' for a symbol, and these spellings do change
… for example in the case of a rotary phone leaving the vernacular, so the pictagram changes, and then we have a new spelling and a new Bliss ID
<Zakim> matatk, you wanted to make suggestion for some concrete and discrete next steps
matatk: Propose using github wiki for collaboration on the primary symbol touchpoints
<Lionel_Wolberger> +1
<janina> +1
janina: 'testing the limits of the approach'