Re: Agenda: APA WEEKLY Teleconference; Wednesday 1 February at 1500Z

Hi all,

Minutes for today can be found at https://www.w3.org/2023/02/01-apa-minutes.html and below in plain text.

Best regards,


Matthew

                             – DRAFT –
     Accessible Platform Architectures (APA) Weekly Teleconference

01 February 2023

   [2]IRC log.

      [2] https://www.w3.org/2023/02/01-apa-irc


Attendees

   Present
          Fazio, Fredrik, janina, matatk, mike_beganyi, PaulG, Roy

   Regrets
          Alisa, Gottfried, Niklas

   Chair
          Janina

   Scribe
          matatk, mike_beganyi

Contents

    1. [3]Agenda Review & Announcements
    2. [4]Open CfC Elevating Maturity Model to Task Force httpS://
       www.w3.org/WAI/APA/task-forces/maturity-model/
       work-statementtatus
    3. [5]APA Rechartering: Ready for CfC? https://github.com/w3c/

       apa/blob/charter-2023/charter.html
    4. [6]New Charters Review https://github.com/w3c/strategy/

       issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+
       requested%22
    5. [7]Explicit Review Requests https://github.com/w3c/

       a11y-request/issues
         1. [8]Web Content Accessibility Guidelines (WCAG) 2.2
         2. [9]RDF Dataset Canonicalization
    6. [10]A11y Review Comment Tracker https://w3c.github.io/

       horizontal-issue-tracker/?repo=w3c/a11y-review
    7. [11]new on TR http://www.w3.org/TR/tr-status-drafts.html

    8. [12]CSS Update (Paul) https://github.com/w3c/css-a11y/

       issues
    9. [13]Actions Checkin (Specs) https://www.w3.org/WAI/APA/

       track/actions/open
   10. [14]Task Force & Deliverables Updates
   11. [15]Other Business
   12. [16]be done
   13. [17]Summary of resolutions

