Minutes of APA call 2022-04-06

HTML format: https://www.w3.org/2022/04/06-apa-minutes.html. 
Text format: See below.

Best regards,
Gottfried 

    [1]W3C

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

                             - DRAFT -
     Accessible Platform Architectures Working Group Teleconference

06 April 2022

   [2]IRC log.

      [2] https://www.w3.org/2022/04/06-apa-irc

Attendees

   Present
          becky, Fazio, Fredrik, Gottfried, iali, janina,
          Jonny_James, Lionel_Wolberger_, Matthew_Atkinson,
          MichaelC, mike_beganyi, Roy

   Regrets
          -

   Chair
          Matthew

   Scribe
          Gottfried, me

Contents

    1. [3]Agenda Review & Announcements
    2. [4]New Charters Review https://github.com/w3c/strategy/
       issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+
       requested%22
    3. [5]A11y Review Comment Tracker https://w3c.github.io/
       horizontal-issue-tracker/?repo=w3c/a11y-review
    4. [6]new on TR http://www.w3.org/TR/tr-status-drafts.html
    5. [7]Dangling Spec Review Cleanup: https://www.w3.org/WAI/
       APA/wiki/Category:Spec_Review_Assigned
    6. [8]FAST and Maturity Model Deliverables Update
    7. [9]Task Force & Deliverables Updates
         1. [10]RQTF
         2. [11]Pronunciation
         3. [12]Coga
         4. [13]Personalization
    8. [14]Actions Checkin (Specs) https://www.w3.org/WAI/APA/
       track/actions/open
    9. [15]Summary of action items

Meeting minutes

   <becky> present?

   <Fredrik> Hello Becky!

  Agenda Review & Announcements

   Nothing special.

  New Charters Review [16]https://github.com/w3c/strategy/
  issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2
  2

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

   <MichaelC> [17]https://github.com/w3c/strategy/issues/325

     [17] https://github.com/w3c/strategy/issues/325

   <MichaelC> [18]https://w3c.github.io/charter-drafts/
   wasm-2022.html

     [18] https://w3c.github.io/charter-drafts/wasm-2022.html

   MichaelC: Web Assembly, recharter
   . No liaison to us. Too low-level.
   . Let it go.

   janina: How to handle formal objections. Came up in discussion:
   Why not review by membership?

   MichaelC: Membership does review as part of public review.

   janina: And approved by AC.

   MichaelC: AC is the latest opportunity. Better ealier.

   Fredrik: Is "membership" regarding W3C?

   MichaelC: Membership refers to W3C membership. Individuals
   otherwise.

  A11y Review Comment Tracker [19]https://w3c.github.io/
  horizontal-issue-tracker/?repo=w3c/a11y-review

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

   MichaelC: No activity this week.

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

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

   <MichaelC> [21]https://www.w3.org/WAI/APA/wiki/Region_Capture

     [21] https://www.w3.org/WAI/APA/wiki/Region_Capture

   <MichaelC> [22]https://www.w3.org/TR/mediacapture-region/

     [22] https://www.w3.org/TR/mediacapture-region/

   MichaelC: Region Capture defines a way to capture of content of
   another part of the same browser window.
   . I think it does not introduce any new a11y problems. No need
   to review.

   janina: Agree

   <MichaelC> [23]https://www.w3.org/WAI/APA/wiki/
   MiniApp_Addressing

     [23] https://www.w3.org/WAI/APA/wiki/MiniApp_Addressing

   <MichaelC> [24]https://www.w3.org/TR/miniapp-addressing/

     [24] https://www.w3.org/TR/miniapp-addressing/

   Roy: I can review this.

   MichaelC: A URI scheme specific to mini apps. Maybe no a11y
   concerns?

   Roy: I don't have any a11y concerns, but i can double-check.

   ACTION: Roy to review Mini App Addressing, [25]https://
   www.w3.org/TR/miniapp-addressing/

     [25] https://www.w3.org/TR/miniapp-addressing/

   <trackbot> Created ACTION-2322 - Review mini app addressing,
   [26]https://www.w3.org/tr/miniapp-addressing/ [on Ruoxi Ran -
   due 2022-04-13].

     [26] https://www.w3.org/tr/miniapp-addressing/

  Dangling Spec Review Cleanup: [27]https://www.w3.org/WAI/APA/wiki/
  Category:Spec_Review_Assigned

     [27] https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned

   MichaelC: Nothing new to bring up.

   Matthew_Atkinson: I need to contribute as well.

  FAST and Maturity Model Deliverables Update

   Matthew_Atkinson: Josh is not a W3C staff member anymore, and
   is on holiday this week.

   janina: Maturity model is still getting organized.

   janina: Next Wed after this hour we need to organize this. Let
   me know if you want to participate.

   janina: Separate mailing list of rtqf?

   Gottfried: My staff member is doing her doctoral thesis on this
   topic. Can she join?

   janina: Make her an IE.
   . But she can join as a guest first.

   <Matthew_Atkinson> [28]https://w3c.github.io/maturity-model/
   index.html

     [28] https://w3c.github.io/maturity-model/index.html

  Task Force & Deliverables Updates

    RQTF

   <Lionel_Wolberger_> Lionel gives the rrsagent/zakim gold star
   award to Matt.

   rsagent, make minutes

   janina: Resolution was to target publication by April 15.
   . We are still cleaning up, Shawn to review.
   . This will be an updated wd for wide review.
   . We got a lot of comments to address.

   janina: Updated wd on remote meetings. At a meeting people were
   actively updating a shared document.
   . However, collaborative editors have limited accessibility
   support.

   <Fazio> Here's the W3C Accessibility Maturity Model Github
   Page: [29]https://w3c.github.io/maturity-model/

     [29] https://w3c.github.io/maturity-model/

   janina: We should include this as an editor's note in the doc.

    Pronunciation

   iali: Nothing new here.
   . Another topic is about the membership. Is ADP a W3C member?
   . ADP is a big payroll provider.

   <janina> [30]http://www.w3.org/Consortium/Member/List

     [30] http://www.w3.org/Consortium/Member/List

   janina: If a person is donating their own time instead of ADP
   time, this could be a case for IE.

   <Roy> [31]https://www.w3.org/groups/wg/apa/instructions

     [31] https://www.w3.org/groups/wg/apa/instructions

   janina: The person needs to fill out this form.

   iali: I need to follow up with the person.

    Coga

   dsinger: Nothing new. Working on How to make content usable for
   UI.

   Matthew_Atkinson: Update the UI or the content of the doc?

   Fazio: Need to bring this up to the team.

   Matthew_Atkinson: Easier to read is great.

    Personalization

   <Roy> Cognitive Accessibility Guidance list: [32]https://
   www.w3.org/WAI/WCAG2/
   supplemental/#cognitiveaccessibilityguidance

     [32]
