COGA review of WCAG 3: Action items and summary from April 9th

Hi, folks, here are the notes I put in the meetings section of our review
doc
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uggxirp4slpc#heading=h.l2oa4im5i0wj>
.April 9th, 2026Members present: Julie, Lisa, Eric, John, Jennifer
Action items

   -

   Lisa to draft new issue saying that “Errors indicated in multiple ways”
   needs to be core, not supplemental and to clarify that, when possible,
   icons and colors should both be used, not choosing just one in addition to
   text.
   -

   Lisa to draft new issue to change “Error suggestions provided” from
   supplemental to core. We also discussed adding an exception if that would
   help make this core, such as “Except when it is not possible to provide a
   suggestion on how to correct the error.”
   -

   Lisa to consider drafting a possible new issue: Eric suggested adding a
   new github issue about error messages that appear too soon, such as after a
   person enters 1 digit and gets error messages right away saying need to
   submit more digits.
   -

   Group to come up with process for determining when to submit a GitHub
   issue about missing user needs.

Summary/Minutes

Scheduling

   -

   Text and Wording: Julie sent Len and Jan an email asking how soon they
   can send pre-read to see if we’ll be ready to discuss April 16
   -

   Interactive Components: Julie and John are aiming to send pre-read on
   April 16 so the group has time to review and discuss at April 23 meeting
   -

   Process and Task Completion: Lisa is not sure how soon she can get this
   ready.
   -

   Animation: Eric’s draft github issues are ready for final review


Process

   -

   Lisa to discuss voting process at Monday’s task force meeting—how many
   votes needed to ensure the group is ready to submit GitHub issues
   -

   Lisa adding review deadlines at top of the scheduling tab
   <https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uggxirp4slpc>



Error handling

Issue 1: Clear language needed in error notifications
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.g9rkpmb69vcd>

   -

   John suggested error messages should also include the consequence if you
   don’t fix the error. Lisa doesn’t want to do that—a lot more reading and
   also sound negative.
   -

   We added pass/fail examples.

Issue 2: Errors associated: Three recommendations to improve cognitive
understanding
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.rf2uhorpkp9o>

   -

   Pass/fail examples added.
   -

   Lisa to consider drafting a possible new issue: Eric suggested adding a
   new github issue about error messages that appear too soon, such as after a
   person enters 1 digit and gets error messages right away saying need to
   submit more digits.
   -

   John noted a low-vision group at W3C had written up some issues about
   proximity of error messages. Eric is looking for a link to this work.
   -

   Lisa to draft new issue: Realized part of the github issue is addressed
   in a different provision. Lisa to create new issue saying that “Errors
   indicated in multiple ways” needs to be core, not supplemental

Issue 3: Two big concerns about “Error messages collocated”
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.pqp8dn50v0p6>

   -

   Discussed WCAG’s confusing definition of “visually collocated”
   -

   Also worked on clarifying the problem with the second half of the
   sentence, which allows a change of focus to something that is far from the
   source of the error, but users might not notice the change in focus.

Issue 4: Missing user needs from Correct errors 2.5.1 Users know about and
can correct errors
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.q2zqgonop0ra>
(Not ready yet for review)

   -

   Julie suggested combining Issue 4 and Issue 7 so we only have one GitHub
   issue about the user needs that are missing in “Error Handling.” Group
   discussed and decided to keep separate.
   -

   Clarified why “Going back supported” is too narrowly worded to capture
   errors that are not part of a multi-step process.


Issue 5: Concerns about the exception in Errors preventable
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.11xjr7wmhvmo>

   -

   Changed the description and GitHub issue name to make clearer what our
   concern is about this provision

Issue 6: Assertions in Errors preventable - why are these not requirements?
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.cfprw5own7fq>

   -

   Looks good—very important to ask this question.


Issue 7: Missing user needs from Correct errors 2.5.2 Prevent errors.
<https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.5gxd4veirbbq#heading=h.xii5nq7gavul>(Not
ready yet for review)

   -

   The group discussed needing a process for keeping track of user needs
   that may be missing and for determining when they are actually missing from
   WCAG 3 rather than possibly being covered in another section.
   -

   We’ll discuss with larger group, including Jan and Len, to come up with
   process for submitting github issues about missing user needs.


Jennifer suggestions

   -

   Lisa to draft new issue: Change “Error suggestions provided” from
   supplemental to core.
   -

      We also discussed adding an exception if that would help make this
      core, such as “Except when it is not possible to provide a suggestion on
      how to correct the error.”

General issues

   -

   Lisa will schedule a meeting to discuss the general issues tab


-- 
[image: understood.logo] <https://www.understood.org/>



[image: ThroughMyEyesimage]   *Julie Rawe*
*Director, Content Strategy & Accessibility*
jrawe@understood.org
www.understood.org


[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/en/donate>

------------------------------


Step into the world of students with
ADHD, dyslexia, and dyscalculia.
See differently. Act differently.
<https://www.understood.org/en/through-my-eyes>

Received on Thursday, 9 April 2026 16:20:47 UTC