Meeting minutes

  Agenda Review & Announcements

   janina: standard agendum plus new item. no specific
   announcements on the agenda

  Open CfC Elevating Maturity Model to Task Force [18]httpS://
  www.w3.org/WAI/APA/task-forces/maturity-model/work-statementtatus

     [18] https://www.w3.org/WAI/APA/task-forces/maturity-model/work-statementtatus


   <Roy> [19]https://www.w3.org/WAI/APA/task-forces/

   maturity-model/work-statement

     [19] https://www.w3.org/WAI/APA/task-forces/maturity-model/work-statement


   <Fazio> I'm here to answer questions

   janina: reminder that the CFC, proposes subgroup of maturity
   model and making them their own TF. a lot of votes have come in
   but please get votes in. CFC closes at midnight Boston time
   Friday

   Fazio: do we want to bring up questions about equity

   janina: discussed last week. thought equity questions were
   about the maturity model itslef and not the work statement

   Fazio: that's correct, Janina

   janina: if there are ways to scope in something we aren't
   currently in a11y, or scope in technology that we're not seeing
   as being web driven, then yes we should revisit the scope

  APA Rechartering: Ready for CfC? [20]https://github.com/w3c/apa/blob/

  charter-2023/charter.html

     [20] https://github.com/w3c/apa/blob/charter-2023/charter.html


   janina: Question for the group: are we ready to go for a call
   for consensus (CfC) on our APA charter?
   … Now is the time to scope in anything that you feel is
   relevant. This charter will govern our work until some time in
   2025 (it's a 2-year charter).

   <Fredrik> FYI: I can't get in through the Zoom link. No idea
   what is going on. It looks as though I'm alone in the meeting.
   And yes, I'm using "our" link from the APA meeting page...

   janina: E.g. if we want to make overlay tech in scope, now is
   the time to ask for it. Same applies for all of our
   deliverables.

   janina: Questions/comments?

   Rendered HTML view of proposed charter: [21]https://
   raw.githack.com/w3c/apa/charter-2023/charter.html

     [21] https://raw.githack.com/w3c/apa/charter-2023/charter.html


   <janina> DRAFT RESOLUTION: APA avers we are ready for a Call
   for Consensus on our draft proposed Charter at [22]https://
   github.com/w3c/apa/blob/charter-2023/charter.html -- taken up
   [from janina]

     [22] https://github.com/w3c/apa/blob/charter-2023/charter.html

   <janina> +1

   <PaulG> +1

   <Roy> +1

   +1

   matatk: Propses a sentence at the start of the external orgs
   section to explain it's as-and-when, and we have worked with
   those in the past. Assume it's editorial though.

   janina: *confirms it's editorial*

   <Fazio> +1

   janina: We met with Web Payment Security Interest Group a
   couple of weeks back; was a productive meeting; intent to
   continue working with them.

   matatk: We should add Blissymbolics Communication International
   (as we are working with them).

   janina: Yes.

   +1 (to CfC on charter)

   janina: I asked Roy to look for refs to "Personalization" and
   update to "WAI-Adapt"

   Roy: Due to IP/process issues, we do need to retain some
   references to "Personalization Semantics Content Module" as
   it's a current draft.

   <Fredrik> ]q on CFC on teh Chartert, /1 on Zoom connection
   (from my side at least; can anyone see me in the meeting?).

   janina: Let's agree to update that draft before this gets to
   the AC, to avoid confusion.

   <Fredrik> Thanks Mat - working on it...

   RESOLUTION: APA avers we are ready for a Call for Consensus on
   our draft proposed Charter at [23]https://github.com/w3c/apa/

   blob/charter-2023/charter.html

     [23] https://github.com/w3c/apa/blob/charter-2023/charter.html


  New Charters Review [24]https://github.com/w3c/strategy/

  issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2
  2

     [24] https://github.com/w3c/strategy/issues?q=is:issue+is:open+label:"Horizontal+review+requested"

   Roy: No new charters this week.

  Explicit Review Requests [25]https://github.com/w3c/a11y-request/

  issues

     [25] https://github.com/w3c/a11y-request/issues


    Web Content Accessibility Guidelines (WCAG) 2.2

   <Roy> - issue: [26]w3c/a11y-request#52

     [26] https://github.com/w3c/a11y-request/issues/52


   <Roy> - due date: 2023-02-24

   matatk: I'll look at it.

    RDF Dataset Canonicalization

   <Roy> - issue: [27]w3c/a11y-request#51

     [27] https://github.com/w3c/a11y-request/issues/51


   <Roy> - tracked: [28]https://www.w3.org/WAI/APA/wiki/

   RDF_Dataset_Canonicalization

     [28] https://www.w3.org/WAI/APA/wiki/RDF_Dataset_Canonicalization


   <Roy> - spec: [29]https://www.w3.org/TR/rdf-canon/


     [29] https://www.w3.org/TR/rdf-canon/


   <Roy> [30]https://www.w3.org/WAI/APA/wiki/

   RDF_Dataset_Canonicalization

     [30] https://www.w3.org/WAI/APA/wiki/RDF_Dataset_Canonicalization


   Roy: We decided no need to review earlier (per the wiki); I
   propose to sign off.

   janina: Yes, please do.

   <Fredrik> No luck at all with Zoom today, have to look into
   that further down the line. I type and read in the IRC and
   that's very much okay for now.

   <Fredrik> matatk: Want a hand with the WCA?

  A11y Review Comment Tracker [31]https://w3c.github.io/

  horizontal-issue-tracker/?repo=w3c/a11y-review

     [31] https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review


   janina: How do we recognize that some of these items have
   timeouts and some don't? Seems they are two separate
   interfaces, so we should have two separate items for now at
   least.

   <Fredrik> "Otherwise" sounds fine. I'll post you tonight.

   rrsaigent, make minutes

  new on TR [32]http://www.w3.org/TR/tr-status-drafts.html


     [32] http://www.w3.org/TR/tr-status-drafts.html


   Roy: no new publications this week.

  CSS Update (Paul) [33]https://github.com/w3c/css-a11y/issues


     [33] https://github.com/w3c/css-a11y/issues


   PaulG: No new issues; will report on tonight's meeting next
   week.

  Actions Checkin (Specs) [34]https://www.w3.org/WAI/APA/track/actions/

  open

     [34] https://www.w3.org/WAI/APA/track/actions/open


   janina: Reminder: Tracker is going away soon. We will move to
   GitHub.
   … If you need help, please ask me or Matthew.
   … We are talking about making GitHub tracking easier in our
   planning calls, and think we can resolve most of the issues
   that we anticipate.
   … If you have any concerns, please let us know as soon as you
   can.

   <Fredrik> janina: Will there be any particulars for W3C/WAI on
   GitHub or will that be more or less standard issue githubbing
   going on?

   janina: Fredrik: we think it'll be fairly standard.
   … We _may_ be able to tweak things/tooling for some people; we
   are working on it, but nothing concrete yet.

  Task Force & Deliverables Updates

   <Fredrik> janina: Exciting, looking forward to further
   developments!

  Other Business

   matatk: We had a great initial meeting with the Accessibility
   for Childern Community Group and Adapt TF. Minutes:
   [35]https://www.w3.org/2023/01/30-adapt-minutes.html


     [35] https://www.w3.org/2023/01/30-adapt-minutes.html


   janina: They've been working on some very interesting things,
   including an ontology that we think will expand our use cases.
   … The AC CG will be working on contributing ot our Explainer
   document to highlight some curb cuts we can do in areas other
   than symbols.

   Fazio: I am looking into the research I mentioned a while back
   on AAC devices and voices (and effects on learning); have
   contact details. The work was done in the Bay area.

   janina: Thank you David. Rachael had some pointers on some
   similar-sounding work too, will forward those.

  be done

   janina: Thanks all!

Summary of resolutions

    1. [36]APA avers we are ready for a Call for Consensus on our
       draft proposed Charter at https://github.com/w3c/apa/blob/

       charter-2023/charter.html


    Minutes manually created (not a transcript), formatted by
    [37]scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

     [37] https://w3c.github.io/scribe2/scribedoc.html


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

Received on Wednesday, 1 February 2023 15:43:47 UTC