Re: Agenda: APA WEEKLY Teleconference; Wednesday 24 August at 1400Z

Hi all,

Minutes from this week's call can be found at https://www.w3.org/2022/08/24-apa-minutes.html and are repeated below for convenience of searching.

Thanks to Irfan for scribing.

Best regards,


Matthew

                             – DRAFT –
     Accessible Platform Architectures Working Group Teleconference

24 August 2022

   [2]IRC log.

      [2] https://www.w3.org/2022/08/24-apa-irc


Attendees

   Present
          alii, Fredrik, janina, Joshue108, Matthew_Atkinson,
          mike_beganyi, Roy

   Regrets
          -

   Chair
          Matthew_Atkinson

   Scribe
          alii, Irfan Ali

Contents

    1. [3]Agenda Review & Announcements
         1. [4]CSS CfC
         2. [5]WCAG CfC
         3. [6]Adapt CR
    2. [7]New Charters Review https://github.com/w3c/strategy/

       issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+
       requested%22
    3. [8]A11y Review Comment Tracker https://w3c.github.io/

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

    5. [10]Dangling Spec Review Cleanup: https://www.w3.org/WAI/

       APA/wiki/Category:Spec_Review_Assigned
    6. [11]APA Review of Draft AGWG Charter https://
       raw.githack.com/w3c/wcag/charter-2022/charter.html
    7. [12]TPAC22 https://www.w3.org/WAI/APA/wiki/Meetings/

       TPAC_2022
    8. [13]APA Review of Draft AGWG Charter https://
       raw.githack.com/w3c/wcag/charter-2022/charter.html
    9. [14]TPAC22 https://www.w3.org/WAI/APA/wiki/Meetings/

       TPAC_2022
   10. [15]Summary of resolutions

Meeting minutes

  Agenda Review & Announcements

    CSS CfC

   Matthew_Atkinson: call for consensus in progress

   <Matthew_Atkinson> [16]https://lists.w3.org/Archives/Public/

   public-apa-admin/2022Aug/0021.html

     [16] https://lists.w3.org/Archives/Public/public-apa-admin/2022Aug/0021.html


   Matthew_Atkinson: it is only open until end of the day. please
   vote

    WCAG CfC

   <Matthew_Atkinson> [17]https://lists.w3.org/Archives/Public/

   public-apa-admin/2022Aug/0023.html

     [17] https://lists.w3.org/Archives/Public/public-apa-admin/2022Aug/0023.html


   Matthew_Atkinson: we have 2.2 CI horizontal review, CFC. this
   one will also open until end of the day.

   janina: I will take a second look on the content.

   janina: we may need to re-run for the CFC if we need to make
   any content change

    Adapt CR

   Matthew_Atkinson: Janina can go in the details about the
   process.

   Matthew_Atkinson: we have a conformance section in specs of dos
   and donts. we have a CFC for the people to adapt the changes.

   janina: this requires documents consensus. I expect that pull
   requests will be merged soon so that we can send a CFC

   <Roy> [18]https://w3c.github.io/adapt/content/#conformance


     [18] https://w3c.github.io/adapt/content/#conformance


   Roy: I have reviewed two pull requests and merged it already.

   Roy: janina can use the conformance section to review

   Roy: there is a link in the implementation report. I will fix
   all of the issues and merge it into the pull request

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

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

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

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

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

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


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


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


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

  Category:Spec_Review_Assigned

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


  APA Review of Draft AGWG Charter [23]https://raw.githack.com/w3c/wcag/

  charter-2022/charter.html

     [23] https://raw.githack.com/w3c/wcag/charter-2022/charter.html


   Matthew_Atkinson: we need to address this. we mentioned about
   it last week. we want to get feedback form the people

   Matthew_Atkinson: this is about formatting on all charters

   Matthew_Atkinson: thats going to be addressed separately.
   should concentrate if we have any question on the content. if
   anyone has any questions/concerns on this proposed charter,
   please let us know

   janina: we should give a chance people to read it

   janina: there was an assumption built to the charter. it
   assumes that 2.2 went to the CR which becomes the w3
   recommendations

   janina: it talks about working on 3.0 which seems it all about.
   we are only 2 weeks away from TPAC and we still do not have CR
   ready.

   janina: publishing 2.2 in CR doesn't mean we are done.

   janina: I think we should split the advisory group into two
   part. one can work on 2.2 and other can focus on 3.0

   Matthew_Atkinson: wonder if we are practicing section 4 success
   criteria

   Matthew_Atkinson: this section doesn't make any sense in
   reality

   janina: APA agrees that WCAG is important and 2.2 and 3.0
   should be allowed to continue unimpeded

   we want to see 2.2. and 3.0 move forward

   DRAFT RESOLUTION: APA confirms it considers both WCAG 2.2 and
   WCAG 3 important for accessibility and wishes to say each of
   them proceed unimpeded.

   <janina> +1

   +1

   <mike_beganyi> +1

   <Matthew_Atkinson> +1

   <Fredrik> +1

   janina: W3 policy requires disclosure on intellectual properly
   and that has to happen during CR.

   janina: advisory committee takes 30 days to approve the
   proposed recommendations.

   Matthew_Atkinson: do you think there ar any other option to
   extended existing charter or rewrite it.

   janina: there should be two groups

   janina: they could take the charter from 2018 and change the
   date.

   Matthew_Atkinson: extend the current charter or split the
   group?

   janina: lets assume one year extension. at that point if it
   still has not happened, what are we going to do?

   Matthew_Atkinson: another option (arising from group
   discussion) is not going for 2.2

  TPAC22 [24]https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022


     [24] https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022


  APA Review of Draft AGWG Charter [25]https://raw.githack.com/w3c/wcag/

  charter-2022/charter.html

     [25] https://raw.githack.com/w3c/wcag/charter-2022/charter.html


   <janina> +1 to current draft charter not meaningful

   Matthew_Atkinson: who agrees that current charter is not
   meaningful?

   +1

   <janina> +1

   <mike_beganyi> +1

   <Fredrik> +1

   <Matthew_Atkinson> +1

   Matthew_Atkinson: where do you think we should go with this?

   <janina> DRAFT RESOLUTION: Current draft charter on github is
   not meaningful path forward

   <janina> +1

   +1

   <Matthew_Atkinson> +1

   <mike_beganyi> +1

   <Fredrik> +1

   RESOLUTION: Current draft charter on github is not meaningful
   path forward

   RESOLUTION: APA confirms it considers both WCAG 2.2 and WCAG 3
   important for accessibility and wishes to say each of them
   proceed unimpeded.

  TPAC22 [26]https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022


     [26] https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022


   Matthew_Atkinson: we have scheduled 7 meetings and expecting
   more to follow

   <Matthew_Atkinson> [27]https://www.w3.org/2022/09/TPAC/

   venue.html

     [27] https://www.w3.org/2022/09/TPAC/venue.html


Summary of resolutions

    1. [28]Current draft charter on github is not meaningful path
       forward
    2. [29]APA confirms it considers both WCAG 2.2 and WCAG 3
       important for accessibility and wishes to say each of them
       proceed unimpeded.


    Minutes manually created (not a transcript), formatted by
    [30]scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

     [30] 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 Friday, 26 August 2022 10:39:06 UTC