WAI-CC minutes 10 February 2025 and summary notes for you

agenda:

  * WAI announcements process changes coming (easier for you!)
      o question 1. Google docs and sheets vs. GitHub ?
      o question 2. Any input on announcement format, tone, approach, etc. at this point ?
  * Guidance for using Google Docs with screen reader

some highlights:

  * Google docs and sheets fairly accessible on Windows; not at all on Mac or Linux
  * Announcements approach — WAI Staff (primarily Tamsin, with Shawn's support) will be more active in providing editorial review of abstracts, introductions, and STOD; and will use that to lead announcements drafting
  * Announcements input — Open invitation to share any ideas for improving announcements format, tone, approach; can send to WAI staff at <wai@w3.org> or this public list <public-wai-cc@w3.org>

minutes online: https://www.w3.org/2025/02/10-waicc-minutes.html

minutes text version below:

    [1]W3C

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

                              – DRAFT –
                   WAI Coordination Call Teleconference

10 February 2025

    [2]IRC log.

       [2] https://www.w3.org/2025/02/10-waicc-irc

Attendees

    Present
           Daniel, janina, Kevin, maryjom, Shawn

    Regrets
           George, Lisa

    Chair
           Shawn

    Scribe
           maryjom

Contents

     1. [3]scribe
     2. [4]WAI announcements process changes coming (easier for
        you!)
     3. [5][sub-topic] question 1. Google docs and sheets vs.
        GitHub ?
     4. [6][sub-topic] question 1. Any input on format, tone,
        approach, etc. at this point ?
     5. [7]Guidance for using Google Docs with screen reader
     6. [8]Any follow-up needed from last meeting? (Kevin sent
        email to Matthew) https://www.w3.org/WAI/cc/wiki/
        WAI-CC_agendas#Agenda_from_last_meeting_(27_Jan) shawn]
     7. [9]anything else?

Meeting minutes

   scribe

   WAI announcements process changes coming (easier for you!)

    shawn: At one time, Shawn did all the announcements. Then other
    staff, chairs, and facilitators contributed more to initial
    drafts.. We are working on announcements templates.
    … and the announcement process. At one time Shawn and EOWG
    reviewed abstacts and introductiosn for all WAI publications,
    then was not able to fit it in workload.. Tamsin is leading
    reviews of abstracts, introductions and SOTD of documents.
    … unless anyone objects, Tamsin will take over drafting the
    announcements.

    janina: Want to be able to carry forward the institutional
    knowledge we have on making announcements.

    shawn: Agree, we've been having different people work in GitHub
    or in Google docs to draft announcements.
    … one thing we learned for trying different options is that in
    GitHub, haiving each type of announcement in a separate file
    was not best. So will do that differently..

   [sub-topic] question 1. Google docs and sheets vs. GitHub ?

    shawn: Want input on this topic and screen reader accessibility

    janina: Some will be happy with Google docs. Depends on the TF
    and how many screen reader users they have.
    … Are we settling into 2 different tools and how we decide on
    what tool to use.
    … most screen reader users export to Word and can then access
    it. But you lose the interactive aspect of editing.

    shawn: Will continue to develop draft templates in Google docs
    for now and will eventually have them ready in GitHub and the
    group can choose which they wish to use.

    janina: Sounds fine.

    shawn: If we had the list of publications in a Google sheet
    that you would only need to access occasionally, would that
    work?

    kevin: Would like to not have a Google spreadsheet, as it would
    be difficult to manage where things are in the process. Prefer
    GitHub

    Daniel: Agrees with Kevin.

   [sub-topic] question 1. Any input on format, tone, approach, etc. at
   this point ?

    shawn: Will come back to the group with specific, but wanted
    input on the format, tone, etc. If you have input, great to get
    now.

    janina: Don't have anything specific now.

   Guidance for using Google Docs with screen reader

    daniel: This depends on your operating system. On windows,
    google docs essentially works ok (with some difficulty). On Mac
    and Linux, it isn't working at all. Missing a lot of characters
    and content.
    … can write guidance for people, but only on Windows are these
    useful.
    … with the WCAG2ICT task force, if you use Google Drive and put
    the Word documents on there you can synch up with that drive
    and get access to the content.

    Janina: We don't want to force everyone onto Windows.

    daniel: That's the high level overview.

    Janina: would agree with that, and some have come up with
    keystrokes to get things to work but it's a burden for everyone
    to do.

    kevin: Wanted to raise this as there were concerns expressed.
    Plus there's other tools we use that we want to make sure are
    accessible.

    <shawn> [ also Shawn has direct contacts with accessibility
    folks at GitHub ]

    kevin: Leonie has inroads to GitHub and is getting issues fixed
    for screen reader users.

    janina: Should get ahead of this in both environments so we can
    document issues and know what works. Others outside of WAI are
    using Google docs, so it would be good to get things documented
    so they can get fixed.

   Any follow-up needed from last meeting? (Kevin sent email to Matthew)
   [10]https://www.w3.org/WAI/cc/wiki/
   WAI-CC_agendas#Agenda_from_last_meeting_(27_Jan) shawn]

      [10] https://www.w3.org/WAI/cc/wiki/WAI-CC_agendas#Agenda_from_last_meeting_(27_Jan)

    shawn: Last meeting there was a long agenda and not a lot of
    folks present.
    … wondering if there's updates to share.

    janina: Can follow-up via email.

   anything else?


     Minutes manually created (not a transcript), formatted by
     [11]scribe.perl version 242 (Fri Dec 20 18:32:17 2024 UTC).

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