14:41:55 RRSAgent has joined #coga 14:41:59 logging to https://www.w3.org/2025/07/21-coga-irc 14:41:59 q? 14:41:59 RRSAgent, make logs Public 14:42:00 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 14:42:02 ack next 14:42:59 agenda+ subgroups resuture 14:43:08 agebda? 14:43:12 agenda? 14:46:14 agenda order is 1 8 2 4 5 7 8 3 14:46:21 close item 3 14:46:34 agenda order is 1 8 2 4 5 7 14:52:30 EA has joined #coga 14:55:10 Q? 14:56:52 agenda+ tpac 14:57:37 Gareth has joined #coga 15:01:23 Rain has joined #coga 15:02:06 Becca_Monteleone has joined #coga 15:02:06 julierawe has joined #coga 15:02:06 present+ 15:02:18 present+ 15:02:57 Charli has joined #coga 15:02:57 scribe+ Becca_Monteleone 15:02:57 present+ 15:03:05 present+ 15:03:12 scribe+ Becca_Monteleone , gareth 15:03:28 next item 15:04:51 Jan has joined #coga 15:04:53 Lisa: new tabs on COGA action item document, including agendas so that people can find info all in one place 15:05:15 Charu has joined #coga 15:05:18 Lisa: Orientation training, key links, instructions for using documents also included 15:05:36 q? 15:05:40 +1 15:05:44 +1 15:06:01 It seems helpful to have it all here 15:06:06 +present 15:06:07 Lisa: Are people happy with agendas included on this document? 15:06:24 +1 15:06:26 +present 15:06:26 next item 15:07:57 q+ about subgroups 15:07:58 Lisa: proposal for two subgroup tracks discussed last week: Guidance and Advice as subgroup track #1, Research as subgroup track #2 15:08:37 Lisa: both on Thursdays. Research at 9 am EST, Guidance at 11 am EST (for now) 15:08:41 kirkwood has joined #COGA 15:09:25 +preset+ 15:09:31 present+ 15:09:32 Lisa: Mondays would review what is covered in Thursday groups and calls for consensus 15:10:09 Charu present+ 15:11:22 Lisa: Are people comfortable with those two tracks? 15:11:37 +1 15:11:40 +1 15:11:45 ack next 15:11:50 +1 15:12:03 Charli: Would there be a 3rd group for Editorial as discussed last week? 15:12:42 q+ 15:12:48 ack next 15:12:54 Lisa: Editorial is usually with Research - but there may be a need for additional calls to be scheduled when certain projects are in process 15:13:08 LenB has joined #coga 15:13:16 present+ 15:13:23 Julierawe: There may be some editors focused on issue papers so they go to Research. Editors focused on Guidance would go to Guidance calls 15:14:12 Lisa: This would also help because some of the subgroups currently are very small, so this restructure would mean more people would be present 15:14:14 any objecttions 15:14:14 +1 15:14:18 +1 15:14:23 _1 15:14:24 +1 15:14:27 +1 15:14:38 ack next 15:14:59 next item 15:15:36 End of September 15:15:41 Lisa: Schedule for restructure in COGA action items document 15:15:57 *new structure for Making Content Usabel 15:16:27 Rain: Plan to have it coded in Github by end of September 15:17:22 Rain: will not include the final text, will use current text as placeholder text; plan to include the icon draft 15:22:02 Julierawe: would call for consensus for new patterns be before or after it goes into template? 15:22:21 Lisa: Suggests calls for consensus as they are completed 15:23:40 Lisa: will need to put them on the Monday agendas, but current deadline is for drafting only 15:27:22 q+ 15:29:54 ack next 15:30:35 julierawe: asking about process - draft a pattern, share with internationalization, incorporate internationalization feedback, then share with the wider group for consensus? 15:30:48 Lisa: Added process to document for clarity 15:31:50 q+ 15:32:12 julierawe: which subgroup would review? 15:32:50 Lisa: suggest keeping with Tuesday subgroup since they are already familiar with everything 15:33:37 julierawe: after the first 5 patterns, then eventually this is something guidance subgroup would be more involved in 15:35:18 ack next 15:38:18 present+ 15:40:11 Lisa: Splitting action items in document to clarify what is necessary for next draft vs. following draft(s) 15:41:21 Lisa: Objections or comments? 15:41:22 Q? 15:41:35 next item 15:42:57 Subscribe with this link: https://www.w3.org/users/16320/calendar/export/?secret=81dac90653cf90e5dd97560cc3de5fa2a97beacb 15:43:08 Lisa: on W3C calendar page, scroll to bottom of page, there is header labeled "Export Options" where you can subscribe with a link. 15:43:56 Lisa: In your personal calendar, you can then add this link and it will update it with your w3c events 15:44:14 Lisa: There is also an option to download as ics 15:45:22 Charli: Some of the monday and thursday meetings already populate in Outlook calendar 15:45:58 Lisa: Roy may be able to help with a walkthrough 15:46:25 Julierawe: on W3C website, if you go to the calendar, do all the meetings show up there? 15:46:52 next item 15:46:58 Julie will provide walkthrough of W3C calendar after today's meeting 15:49:39 +q 15:50:16 Lisa: at the beginning of each document, we want a comprehensive statement about who is included 15:50:27 q+ 15:50:59 Users with disabilities that impact cognitive accessibility include people with: 15:50:59 cognitive, developmental, intellectual, learning, and specific learning disabilities, 15:50:59 language and communication disorders, 15:50:59 neurodivergence, 15:51:00 traumatic brain injury, 15:51:00 mental health impairments, and 15:51:00 temporary impairments that affect cognitive function, such as extreme anxiety, illness and others. 15:51:23 Lisa: better to be redundant and lengthy than to not include certain groups in this statement 15:51:42 ack next 15:52:21 EA: do we need to include "people with" in that first line since we already call them users? 15:52:23 q+ 15:52:27 +1 15:52:36 i would want to include aging, or aging related cognitive decline? 15:52:41 julierawe: "those with" can sound othering 15:53:04 stil agree with EA 15:53:11 Alternate wording: "Disabilities that can impact cognitive accessibility include:" 15:53:27 agreed it doesn’t read correctly 15:53:28 Noting that in the age of AI, users are no longer necessarily "people" 15:53:38 +1 to julierawe's suggestion 15:53:40 Jan has joined #coga 15:54:00 q+ 15:54:04 +1 to Julie's suggestion 15:54:07 I like what Lisa just said: "Users who need cognitive accessibility include people with: 15:54:28 q- 15:55:08 q+ 15:55:13 possible wording: "Disabilities that may require cognitive and learning centered accessibility support:" 15:55:30 +1 15:55:40 +1 15:57:14 Should we consider rewording in a way to include some "such as" examples? Like "neurodivergence, such as autism" and "learning differences or specific learning disabilities, such as dyslexia and dyscalculia" 15:57:16 +q 15:57:21 q+ 15:58:38 Lisa: hesitant to add examples because they may be nested under several different bullet points. Maybe a sentence at the end? 15:58:51 +q 15:59:03 ack next 16:00:26 Becca_Monteleone: suggest striking "extreme" from qualifying anxiety 16:00:47 ack next 16:01:22 q+ 16:01:27 julierawe: "anxiety" seems to be the only specific in the list - so maybe there's a separate bulleted list with more specifics for someone scanning or searching the document 16:01:58 ack next 16:02:04 Lisa: Asking for comments in document 16:02:22 EA: impact vs. affect - commented onto docuemnt 16:03:07 EA: "affect" suggests on-going, more nuanced 16:03:16 ack next 16:03:55 Gareth: Suggest list should be in one place with a link to it so that we can easily cite it across documents 16:04:07 +1 to Gareth's comment about having one universal list 16:04:32 ack next 16:04:50 Have to drop 16:05:21 +1 to Charli's comment about all mental health impairments affecting cognitive function 16:05:32 Charli: may not need to qualify "mental health impairments" with "that affect cognitive function" 16:06:15 Charli: +1 to having a laundry list of specific examples so people know they are included 16:06:36 Need to drop - sorry! 16:07:55 RRSAgent, publish minutes 16:07:56 I have made the request to generate https://www.w3.org/2025/07/21-coga-minutes.html Lisa 16:26:57 kirkwood has joined #COGA 17:00:14 kirkwood has joined #COGA 17:17:53 Charli has left #coga 17:19:57 kirkwood has joined #COGA 17:22:09 kirkwood has joined #COGA 22:01:49 kirkwood has joined #COGA