Meeting minutes
Introduction, updates.
Upcoming presentations: Virtual TPAC, AC Lightning Talk
Lionel_Wolberger: Reviews status ...
Lionel_Wolberger: Checks session calendar -- WKD is listed
URL for the TPAC Virtual, w3c/
… Exploring making site navigation more accessible, with "well-known destinations"
<gb> Issue 10 Exploring making site navigation more accessible, with "well-known destinations" (by matatk) [session]
Lionel_Wolberger: Note to check slides next mtg
Abhinav: Notes his offer to co-present
Lionel_Wolberger: Also a Lightning talk at AC
janina: Explains Lightning talks
<Abhinav> w3c/
<gb> Issue 11 Nu Tracker: Helping you manage actions and horizontal review tasks from the command line (by matatk) [session]
... Matt has proposed lightning talk at the AC meeting in Japan. We wait for an update from Matt.
… the above link, explaining AC and how W3C works.
… Matt wrote, "we are really happy with the draft we have. Before we can post it, Russell is going to check to be sure we can use a couple of the proposed Bliss Unicode code points."
… for the record, the issue w3c/
Symbols: Issue 240 Way Forward
https://
Russell: Notes mtg with Matt and reviewed candidate response editing as needed
Russell: Have not received edited copy yet
Russell: Intent is to post to list for last reviews before posting on github
Russell: Notes several "likes" on issue recently
<gb> Issue 240 Could we build symbolic annotations with existing Web standards? (by DuncanMacWeb) [i18n-tracker]
Russell: Suggests thread still monitored; we just need to bring this to conclusion
Lionel_Wolberger: So where to we go from there?
... registry spec, https://
… symbols module, https://
Implementation Opportunities
[discussion of issue participants who's who]
Lionel_Wolberger: Suggests emoji markup to show translation across cultural contexts
Janina discovers the Emojipedia: https://
Russell: Notes this is unicode symbols by combining emoji; will be left as a unicode recommendation
Lionel_Wolberger: Summarizes ...
Lionel_Wolberger: Suggests YouTube
Lionel_Wolberger: Notes Global Symbols
Lionel_Wolberger: Dividing implementation into authoring, e.g. marked up content, and rendering
… we have many ideas for both
… To be expanded on in future meetings
Lionel_Wolberger: Reopens question of using the term "symbol" -- because it confuses people
Lionel_Wolberger: AAC not known by the public; emoji may not be helpful
Russell: Yes, also discussed internally
Russell: Symbol not perfect, but well known in the aac world
Russell: ubiquitously used in the aac world; a well known term of art; industry standard
Lionel_Wolberger: Notes this spec potential to impact areas that do not have overlapping terminology
Lionel_Wolberger: Original example was icon, favicon, pictograph, etc
Lionel_Wolberger: They're all target audience, especially icon
Lionel_Wolberger: addresses semantics, not just symbols
Russell: all icons are symbols; but not all symbols are icons
Lionel_Wolberger: Even related terms like avatar, badge
Russell: think of icons as a concise symbol
janina: We are returning to the world of hyroglyphics, this has an ancient history
Symbols: vocabulary
Well Known Destination: Github actions and PRs
janina: We are waiting for Matt to get to the FPWD
Lionel_Wolberger: The name space we will ask for is /ia
… /.well-known/ia/accessibility
janina: The W3C will make the decision on the slash prefix
… we met with Web Security back in Seville regarding this
… they encouraged us not to put everything under /a11y
<Abhinav> https://
Lionel_Wolberger: The current WK URIs for which W3C is change-controller, are:
… change-password, csvm, dnt, genid, tdmrep.json, void, wot
<Abhinav> https://
Lionel_Wolberger: There is also did-, and did.json registered by CG and WG and not by W3C
Abhinav: As of now, IANA does not seem to support name-spaces.
Lionel_Wolberger: The IANA page lists Mark Nottingham as the expert contact
janina: We should go through the W3C TAG via the official IANA/W3C liaison.