14:53:57 RRSAgent has joined #coga 14:54:02 logging to https://www.w3.org/2026/04/20-coga-irc 14:54:02 RRSAgent, make logs Public 14:54:03 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 14:54:08 date: 20 apr 2026 14:54:13 chair: julierawe 14:54:16 present+ 14:54:19 agernda? 14:54:21 agenda? 14:54:30 zakim, clear agenda 14:54:30 agenda cleared 14:55:46 agenda+ Update on COGA review of WCAG 3 14:56:32 agenda+ Should COGA update its user needs and functional needs? If so, how and where? 14:56:35 agenda? 14:57:59 Lisa has joined #coga 14:58:15 Lisa has joined #coga 14:58:27 regrets+ Lisa, EA, Eric 14:59:37 present+ 15:00:35 agenda+ Reminder about this week's subgroup calls 15:00:45 agenda+ Reminder to sign up to scribe, thank you! 15:05:02 Becca_Monteleone has joined #coga 15:06:19 johnkirkwood has joined #COGA 15:06:26 agenda? 15:06:29 present_ 15:06:33 present+ 15:06:36 present+ kirkwood 15:06:38 zakim, take up item 4 15:06:38 agendum 4 -- Reminder to sign up to scribe, thank you! -- taken up [from julierawe] 15:06:39 scribe: Becca_Monteleone 15:06:47 LenB has joined #coga 15:06:47 Jennifer has joined #coga 15:06:53 present+ 15:07:12 Link to our scribe list: https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit?tab=t.8zemqdwbcwtr 15:07:44 zakim, take up item 3 15:07:44 agendum 3 -- Reminder about this week's subgroup calls -- taken up [from julierawe] 15:08:15 Q+ 15:08:18 Julierawe: research subgroup meeting tomorrow at usual time. Usual thursday COGA review of WCAG 3 call 15:08:21 ack Lisa 15:08:49 Lisa: Research subgroup has now been moved to Tuesdays at 9 ET (used to be Thursday). Reminder to attend new time 15:09:09 W3C calendar link for tomorrow's research call at 9am Boston time: https://www.w3.org/events/meetings/3263a635-3a48-4d90-944c-e0bbc9f8f47a/20260421T090000/ 15:09:21 Jan has joined #coga 15:09:31 Julierawe: Thursday call also started at 9 ET 15:09:31 present+ 15:09:49 zakim, take up item 1 15:09:49 agendum 1 -- Update on COGA review of WCAG 3 -- taken up [from julierawe] 15:11:04 julierawe: COGA working on process for how to review WCAG 3. Streamlining voting process to vote directly into Google doc. 15:12:07 julierawe: will send out github issues to get asynchronous feedback, but will meet as Thursday group to make sure wording is agreed upon before doing that. 15:12:26 julierawe: wording will be finalized before voting 15:12:43 Q+ 15:12:50 ack Lisa 15:14:29 Lisa: the main purpose of initial send out will be to gather initial feedback and then Thursday group will reach consensus on wording and then will circulate for final approval 15:14:59 tiffanyburtin has joined #coga 15:15:19 Present+ 15:15:34 julierawe: example with general issues that Thursday group aligned on this week 15:16:02 Action item: COGA task force to vote on the general issues that the Thursday group aligned on last week: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?tab=t.xhbqn69zszr5#heading=h.u8djtsijtiud 15:16:27 Please submit your vote for each general issue by adding +1, -1, 0 in the google doc 15:18:11 Lisa: unless there are serious objections, consensus on these issues close today 15:19:16 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2026Apr/0013.html 15:20:25 Lisa: plan to submit issues to AG tomorrow morning so vote on Google doc by end of day Monday April 20 15:20:52 Updated action item: Vote by the end of today (April 20) 15:21:53 Issue G1: Please adjust 3.1.1 - the definitions of core and 15:21:53 supplemental, so WCAG is more equitable. 15:21:53 15:21:53 - 15:21:54 Issue G2: Assertions should be core or supplemental. 15:21:54 15:21:54 - 15:21:55 Issue G3: Assertions are too long and hard to follow. Please replace 15:21:55 the text of how to write an assertion, with a link. 15:21:55 15:22:04 To vote, go to this tab in the google doc and enter your vote for the three issues: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?tab=t.xhbqn69zszr5#heading=h.u8djtsijtiud 15:23:19 julierawe: John and julie have done initial review of interactive components section. Draft issues sent out on Friday for first 4 subsections, will send update with a few more issues today 15:23:29 julierawe: to be discussed on Thursday 15:24:05 This Thursday we will have initial discussion of the "Interactive Components" section: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?tab=t.qrwl38yxhls4#heading=h.bol0fq7zyoei 15:24:12 zakim, next item 15:24:12 agendum 2 -- Should COGA update its user needs and functional needs? If so, how and where? -- taken up [from julierawe] 15:25:13 julierawe: Len created a comprehensive list of COGA user needs in COGA publications 15:25:24 Len used AI to compile a list of COGA user needs: https://docs.google.com/document/d/1dIx9tEnG4xVPfUhacHpTeBrXVFJL6YYLK5si41oI4AY/edit?tab=t.0#heading=h.9myp61g5tbup 15:26:49 Lisa: we get user needs from different places - research modules, feedback from community groups, other research, open issues in Github and comments list 15:27:05 Lisa: sometimes AG identifies user need that we haven't identified 15:27:33 Lisa: we need to collect and consolidate them so that we have a more comprehensive list for the next version of Making Content Usable 15:28:20 Lisa: questions - where do we store them? is it grounded in the research? how do we assess if the user need is legitimate? 15:29:22 Lisa: need to document where these user needs come from and what they are based on (research, consensus, anecdote, etc.) 15:30:25 Len: in review of WCAG 3, noted that there had been a lot of good identification of user needs among the group without supporting research 15:32:11 Len: e.g., in review of text section of WCAG 3, we noticed that there was guidance around readable font - there seemed to be a gap in our identification of user needs, even though could point to some of the research that supports this 15:32:36 Len: some of the gaps may require an issue paper and others may not, but needs to be decided upon as a group 15:32:43 tiffanyburtin has joined #coga 15:33:48 julierawe: identifying two issues - we don't have a long list of user needs around text appearance AND we don't have the research module for this 15:34:01 tiffanyburtin has joined #coga 15:34:30 julierawe: what's a process that can help us capture what we need around user needs? 15:35:03 julierawe: how can we think about what else might be missing? Someone suggested, for example, time blindness as a functional need 15:35:37 Lisa: could start with a google doc or spreadsheet. Start with Len and Jan's suggestions and then start a running list 15:36:45 Lisa: could start with Len's google doc and start different tabs for different sources: https://docs.google.com/document/d/1dIx9tEnG4xVPfUhacHpTeBrXVFJL6YYLK5si41oI4AY/edit?tab=t.0#heading=h.9myp61g5tbup 15:38:02 Lisa: be careful about noting where each user need is coming from so that we can refer back 15:38:03 LenB has joined #coga 15:39:16 LenBN: some of the gaps may require an issue paper and others may not, but needs to be decided upon as a group 15:40:27 Lisa: New tabs on doc to refer to location of each user need being identified. Draft table included. 15:41:18 julierawe: need to check that these user needs are actually excluded from COGA docs and not just worded differently or located elsewhere 15:42:35 https://github.com/w3c/coga/issues 15:44:13 COGA issues on github and comments list are places where people may suggest new user needs 15:45:39 Comments list: https://lists.w3.org/Archives/Public/public-coga-comments/ 15:46:43 Lisa: COGA community group has a google doc with an entire section on user needs as well 15:48:41 julierawe: need for separate tables for sources? 15:49:00 Lisa: may be easier to identify where it's from if tables are separate 15:50:50 present? 15:51:00 present+ tiffanyburtin 15:51:10 Lisa: suggest a separate tab for WCAG 3 review since we will need to break it up by section 15:51:37 present+ LenB 15:52:24 present+ Jennifer 15:53:52 LenB: having WCAG review separate may allow us to a) show AG our work and b) prioritize where we go 15:54:51 Julierawe: reminder to people who cannot attend WCAG 3 review meetings on Thursdays to please submit asynchronous feedback 15:55:23 julierawe: in need of more people to volunteer to review sections of WCAG 3 15:55:31 Q+ 15:55:39 ack Lisa 15:55:42 julierawe: please let julie know if there are barriers to participate 15:56:08 Lisa: suggesting that if reviewing alone feels daunting, working in pairs is possible 15:56:47 Lisa: sections vary in length, so shorter reviews are possible 15:57:35 Johnkirkwood: reviewing user need themes - one of the major themes that seems like it should appear here is Memory 15:57:56 User Need Themes: https://docs.google.com/document/d/1dIx9tEnG4xVPfUhacHpTeBrXVFJL6YYLK5si41oI4AY/edit?tab=t.0#heading=h.9myp61g5tbup 15:59:23 julierawe: interesting that AI tool did not flag Memory - view this AI summary as a work in progress 15:59:57 LenB: raises questions about how we should structure. Map on to WCAG 3? Take a different structure? 16:00:15 LenB: there are only 2 provisions in WCAG 3 that refer to memory 16:01:58 rrsagent, make minutes 16:02:00 I have made the request to generate https://www.w3.org/2026/04/20-coga-minutes.html julierawe