W3C

– DRAFT –
APA Adapt Task Force Teleconference

13 feb 2023

Attendees

Present
-
Regrets
-
Chair
Lionel_Wolberger
Scribe
Lionel_Wolberger, matatk

Meeting minutes

General announcement: TPGi webinar that touches upon Symbols: https://www.tpgi.com/webinar-february-14-at-12pm-et-exploring-new-accessibility-frontiers-with-tpgi-and-the-w3c/

Accessibility 4 Children

janina: We're looking forward to reading about the ontology.
… We should ping the group.

Minutes from our call with ACCG: https://www.w3.org/2023/01/30-adapt-minutes.html

Lionel_Wolberger will contact them.

Adapt wiki: Symbol CR and Registry FPWD are not mentioned

Sharon: Just a reminder on this.

janina: ACK matatk's email about some other APA/TF pages that need updating - will add to APA-plan agenda.

janina: Some of these are pages that we need staff to update.

Gap Analysis

janina: We need to be sure to keep ACCG and COGATF lopoed in. We're looking for curb cuts. We want to reassure everyone that their concerns are taken into consideration.

Lionel_Wolberger: +1

Lionel_Wolberger: We'll carry this as a long-term agendum.

janina: We need to've finished this when we go to our next CR, with the next attributes.

janina: There are mainstream implications of COGA's excellent work.

matatk: I was thinking of the gap analysis action ...

matatk: Namely, why not microformats, etc.

Sharon: Correct, that's where this agendum originates.

matatk: Apologies, I've stalled on this

matatk: I do have Lionel's pointers on this

matatk: I could use a refresh pointer ...

matatk: You did it usefully and structurally off the top of your head! Impressive.

Lionel_Wolberger: Sure

Lionel_Wolberger: Shares screen, recommends screen grab

Lionel_Wolberger: Includes rhel, auto-complete, microformats, css media queries, dpub (using a rhel type approach),

janina: RDF as well?

matatk: Yes, but you were explaining an engineering approach of how to do a good gap analysis

matatk: It's the process I'm trying to get back to

matatk: example, using X is too encumbered

Sharon: I remember now

Sharon: May be in our minutes ... Maybe December?

Sharon: Will dig them up

Lionel_Wolberger: The end point is to dispose of this concern so we never need revisit it.

Lionel_Wolberger: Follow classic engineering gap analysis approach; write it up; make a decision; and file it where we can always find it!

matatk: thanks for the individual help on this. It will help!

Sharon: I dug into the former minutes back to December, and cannot find this

Symbol Module Implementations

Gap Analysis

Lionel_Wolberger: I found six steps, identified by ChatGPT.

Lionel_Wolberger: Pasting here

[1] Identify the item we are focusing on, Define its function

[2] Identify the item we're comparing it to, and identify its function

[3] Identify the gaps or differences.

[4] For each gap identified, assess impact on a simple

[5] Take a decision and Memorialize it

[6] Make the record of the gap analysis available

Symbol Module Implementations

janina: Next steps include meeting with Bliss, Global Symbols, and anyone in COGA who's interested, and extend the current published Registry draft.
… We need to define how to internationalize it. Namely, do the symbols change if the BCI index value/descriptive text are looked up in a different language? I expect the answer to be yes.
… Once we have authoritatively answered this, I can reply on issue 203.

janina: We need to define:
… 1. How to add more languages.
… 2. How to add more symbol sets.
… 3. How to update existing datum points.

janina: We decided the first one was i18n. Roy took an action to reach out to the i18n chair.

Lionel_Wolberger: This is an APA item?

janina: It was being handled by Michael, but we'd like to move it to Adapt.

janina: I don't think it'll impact meeting time much; is a natural vector for recruiting.

RESOLUTION: The Adapt TF will take on the development of the AAC Registry.

https://www.w3.org/TR/aac-registry/

matatk: Regarding 2 above, it will be about mapping to the existing set of concepts; symbol providers will be making their own mappings.

janina: +1; we need to define how they do that normatively.

Lionel_Wolberger: If I'm another symbol set, I want to be attached to it?

janina: You'd be listed in it.

Lionel_Wolberger: I was wondering about this as well as matatk. This is so that the symbols are discoverable? This will be another section of the registry?

janina: yes

Lionel_Wolberger: and 3 above is about how to update the concepts?

janina: yes

janina: People may join us just to work on those things.

matatk: Points out potential issues with W3C maintaing a list of pointers to other symbol sets, these will need to be explored

Summary of resolutions

  1. The Adapt TF will take on the development of the AAC Registry.
Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

Succeeded: s/wirte/write

Maybe present: janina, Lionel_Wolberger, matatk, Sharon

All speakers: janina, Lionel_Wolberger, matatk, Sharon

Active on IRC: janina, Lionel_Wolberger, matatk