Re: APA Adapt Task Force Teleconference - Monday 13 Feb 2023 Agenda

Hi all,

Minutes from today can be found at  https://www.w3.org/2023/02/13-adapt-minutes.html and below in plain text.

Best regards,


Matthew

                             – DRAFT –
                  APA Adapt Task Force Teleconference

13 feb 2023

   [2]IRC log.

      [2] https://www.w3.org/2023/02/13-adapt-irc


Attendees

   Present
          -

   Regrets
          -

   Chair
          Lionel_Wolberger

   Scribe
          Lionel_Wolberger, matatk

Contents

    1. [3]Accessibility 4 Children
    2. [4]Adapt wiki: Symbol CR and Registry FPWD are not
       mentioned
    3. [5]Gap Analysis
    4. [6]Symbol Module Implementations
    5. [7]Gap Analysis
    6. [8]Symbol Module Implementations
    7. [9]Summary of resolutions

Meeting minutes

   General announcement: TPGi webinar that touches upon Symbols:
   [10]https://www.tpgi.com/

   webinar-february-14-at-12pm-et-exploring-new-accessibility-fron
   tiers-with-tpgi-and-the-w3c/

     [10] 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: [11]https://www.w3.org/2023/

   01/30-adapt-minutes.html

     [11] 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

      [1] https://www.w3.org/


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

      [2] https://www.w3.org/2023/02/13-adapt-irc


   [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.

   [12]https://www.w3.org/TR/aac-registry/


     [12] 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. [13]The Adapt TF will take on the development of the AAC
       Registry.

-- 
Matthew Tylee Atkinson (he/him) 
-- 
Principal Accessibility Engineer 
TPG Interactive 
https://www.tpgi.com 
A Vispero Company 
https://www.vispero.com 
-- 
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. 
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful. 




On 10/02/2023, 23:12, "Sharon D Snider" <snidersd@us.ibm.com <mailto:snidersd@us.ibm.com>> wrote:


CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.


Hi all, 
Please review the agenda for Monday's WAI-Adapt TF call and let us know if there are any other topics that need to be added. 
Chair: Sharon 


* Update on A11y4Children 
* Reminder: Symbol CR and Registry FPWD are mentioned on our wiki 
* Gap Analysis [from matatk] 
* Symbol Module Implementations [from matatk] 
* Test to show rendering symbols do not 'break' existing pages [from matatk] 
* Review open issues 
* Recruiting 


The teleconference information is at: call info - adapt <https://www.w3.org/2017/08/telecon-info_adapt> <https://www.w3.org/2017/08/telecon-info_adapt&gt;> 


Time: 


* 10:00 a.m. Eastern 
* 05:00 p.m. IS 
* 03:00 p.m. UK 
IRC access: 


* An IRC (Internet Relay Chat) channel will be available during the call at: https://irc.w3.org/?channels= <https://irc.w3.org/?channels=> <http://irc.w3.org/?channels=adapt>adapt <http://irc.w3.org/?channels=adapt&gt;adapt> 
* The server is irc.w3.org <https://irc.w3.org/> <https://irc.w3.org/&gt;> 
* The port number is 6665 
* The channel is #adapt. 
* You can write any name as a nickname 
Resources and useful links: 


* Wiki <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&amp;si=8000000004174048&amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>; <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&amp;amp;si=8000000004174048&amp;amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f&gt;;> - this page has links to all our work 
* Mailing list archives <https://lists.w3.org/Archives/Public/public-adapt/> <https://lists.w3.org/Archives/Public/public-adapt/&gt;> 
* Web-Based Surveys (WBS) <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49LdqK1N4hm1W1N81nQ3Cfv3hw1N4K5047V2&amp;si=8000000004174048&amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f> <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49LdqK1N4hm1W1N81nQ3Cfv3hw1N4K5047V2&amp;amp;si=8000000004174048&amp;amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f&gt;> 
* Adapt source repository issue tracker <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RpW3H3bfK1LyzF74W1vp1&amp;si=8000000004174048&amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f> <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RpW3H3bfK1LyzF74W1vp1&amp;amp;si=8000000004174048&amp;amp;pi=8e540703-aba8-4282-85a0-c6cb1d664a5f&gt;> 


Regards, 
Sharon Snider 
IBM Design ► IBM Accessibility Team
(512)965-3957 
www.ibm.com/able <https://www.ibm.com/able> <https://www.ibm.com/able&gt;> and w3.ibm.com/able <https://w3.ibm.com/able> <https://w3.ibm.com/able&gt;>

Received on Monday, 13 February 2023 16:11:52 UTC