W3C

– DRAFT –
COGA Guidance Subgroup Call

30 Oct 2025

Attendees

Present
gareth, julierawe, lbeasley, Len, Lisa, who joined about halfway through the meeting
Regrets
-
Chair
julierawe
Scribe
julierawe

Meeting minutes

1st item in “What to do”: Align on Rain’s suggestion to include a few links in a call-out box instead of a longer wiki that will be harder to update/keep current over time.

3rd item in “What to do”: Align on adding a placeholder sentence and editor’s note about a soon-to-be-published study that makes clear there is a cognitive reason why we are overlapping with two WCAG 2.2 patterns about target size.

Exception[s]: Should the current exception remain in its current location or be moved higher up in the "What to do" section? And should we add another exception about security?

Gareth suggestions for the illustrations and captions.

Recap of Oct 23rd guidance subgroup meeting

We aligned on new title for pattern: https://docs.google.com/document/d/1uAVRkNIgd3XlUIGQ6Gq-ZOcnwsFvIM9UJ1dNyHq8NSQ/edit?pli=1&tab=t.ht1sood1wqs8

We also aligned on where to put the personalization info (at end of the "Key considerations" section)

Pattern we're reviewing: https://docs.google.com/document/d/1uAVRkNIgd3XlUIGQ6Gq-ZOcnwsFvIM9UJ1dNyHq8NSQ/edit?pli=1&tab=t.ht1sood1wqs8

Finish aligning on pattern about interactive elements (controls)

1st item in “What to do”: Align on Rain’s suggestion to include a few links in a call-out box instead of a longer wiki that will be harder to update/keep current over time.

We aligned on doing a short call-out box instead of a wiki. We also change the brand names to "Desktop, mobile, and other platforms."

Lisa adjusted the pattern name to avoid "Ensure"

3rd item in “What to do”: Align on adding a placeholder sentence and editor’s note about a soon-to-be-published study that makes clear there is a cognitive reason why we are overlapping with two WCAG 2.2 patterns about target size.

We aligned on mentioning the soon-to-be-published study. The editor's note will help us remember to update this before we publish the full V2 document.

Exception[s]: Should the current exception remain in its current location or be moved higher up in the "What to do" section? And should we add another exception about security?

We ran out of time and did not get to discuss the exception[s]/ We stopped reviewing after we finished the "Do" example's illustration and caption in #4 in "What to do."

Will finish the rest of the patten next week.

Thanks again to Gareth for drafting the illustrations!

Len joined about halfway through the meeting

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

No scribenick or scribe found. Guessed: julierawe

Maybe present: Exception[s]

All speakers: Exception[s]

Active on IRC: gareth, julierawe, Lisa