Meeting minutes
Administratrivia and Logistics
matatk: Giving regrets in advance for next week
Lionel_Wolberger: We will still meet next week, thanks Matt for being on the TAG
Destinations
Abhinav: Did everyone review PR 326, https://
matatk: I call attention to PR 325, w3c/
… nothing blocking merge of 325
… 326 requires a reading by Janina and/or Lionel
Lionel_Wolberger: Ack
janina: Will get to it soon
Destinations 'Name Game' -- Renaming?
matatk: (from last week) The name "Well Known Destinations", while an apt description of what we do, has a confusing overlap with the "Well Known URIs" spec that inspired us (but this now works in a very different way).
janina: There is valu in looking at a renaming
… there are advantages to naming discussions, as they are a chance to involve wider WAI team
… and potentially AGWG
… as part of our interest is a 'well known destination' for the accessibility statement
… two components
<janina> ~ack ja
Lionel_Wolberger: I recall that Matt, when he joined the task force, investigated the overlap of destination, purpose and action
matatk: Yes, we had modules defined, all of which sought to add semantics to web pages to make them more accessible
… the scope featured action, destination and purpose
… action was to be attached to buttons and other triggerable affordances
… will it open a popu up? will it send you somewhere
… destination is similar, when you click a link, where will you end up
… purpose was for a form field, information on what the form field would require
… purpose was needed, as the HTML auto-complete cannot be applied to all form elements, but purpose could mark up a fieldset as a whole
… and auto-complete cannot achieve this fieldset role
… after much discussion, the task force converged on links and attributes we can add such as 'rel'
… which can be added to links, or anchors
… A close examination of destination, action and purpose seemed to highlight their similarityh
… is it significant that one is marking up a button, another is a link?
… in practice, links may be coded as buttons and vice a versa
… as a test of the need for having two ideas, say action and destination, and tried to think of cases where they would code different values
… (a falsification logical test) - L
… and we did not find any
Lionel_Wolberger: If we can assert that destinations and actions are the same, that's a step forward
… as we will be covering more scope
matatk: Use standard 'follow your nose' HTML procedures, make it discoverable
Lionel_Wolberger: Let's look at standard, recognized
… waypoints ( a word from wayfinding)
… familiar, core
… We encourage discussion on list, as we need time and examples for naming
Symbols
Russell: The software is a bit complex, I have a call in to support
… I may need some support from font designers
janina: +1 to bringing on other people with known expertise in designing the fonts and/or symbols that we need
… keep in miind, how much of this expertise do we need to standardize
Lionel_Wolberger: I would be pleased to collaborate with Russel, but that's two newbies, not sure we would finish in reasonable time
Russell: Agree
<matatk> PR needing review for updates to Symbols explainer: w3c/
Russell: We do not need font design, it's font creation with multi-colored SVGs and overlapping components
… these font creation software expect the user is creating a glyph of a character that will be solid
… but our SVGs, and emojis, have overlapping lines
… that tend to be merged by these software packages
… Glyphs seems to support it
… an engineer who writes font software would be perfect
… a font designer has their heart in another place
janina: We need an engineer, not a fine art student