13:49:43 RRSAgent has joined #coga 13:49:47 logging to https://www.w3.org/2026/03/30-coga-irc 13:49:47 RRSAgent, make logs Public 13:49:48 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 13:49:54 agenda+ scribe 13:50:17 agenda+ Meeting for next two weeks 13:50:41 agenda+ Wcag review ? - what to review 14:52:09 Lisa has joined #coga 14:52:15 Agenda? 14:52:31 agenda+ new name for guidlines? 14:55:06 Q? 14:55:58 RRSAgent, publish minutes 14:56:00 I have made the request to generate https://www.w3.org/2026/03/30-coga-minutes.html Lisa 14:57:24 Topic: COGA (Cognitive Accessibility) Task Force 14:57:45 zakim, start meeting 14:57:45 RRSAgent, make logs Public 14:57:47 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 14:59:09 Agenda? 15:03:24 Jennie_Delisi has joined #coga 15:03:29 present+ 15:05:40 no quarem 15:06:06 Jan has joined #coga 15:06:14 present+ 15:10:19 Jennifer has joined #coga 15:10:24 quarum 15:10:41 scribe+ 15:10:49 scribe+ Jennie_Delisi 15:11:05 Lisa: talking about schedule for next 2 weeks 15:11:21 LenB has joined #coga 15:11:23 Meeting for next two weeks 15:11:23 Thursday, Apr 2 - no call 15:11:23 Monday, Apr 6 - considering an informal 30 minute meeting. 15:11:23 Tuesday, Apr 7 - no call 15:11:26 present+ 15:11:42 Lisa: Easter and Passover are impacting schedule 15:12:01 kirkwood_ has joined #COGA 15:12:16 Lisa: Any questions/thoughts? 15:12:20 Present + 15:12:49 Lisa: For those unable to make calls - you can review asynchronously. 15:13:07 ...If no quorum we will collect feedback from those who are present, then have an extra call. 15:13:51 next item 15:13:57 close item 1 15:14:01 close item 2 15:14:05 next item 15:14:52 (Looking at the tab: Schedule, actions, and minutes) 15:15:11 Lisa: top section: actions and to do items - drafts ready for review - error handling 15:15:26 ...This links in the document to "Drafts for github" 15:15:59 ...You don't have to go anywhere else in the document to see what is being discussed. 15:16:21 ...This links to the spreadsheet with usernames, but you don't have to (link name row 1 in spread sheet) 15:17:06 ...This will take you to the exact row in the spreadsheet. 15:17:40 ...In the spreadsheet - the notes should generally be the same as the issue description in the github description proposal draft. 15:18:02 ...The spreadsheet also contains links to related issues in Github 15:18:21 ...You can vote within the Google document if that works easier for you than the spreadsheet 15:18:52 ...You can add comments in either the Google document or the spreadsheet 15:19:07 ...Next call: this is what we will review. 15:19:31 ...Any questions? 15:19:32 Q? 15:19:47 John K: what is the purpose of the spreadsheet? 15:20:10 Spreadsheet title: "Review Tracking WCAG 3 - W3C Editor's Draft..." 15:20:19 Lisa: Review tracking spreadsheet 15:20:55 ...Some people prefer the Google document, others prefer the spreadsheet. 15:21:12 ...both are options to use 15:22:08 ...We can have another call if necessary 15:22:23 ...There are some issues which appear to be missing. 15:22:41 ...We also have some related feedback. 15:22:56 ...These are in the tabs "Missing from WCAG 3" and "Other WCAG 3 Feedback" 15:24:09 ...Then if you miss the Monday call, you can start at the top of the tab "Schedule, Actions and Minutes" and find what is happening 15:24:13 https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?tab=t.uggxirp4slpc#heading=h.crubeit1ngyb 15:24:21 scedule for wcag review 15:24:23 (this is the link to that location) 15:25:03 Q? 15:25:08 (Jan and Jennie like this) 15:25:08 next item 15:25:37 Lisa: we have an old action item: finding a new name for Making Content Usable 15:26:05 ...lots of discussion 15:26:27 ...Cognitive Accessibility Guidance - what was discussed 15:26:57 ...Issue: original document name is long, some felt their disability of interest was not included and didn't match local naming of disability 15:27:37 ...Issues continued: some people were not reading the abstract and information which expanded on what was included (but not in the title) 15:27:40 LenB has joined #coga 15:27:57 ...Issue: some people already know the title Making Content Usable 15:28:28 ...Other considerations: didn't want specific vocabulary like impairment 15:29:11 ...Other considerations: terminology impacted jurisdiction differences (legal) 15:30:05 ...We cannot use the phrase Cognitive Accessibility Guidance because it is considered too close to other W3C titles 15:30:16 ...John K and Julie reviewed several similar options 15:30:55 ...Best practices will be less likely to be followed in some areas. 15:31:24 kirkwood_ has joined #COGA 15:31:29 ...Some places will include best practices in legal requirements but not others 15:32:25 ..."Heuristics" is included in one suggestion - some do not know what that means 15:32:27 Cognitive Accessibility Protocols 15:33:05 (Lisa's suggestion): Cognitive Accessibility (followed by longer subtitle) 15:33:20 John K: Are we allowed to use protocols? I think it is a good way to name it 15:33:23 Lisa: I like that 15:33:45 who want Cognitive Accessibility Protocols 15:33:48 +1 15:34:03 +1 15:34:05 +1 15:34:09 0 15:34:12 +1 15:34:13 (Jennie): an option fo rme 15:34:17 I am not how that will translate 15:34:20 0 15:34:56 Jan: I don't know enough about how people speaking other languages will understand that word 15:35:23 ...Not my area of expertise but might need some feedback. 15:36:08 Jennie: might need to check set definitions 15:36:27 John H: agree, with protocols and procedures in government this could be something to check 15:36:44 Jennie: also in IT shops, there could be specific definitions for protocols 15:37:02 Lisa: Sounds like we would want to pursue if it works with translations and defintions 15:37:25 John K: great acronym, too! 15:37:45 Lisa: We can take this one to the next step 15:37:53 q+ 15:38:17 Lisa: Do we want to review other suggestions? 15:38:17 ack next 15:39:14 Jennie: could the group pursue 2 or 3 at the same time? 15:39:21 Jennie thinks a back up might be Cognative accessibility with subtitle making content usable for peopel with learning and cognative disabilities and mental health disabiliabilities ect) 15:39:36 ...Lisa's suggestion before ensures greater search follow up for those with previous experience with the document 15:39:38 +1 I do like "cognitive accessibility" as a more streamlined option 15:39:51 Lisa: Does anyone prefer Cognitive Accessibility without protocols? 15:40:24 Jennifer: I do. Protocols feels technical. 15:40:58 John K: Are there other ones? What is the whole ecosystem? 15:41:38 ...I am wondering if "Cognitive Accessibility" without anything else might be misunderstood. 15:41:40 q+ 15:41:46 ack next 15:42:24 jenny digital cognative accessibility 15:42:39 John K: I am unsure if the word digital is important. 15:43:04 Lisa: We are not doing anything outside of digital, though someone looking at it may be looking at environment and digital 15:43:14 John K: We are publishing under the world wide web 15:43:28 Lisa: But some who receive the document may not know who published it when they receive it 15:43:55 John K: Did we discuss this in the Wayfinding and other areas? 15:44:07 Lisa: For Making Content Usable - this is for that document 15:44:19 John K: This is under the umbrella of web 15:44:29 I'm leaning towards this: "Cognitive Accessibility: Making Content Usable for All Users" 15:44:32 Lisa: People may not hear "making content usable" if we remove that" 15:45:08 Lisa: We will not include "all users" because people interpret this to include other disability groups 15:45:32 John K: aging is not considered a disability in many places 15:46:05 Lisa: some individuals also do not consider themselves as having a disability even if they qualify as having one 15:46:32 ...subheading could include aging 15:46:43 ...or age-related 15:46:59 John K: it includes memory and processing speed. E.g. 7 page form 15:47:11 Lisa: and learning new things 15:47:50 ...this is why we wanted a long subtitle - so we can add different groups 15:48:06 John H: what about COGA guidance? 15:48:13 Lisa: We cannot use guidance 15:48:27 ...we could use COGA 15:48:31 q+ 15:49:14 COGA (COGnative Accessibility and making caontent useable for ......... 15:49:28 ack next 15:49:56 Lisa: this could include the subheading to help those new to the topic 15:50:09 -1 still, sorry, on this one 15:50:30 Lisa: Cognitive Accessibility Protocols, Cognitive Accessibility 15:50:34 ...each with the subtitle 15:50:56 ...We still want to look into translation and definitions for protocols 15:51:06 Digital cognative accessibility 15:51:15 Lisa: any more suggestions? 15:51:24 johnkirkwood has joined #COGA 15:51:30 Making Content Usable: 15:51:41 Len: Leveraging making content usable? 15:51:52 ...Then add one of the titles suggested above? 15:52:10 John K: Usable - not something that holds in legal circles 15:52:35 ...often associated with usability studies, so wondering if this would impact how people review the information 15:52:52 ...Usable vs accessible is part of the differences. 15:53:02 Len: that is an interesting question 15:53:10 ...Usable is used in real estate, medication 15:53:27 ...for example a usable amount of marijauna 15:53:50 ...under the law has its own meaning, and I am wondering if this is a good question for a lawyer 15:54:34 Lisa: Making Content Usable - Cognitive Accessibility 15:54:47 Making Content Usable: Coganive accessibility protacals for digtal accessibility or ....................................................... 15:55:06 Lisa: This could then include the whole list 15:55:16 ...then Making Content Usable is the short name 15:56:02 USable seems nice. Accessiblity protocols. Seems to have more legal weight to me. 15:56:20 Lisa: I will ask for a list of what they are comfortable with 15:56:53 ...Each one comes with a subheading with the details 15:57:00 Making Content Usable: Coganive accessibility protacals for digtal accessibility ; cognative accessibilty ; digital cognative accessibilty , cognative accessibilty protocals 15:57:04 My apologies - I have to drop for another call 15:57:25 and cognative accessibilty 15:57:34 cany chance we sould have all the options in irc? 15:57:37 sorry 15:57:49 Making Content Usable: Coganive accessibility protacals for digtal accessibility ; cognative accessibilty ; digital cognative accessibilty , cognative accessibilty protocals 15:57:51 Eric_hind has joined #coga 15:57:54 present+ 15:58:16 RRSAgent, publish minutes 15:58:18 I have made the request to generate https://www.w3.org/2026/03/30-coga-minutes.html Lisa 15:58:24 Cognitive accessibility; digital cognitive accessibility, cognitive accessibility protocols (if this works); 15:58:54 Cognitive Accessibility Protocols 15:58:56 Lisa: This would go to the AG chairs, internationalization 15:58:57 0 for the names in the list 15:58:57 Making Content Usable: COGA Protocols, 15:58:57 Making Content Usable: Digital Cognitive Accessibility, 15:59:04 these feel better 15:59:21 I also like: Making Content Usable: Digital Cognitive Accessibility 15:59:32 Cognitive accessibility Strategies +1 15:59:35 I really like Making Content Usable: Digital Cognitive Accessibility 16:00:11 Lisa: Strategies - this has been shared as being difficult in some legal areas 16:00:28 RRSAgent, publish minutes 16:00:29 I have made the request to generate https://www.w3.org/2026/03/30-coga-minutes.html Lisa 16:00:48 Prefer just “Cognitve Accessiblity” 16:01:13 RRSAgent, publish minutes 16:01:15 I have made the request to generate https://www.w3.org/2026/03/30-coga-minutes.html Lisa 18:59:06 johnkirkwood has joined #coga 19:01:21 johnkirkwood has joined #coga