COGA WCAG 3 Coordination Subgroup: Highlights + Minutes from February 13th

Hi, folks, thanks for your time today. Below are the highlights and minutes
from today's subgroup meeting.

*Highlights*

   - *COGA tracking doc for WCAG 3 pathways*
   <https://docs.google.com/spreadsheets/d/1VhXbUz8PZpRTMvHJq5ZXPwPNXwFNFQDyBi9SWbL6awk/edit?gid=0#gid=0>
      - Anyone in COGA can add to this tracking doc at any time.
      - Use this doc to raise concerns or share updates about WCAG 3
      subgroups.
      - Please bookmark. (Julie also added link to this tracking doc in the
      WCAG 3 section of COGA action items
      <https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit?tab=t.0>
      .)
   - *Trigger warnings*
      - *Action item:* Rashmi will email COGA's draft issue paper
      <https://docs.google.com/document/d/19RdKrd2aUJkZcm9FmIOvZ2jfn9JgYpFcqT5mubyQUAQ/edit?tab=t.0#heading=h.p1q1f5jvv2f>
      to the WCAG 3 group that is working on trigger warnings. (Julie
and Rashmi
      discussed this at the Github editors call earlier today.)
   - *Appropriate tone *
      - This draft requirement
      <https://www.w3.org/TR/wcag-3.0/#appropriate-tone> started out
in the Prevent
      Harm scratchpad
      <https://docs.google.com/document/d/1S9K4i0CAiTHCWXD0_LnpS90E2l9VC_Xs18UmOXhGzaw/edit?tab=t.0#heading=h.t3uqwwnk7ffi>,
      but the AG chairs moved it to Plain Language.
      - Julie is wondering if Plain Language is the best place for it.
      - Frankie and John K. provided insights on the origin of this
      requirement, which includes protecting against false urgency and other
      forms of deception.
      - *Action items: *
         - Julie will ask Gregg Vanderheiden for more insights about
         "Appropriate tone."
         - Julie will talk with Plain Language group about developing an
         assertion about having a style guide that covers tone.
         - Julie will talk with the other WCAG 3 subgroup leaders about
         possibly moving "Appropriate Tone" requirement to Safety and Deception.
      - *Global concern about all WCAG 3 paths*
      - Subgroup discussed low participation in different paths (very small
      number of people doing the drafting) and very ambitious timeline
to get all
      the drafts in.
      - Subgroup discussed concerns about needing time for COGA to review
      the drafts, which will be very hard given all the simultaneous
workstreams
      of drafting more WCAG 3 guidelines while also working on next version of
      Making Content Usable.
      - Frankie suggested that AG build in time for a review sprint where
      different paths review each other's work.
      - *Action item: *Julie will raise this concern and the idea of review
      sprints with Rachael.

*Minutes*

   - Apologies, but Zakim wasn't working properly so I had to copy and
   paste everything in IRC in order to generate minutes. I wish Zakim wasn't
   so hard to use.
   - https://www.w3.org/2025/02/13-coga-minutes.html


*Next WCAG 3 Coordination Subgroup Meeting*

   - Thursday, April 3rd, at 11am ET




-- 
[image: understood.logo] <https://www.understood.org/>   *Julie Rawe*
*Director, Content Strategy & Accessibility*
jrawe@understood.org
www.understood.org
she | her | hers

[image: facebook icon] <https://www.facebook.com/Understood/>  [image:
linkedin icon] <https://www.linkedin.com/company/understood/>  [image:
instagram icon] <https://www.instagram.com/understoodorg/?hl=en>  [image:
tiktok icon] <https://www.tiktok.com/@understood.org>   *Support us
<https://www.understood.org/donate>*