W3C

– DRAFT –
APA WAI-Adapt Task Force Meeting 13 November 2023

13 November 2023

Attendees

Present
Abhinav, Janina, Lionel, Lionel Wolberger, matatk, Roy, Russel, Sharon, Wolberger
Regrets
-
Chair
Sharon
Scribe
janina, Lionel_Wolberger, matatk

Meeting minutes

<gb> Action 247 Symbols Explainer Made Available as HTML Pages on GitHub (on ruoxiran) due 2023-10-30

Welcome, general updates

New Meeting Time

janina: Sounds like the core group is fine with Tuesdays at this same time

Sharon: Next week is Thanksgiving in the USA
… and in December the 2nd half starting the 11th I have vacation

RESOLUTION: Task Force weekly teleconference will move to Tuesday 10AM Boston as of next week Nov 21sat

Thanksgiving week meeting yes or no?

Sharon: No objection

RESOLUTION: Adapt TF shall meet next week on 21-November

Roy_: I will show the chairs and facilitators how to use the calendar

matatk: (Matt notes the IRC topic was incorrect. Janina told us how to run /topic)

Issue 240 discussion (Unicode / Registry) 

russell: At the link w3c/adapt#240

<gb> Issue 240 Could we build symbolic annotations with existing Web standards? (by DuncanMacWeb) [i18n-tracker]

russell: CookieCrook spoke of using polyfills
… emojis can now be defined by stringing together different emojis
… for example, a wmoan man and child make a family

janina: Has authoring come up at all in this discussion?

russell: There are hundreds of symbol sets now.
… they have some overlap, as well as non-overlap
… so given set A and set B, there will be symbols in both sets, as well as some symbols in "B" that are not in "A"
… is that what you mean by authoring?

janina: If we go to unicode what do we give website content creators to add as the code to embed (or markup) their content to deliver on the promise of personalizable symbols
… to be overly specific say whitehouse.gov wishes to add symbols
… would they add unicode? We would still need the registry.

matatk: Regarding authoring, I see the concern. It's about looking up the right concept and seeking the right ID
… whether that ID is a BlissID or a Unicode value, we get a non-ambiguous ID

janina: That's my point -- we would still need authoring support

matatk: Unicode does give a full textual basis for the character

russell: the issue is not the mapping of a single code point to a single concept

matatk: THe issue is that there is no clear delimiter. A string of code-points will not be clear
… let's say you have code points A, B, C, D, E; you dont know if it is ABC and DE, or A and BCD and E

russell: No, they have a solution to delimeters
… the issue is that there is no symbol in Bliss Symbolics to match any arbitrary contstructed group of symbols A, X, Z

Lionel_Wolberger: Personally struggling how to do a visual representation, and how to describe that nonvisually

Lionel_Wolberger: We have several needs; unique and reliable identifiers.

Lionel_Wolberger: Don't recall Adapt wrestling aggregated symbol entities

Lionel_Wolberger: The idea of aggregated symbols is new.

Lionel_Wolberger: Unicode is maintainted by whatever bodey, so our Registry would be more responvie; approved sooner and more able to provide new entity values more promptly

Lionel_Wolberger: Bliss symbols are community responsive, so unicode doesn't add value, it just another organization holding dissemination back

matatk: looking forward to the graphic Lionel and Russell develop to illustrate this

matatk: We are trusting Bliss to represent community fairly

matatk: Not sure how promptly other symbol sets catch up, or how BCI vs Unicode is a factor there

russell: Unsure what experience with these communities among us on the call?

russell: Many other sets are full package solutions
… ARASAAC is constantly adding symbols, depending on what the immediate need is
… COVID drove the addition of symbols
… Bliss also get requests from device manufacturers
… growth is organic and every symbol set grows at its own pace

Lionel_Wolberger: Want to bring us back to support for content creators/publishers; Without that how to do that?

Lionel_Wolberger: Recalls recently iphone showing up with all kinds of unicorns? How does that illustrate

russell: Possible, but not realistic

Lionel_Wolberger: We can take as an axiom, that Bliss Symbolics will likely never be capable of addressing all possible symbols, as even if it did encompass all symbols at a given moment,
… the next moment a new symbol may spring into existence that is not in BCI

janina: With that in mind, all we need to do is give the reasoning as to why this is a good starting place
… and a sufficient mechanism to add to that registry

<gb> Action 247 Symbols Explainer Made Available as HTML Pages on GitHub (on ruoxiran) due 2023-10-30

 well-known URI for accessibility proposal/discuss. include in Gap analysis (Lionel) https://github.com/w3c/adapt/wiki/Gap-Analysis

matatk: Have started from user perspective by writing an Explainer first

matatk: See three distinct needs; yielding three short specs

matatk: Main would be use of combo of well-known-uri plus relations to be used in a rhel

matatk: e.g. help for site, or help for in page page help

matatk: a11y statement is one obvious, but COGA has research for multiple destinations

matatk: Second is taking a SAP proposal -- when at the A11y statement, what actually is in it?

matatk: Potential for specifying what's included in machine readable way, at least a note of what should be there

matatk: WKU isn't about content of what's in an a11y statement

matatk: Third is what we discussed with Reporting API PEOPLE -- what do we mean by "reporting" for a11y

matatk: either auto or semi-auto reporting tool that produces report from the DOM

matatk: Reporting also of "I'm a user having problem X" which may go to a different endpoint

matatk: Expect to get these drafts out this week!

Abhinav: Are you proposing three different end points?

avilar: thinking in terms of endpoints; we need reporting results which has at least two end points

matatk: what goes into a11y statement that might be machine readable is not natively WKU; but we want to figure that out

matatk: Then there's what WKU is intended which we also need. All three are related.

Lionel_Wolberger: Yes, we need to timebox 240 plus WKU!

<Roy_> https://www.w3.org/groups/tf/personalization-tf/calendar/

<Roy_> https://www.w3.org/Guide/meetings/organize.html#calendars

<Roy_> https://www.w3.org/groups/tf/personalization-tf/calendar/

<gb> Action 247 Symbols Explainer Made Available as HTML Pages on GitHub (on ruoxiran) due 2023-10-30

Summary of resolutions

  1. Task Force weekly teleconference will move to Tuesday 10AM Boston as of next week Nov 21sat
  2. Adapt TF shall meet next week on 21-November
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Lionel_Wolberger

Maybe present: avilar, Lionel_Wolberger, Roy_, russell

All speakers: Abhinav, avilar, janina, Lionel_Wolberger, matatk, Roy_, russell, Sharon

Active on IRC: janina, Lionel_Wolberger, matatk, Roy_, russell, Sharon