https://www.w3.org/WAI/WCAG2/supplemental/#cognitiveaccessibilityguidance

   Lionel_Wolberger_: Focused on getting a name. Meeting with WAI
   coordination group.
   . Pushed back on i18n.
   . Want to write something on symbols.
   . Waiting for Janina to move this on.

   janina: It is on the agenda.

   Lionel_Wolberger_: Specification allows to specify a
   personalized symbol via a Bliss symbol id.
   . This Bliss id can be reused to specify any symbol.
   . Consulting with AAC experts: Only markup short sentences, not
   complete books or chapters.

   <Matthew_Atkinson> For background, this is the specific issue:
   [33]https://github.com/w3c/personalization-semantics/issues/144

     [33] https://github.com/w3c/personalization-semantics/issues/144

   Lionel_Wolberger_: If these persons have long texts to read,
   they would watch a video, not reading a long text with symbols.
   . We spoke with AAC experts, involved with AAC daily practice.

   Fazio: We should really involve AAC users. Nothing about us
   without us.
   . I have a contact who has a Masters.
   . We can send out a request to a cerebral palsy org or similar.

   janina: Can you do this ahead of CR? But we should not hold up
   this spec.

   janina: Let's do this in CR.
   . It is a philosophical disagreement.

   Lionel_Wolberger_: I like David's suggestion, and as chair of
   this tf want to follow up on that.

   janina: We have this expertise in Coga, right?

   Fazio: I will check next meeting.

   Matthew_Atkinson: We appreciate the suggestion to involve real
   AAC users.
   . It probably has to be done during CR.

   janina: We had Coga meetings on this spec.

   Lionel_Wolberger_: I would like to contact David's contact
   directly on this question.

   Matthew_Atkinson: We should bring this up in coga. Good to
   improve the process from now on.

   <Lionel_Wolberger_> Lionel sends regrets, has to leave early,
   and quietly walks out the virtual exit door.

   <Roy> [34]https://lists.w3.org/Archives/Public/
   public-wai-announce/2022JanMar/0005.html

     [34]
https://lists.w3.org/Archives/Public/public-wai-announce/2022JanMar/0005.htm
l

   Roy: Post on "Cognitive Accessibility Design Patterns - New
   User Interface"
   . I can give some information on personalization issue 144. Can
   talk to Philipp

   janina: That is important for the coordination call. Thank you.

   <becky> [35]https://github.com/w3c/virtual-keyboard/issues/15

     [35] https://github.com/w3c/virtual-keyboard/issues/15

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

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

   <becky> [37]https://github.com/w3c/virtual-keyboard/issues/15

     [37] https://github.com/w3c/virtual-keyboard/issues/15

   becky: Confusion of whether the virtual keyboard is overlaying
   page content.
   . In this case, it might be difficult to get behind the virtual
   keyboard to read the content.
   . I discussed, but the response was not satisfactory. They said
   that this can happen with other elements (e.g. drop-down) as
   well.
   . I argued that the difference is that you can move the focus
   off a drop-down, but not for the virtual keyboard.

   Matthew_Atkinson: This seems to violate WCAG.
   . Focusable stuff behind the keyboard is not okay. This is
   covered in another spec.
   . We should respond to this.

   janina: They are building in a WCAG failure.
   . We should phrase this as an APA comment on the spec, and make
   a consensus call.
   . We need to catch this.
   . Becky, can you draft a message?

   Matthew_Atkinson: We should park the other action items until
   next week.

   <Roy> [38]https://www.w3.org/WAI/APA/track/actions/2317

     [38] https://www.w3.org/WAI/APA/track/actions/2317

   action-2317?

   <trackbot> [39]action-2317: Janina Sajka to Review miniapps --
   due 2022-02-02 -- OPEN

     [39] https://www.w3.org/WAI/APA/track/actions/2317

   <Roy> [40]https://github.com/w3c/miniapp-packaging/pull/53/
   files

     [40] https://github.com/w3c/miniapp-packaging/pull/53/files

   Roy: Janina should not only look at the normative stuff,
   because they have changed some sections.
   . Please review the version on github.

   Matthew_Atkinson: Meeting adjourned

Summary of action items

    1. [41]Roy to review Mini App Addressing, https://www.w3.org/
       TR/miniapp-addressing/


    Minutes manually created (not a transcript), formatted by
    [42]scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).

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

Diagnostics

   Succeeded: s/when/if

   Succeeded: s/at this hour/after this hour

   Succeeded: s/payment/payroll

   Succeeded: s/and explain the situation of going into CR without
   having resolved this issue.//

   Maybe present: dsinger

Received on Wednesday, 6 April 2022 15:01:08 UTC