[minutes] WAI-CC 13 Nov 2023

online: https://www.w3.org/2023/11/13-waicc-minutes.html

text:

    [1]W3C

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

                              – DRAFT –
                   WAI Coordination Call Teleconference

13 November 2023

    [2]IRC log.

       [2] https://www.w3.org/2023/11/13-waicc-irc

Attendees

    Present
           Daniel, George, James, janina, Jem, kevin,
           Lionel_Wolberger_, maryjom, matatk, Shawn,
           KrisAnne(part)

    Regrets
           -

    Chair
           Shawn

    Scribe
           matatk

Contents

     1. [3]Group updates
     2. [4]Managing issues and public comments

Meeting minutes

   Group updates

    Lionel_Wolberger_: Working on symbols module, and the
    well-known URLs for accessibility.

    janina: Happy to have matatk back.

    matatk: Very happy to be back!

    janina: I've been asked by a11yNYC to present on APA's work in
    W3C WAI. Working on slides. Will present all our work and leave
    time for questions. Wonderful recruiting opportunity.
    … Would appreciate help socializing it.

    shawn: Is the focus on APA or broader?

    janina: APA

    shawn: Skimming minutes, I saw a comment that APA would not
    want Maturity Model to move out into a broader group?

    janina: Think there's some misunderstanding about that, maybe
    best to check in directly first, and then maybe take up on this
    call.

    janina: Now I have a co-chair back, want to catch up between us
    first.

    shawn: ACK; please add to follow-up list, kevin

    janina: This has bounced around in Maturity Model and Sherri
    has been in Equity conversations; need to follow up on those.
    Is Equity working as part of AG?

    shawn: It moved out, broader.

    maryjom: WCAG2ICT: still finishing up addressing public
    comments from FPWD.
    … Trying to follow up with folks assigned to draft responses.
    … We're also working to get WCAG 2.2 changes incorporated into
    the next draft, too. Expecting that to come out in March.
    … Next draft for AG review soon (expecting within a week).
    Trying to get the first in before the end of year holidays.

    Jem: co-chairing ARIA APG group with Matt King. Expecting
    another publication before the end of the year.

    <janina> Publish? Updated WD? Final Note Version? Which?

    dmontalvo: Placeholder publication for tomorrow likely delayed.

    <Jem> [5]https://www.w3.org/WAI/ARIA/apg/

       [5] https://www.w3.org/WAI/ARIA/apg/

    janina: There was some concern in APA about how mature the
    patterns are.

    Jem: Would like to hear feedback from the group about what
    improvements we can make.

    janina: Matt King asked for us to meet up on this at TPAC; I
    said we'd have to follow up in due course as we have a lot
    changing at the moment.

    jamesn: Please can I be invited?

    dmontalvo: Please can I be invited?

    <shawn> [ Shawn also interested in participating that meeting.
    ]

    janina: This came as a result of looking at proposed charters,
    including EOs, and a discussion on making sure we point to
    mature content.

    Jem: We already have a note that states if a pattern is in the
    development/testing stage.

    janina: That helps.

    jamesn: There will always be some things in APG that are not
    mature, because some of the patterns are used by browser
    vendors to work out the provision of support for those
    patterns.

    janina: I'll carry that back.

    shawn: This seems like a communications issue. On the one hand,
    some people think they're patterns that can be used, but on the
    other, some are examples of things that could be used in
    future.

    jamesn: This is the purpose of ARIA-AT - to put into the APG
    the real test results of support, but that's not complete yet.
    We have started this, and it needs more effort.
    … It takes a long time to work with each of the ATs and figure
    out what and how they think they should be/are supporting
    things.

    <Jem> [6]https://www.w3.org/WAI/ARIA/apg/patterns/button/
    examples/button/

       [6] https://www.w3.org/WAI/ARIA/apg/patterns/button/examples/button/

    Jem: One example covers how different ATs support the button
    pattern.

    Jem: This shows the data.
    … One level is how we explain to users the state of a
    particular pattern, and another is communicating the test
    results.

    shawn: [cites the note about code not being intended for
    production environments that is present in the APG]

    <dmontalvo> Can we get a pointer to that Gh comment?

    janina: Our hope is to give pointers to wider WAI work, but we
    got tripped up on exactly what we should link to.

    <Jem> I think "reliable" is the moving target considering the
    change of technology everyday.

    shawn: Where is the comment? APA repo? Do we need a WAICC repo
    [as suggested just by kevin also]?

    kevin: Yes, I think this is demonstrating the need for this.

    shawn: We're tracking two things. The second thing is APG
    communication.

    Jem: is the scope just APG, or ARIA spec too?

    janina: APG

    <shawn> WAI-CC to track 1. Maturity Model going broader than
    APA? 2. For APG, better communicate APG purpose, status of
    patterns, etc.

    janina: Really good feedback from you all about these comments.
    We are just concerned about ensuring communication is clear.

    George: We're working on the user experience guide for
    accessibility metadata in the Publishing CG.

    KrisAnne: Working on EO charter. Had uptick of people asking to
    participate who're not W3C members.
    … Been kicking around the idea of running a CG.

    shawn: Decided to get another EOWG charter extension, for more
    time to see what resources [participant & Chair] for EOWG.

    shawn: One idea floated was to not recharter EO due to lack of
    participation.
    … The chairs and some people in the group wanted to continue,
    so we're doing another 6 months. This is opportunity for W3C
    members to contribute to EOWG work, and demonstrate the support
    for getting the work done.
    … This is kind of a big deal.

    shawn: If you and your organization want EO to continue,
    support the work.

    jamesn: What's the downside of making it a CG? There aren't any
    IPR issues?

    KrisAnne: In the past it's been expressed that the amount of
    work that EOWG does is worthy of being a WG. But when you're
    not a WG, companies may not give people the time to do the
    needed work. Creating and publishing resources involves a
    significant amount of effort.
    … We want to ensure that people are given the time to do it.

    James: Sounds like participants not currently having time for
    WG.

    KrisAnne: Some people who have been given the time, but have
    too much other work to do it.
    … There is fallout from organizations shrinking.
    … On paper, we're a large WG. We asked how we can get people
    more involved, and we often get the answer that people are as
    involved as they can get. If you have someone in your
    organization who is interested in training, education,
    outreach, we could use help.
    … That was a reason we thought about the CG, as we're not bound
    by membership. Though may give more weight to the resources we
    publish - if they come from a WG.

    <janina> I think EO generates publications we want the WAI
    imprimatur which wouldn't be available from a CG

    shawn: We're still discussing and appreciate your perspectives.

    Lionel: There was a successful pattern in Verifiable
    Credentials with CG(s) and then particular work being
    "promoted" to the WG.

    shawn: That's the same thing we're doing with ACT Rules. EOWG
    plans to experiment with options.

   Managing issues and public comments

    shawn: Thanks for good discussion. Will defer this agenda item.
    see what Mary Jo shared via email. Especially for new-to-W3C
    participants [7]https://github.com/w3c/wcag2ict/wiki/
    Process-for-addressing-public-comments

       [7] https://github.com/w3c/wcag2ict/wiki/Process-for-addressing-public-comments


     Minutes manually created (not a transcript), formatted by
     [8]scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

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

Received on Monday, 13 November 2023 18:04:25 UTC