12:02:12 RRSAgent has joined #coga 12:02:17 logging to https://www.w3.org/2024/09/30-coga-irc 12:02:17 RRSAgent, make logs Public 12:02:18 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 12:04:24 agenda+ scribe. see: https://www.w3.org/WAI/GL/task-forces/coga/wiki/Scribe_list 12:04:54 agenda+ Ctaur : can we meet today? 12:05:08 agenda+ Ctaur : When can we rap up the feedback 12:05:30 agenda+ Structure summary 12:05:48 agenda+ What are we missing and what can we add (audit from studies) 12:05:48 . 12:06:09 agenda+ What are we missing - review ideas for next week 12:06:09 . 12:07:21 Agenda+ Tpac take aways 12:08:26 agenda order is 7 1 2 3 4 5 6 13:33:47 kirkwood has joined #COGA 14:03:04 janina has joined #coga 14:50:55 lisa has joined #coga 14:51:18 RRSAgent, publish minutes 14:51:19 I have made the request to generate https://www.w3.org/2024/09/30-coga-minutes.html lisa 14:51:39 agenda? 14:53:09 agenda order is 1 2 3 7 4 5 6 14:54:57 q? 15:00:40 Rain has joined #coga 15:00:56 Jennie has joined #coga 15:02:07 take up item 1 15:02:14 present+ 15:02:27 scribe+ jennie, lisa 15:02:30 julierawe has joined #coga 15:02:33 present+ 15:02:35 present+ 15:02:43 next item 15:02:48 close item 1 15:02:51 present+ 15:02:53 next item 15:02:58 Lisa: People can sign up to scribe on the list, then it doesn't need to be an agenda item 15:03:19 take up item 4 15:04:09 Lisa: question 1 - do we want to meet today? 15:04:11 DavidSwallow has joined #coga 15:04:14 take up item 2 15:04:19 ...that is in reference to the CTAUR 15:04:20 present+ 15:04:26 ...after this call 15:04:52 ...or is there a better time. We need to tell them when we will get back to them. 15:04:59 John K: I can meet 15:05:07 David: I can meet for a half an hour 15:05:14 Lisa: let's meet for a half hour, get next steps 15:05:53 ...Can Jennie review asynchronously? 15:05:57 Jennie: not until Friday 15:06:10 Lisa: OK, that's helpful information. 15:06:29 ...What about next Monday after the call to wrap things up? 15:07:38 ...then we could have a meeting for anyone who can meet for a half hour 15:07:40 tiffanyburtin has joined #coga 15:07:44 present+ 15:07:47 rashmi has joined #coga 15:07:48 ...And I can give a half hour during the call 15:07:51 David: works for me 15:07:57 Lisa: any objections? 15:08:00 Present+ 15:08:09 next item 15:08:36 Lisa: I think we can wrap up feedback by end of next week 15:08:41 David: I think that will work. 15:08:47 ...mid to end of next week 15:08:58 Frankie has joined #coga 15:09:14 present+ 15:09:15 next item 15:10:07 Julie: a couple of highlights 15:10:19 ...#1 - Monday looked back at the past 6 months of decisions 15:10:37 ...some discussion about the way accessibility guidelines working group is putting summaries into Github threads 15:11:01 ...I shared it can be daunting to participate in the meetings, even with these summaries. 15:11:13 ...It was a thoughtful discussion 15:11:26 ...#2 - Monday afternoon and most of Tuesday - conformance 15:11:36 ...We went through a "broken" website 15:11:49 ...We thought about - if there is a webpage with a video with no captions 15:11:56 ...This helped us discuss conformance levels. 15:12:27 ...We discussed: should we separate a conformance model 15:12:45 ...#3 I went to the joint meeting with accessibility guidelines working group and internationalization 15:12:54 agenda+ is our agenda page good? should we request something similar to ag. how can we support it? 15:12:56 ...topic focused on when do they want to get involved in drafts 15:13:03 ...Answer: early, but not too early 15:13:13 ...for WCAG 3 they want it after exploratory 15:13:22 ...Moving into the 3rd phase 15:13:48 ...We also introduced attendees to the new subgroups, and the community group, and encouraged people to join 15:14:01 John K: I joined that as well 15:14:35 ....I commend Julie on how we can connect with them, and the timelines 15:14:43 q+ 15:14:44 ...We should work with them more 15:14:57 ack next 15:15:05 Rain: the summaries were good. 15:15:20 ...Re internationalization: there was emphasis from them that they want everything in Github 15:15:33 ...Well supported by Chuck as the accessibility guidelines working group chair 15:15:43 ...we explained that Github is not accessible for our group. 15:16:18 q+ 15:16:22 ...We got to agreement (as well as with ARIA) - maybe we could have more of a structure for inviting them to meetings strategically 15:16:33 ?+ 15:16:36 q+ 15:16:40 ...then they can take the task of getting items added into Github. No formal agreement, but discussion 15:16:47 ...A good desire by all groups to work together. 15:17:11 ...The other take-away I had is the challenge of conformance 15:17:20 ...How does the COGA task force define harm? 15:17:43 ...During the exercise Julie mentioned - the group I was in was heavy on those very impacted by barriers 15:18:19 ...Our scores indicated the severity of the failures the most compared to other groups, possibly because of the focus on harm. 15:18:22 q+ to ask for link to summaries /scedule and time table it 15:18:24 q+ tpac exercise 15:19:00 ...Currently: everything is marked "the worst" which means that nothing becomes highlighted as "the worst." 15:19:08 ...Then, no progress can be made. 15:19:24 ...I think the COGA task force understands harm differently than other groups. 15:19:36 ....Maybe we should try to define harm to help conformance discussions move forward. 15:19:46 Lisa: Julie - do you think there is a time limit for this? 15:19:53 ...Would October 14th work? 15:19:55 +1 to Rain 15:20:10 Julie: The conformance conversation is part of the accessibility guidelines call tomorrow. 15:20:30 ...I agree with Rain - this is in early conversations. There are conversations around safety, like flashing. 15:20:46 ...There was 1 conversation about usability vs accessibility 15:21:06 ...But I think that somehow expressing confusing navigation for the most important piece of information on a page. 15:21:23 ...I think Gregg was supporting the idea that having information that is easy to understand and find being essential. 15:21:40 Lisa: as a date, provisionally, to have that discussion on the agenda. 15:22:00 q+ 15:22:19 Julie: re internationalization - Rain had mentioned the desire to do everything through Github. 15:22:40 ...The internationalization group would like us to use a "short checklist" - which is not short, but links to other checklists. 15:22:54 ...They want us to go through this before we submit anything, which feels like a lot 15:22:57 Frankie has joined #coga 15:23:05 ...They see this as a solution, I see it as a lot of work. 15:23:11 John K: I second what Julie is saying 15:23:33 Lisa: Julie - can you put links for the schedules 15:23:34 Justine has joined #coga 15:23:44 ...for internationalization 15:23:48 ...and the checklist 15:23:57 ...I will put it on the things to go onto future agendas 15:24:10 Julie: I can. 15:24:14 we should really look at those 15:24:39 Lisa: I would like Jan to be on the call at the same time. 15:25:19 ...If anything else people want to discuss we can put on a future agenda. 15:25:41 ack next 15:25:50 ack Rain 15:25:58 Rashmi: I attended for a short period 15:25:59 Internationalization has requested we do a self-review before submitting any drafts to them: https://github.com/w3c/i18n-request/issues/new?assignees=&labels=REVIEW+REQUESTED%2CSR%2Cpending&projects=&template=request-a-self-review-check.yml&title=Spec_name+2023-mm-dd 15:26:04 ...There was a conversation about diagnoses 15:26:14 ...There are some parallel functional needs 15:26:23 ...We should take care of that in our group, I think 15:26:29 Lisa: Yes. 15:26:29 Internationalization also shared its "short checklist" that includes links to longer checklists: https://www.w3.org/International/i18n-drafts/techniques/shortchecklist 15:26:36 ...Do you feel we should discuss it more? 15:26:46 Rashmi: I think it is important. You put useful points 15:27:03 Lisa: We should on the pending agendas functional needs vs diagnosis 15:27:15 ...and maybe memorialize it in our language section. 15:27:28 Rashmi: yes. 15:27:39 ack next 15:27:40 Lisa: I will also follow up what is happening with the functional needs task force 15:27:48 ack next 15:27:49 lisa, you wanted to ask for link to summaries /scedule and time table it 15:28:04 q- 15:28:13 ack next 15:28:21 (tiffiany) 15:28:32 Tiffany: in the future when these types of exercises happen, there needs to be short, simple, clear expectations for the test we will do 15:28:51 ...My group: it seemed like we didn't have consensus on what we should be doing 15:29:03 ...We defaulted to WCAG 2.2 style, then applied it to how hard it would be 15:29:11 ...Some of us scored it harder than others 15:29:25 +1 15:29:26 ...I think we need to get across how difficult navigating the web is when you have lived experience 15:29:42 +1 15:30:08 John K: I find it difficult to navigate around the rooms - it would good to have COGA people around in all the different rooms 15:30:19 ...Finding Zoom links was often difficult in the ecosystem 15:30:35 ...In the past we have had a side chat for COGA people to help find Zoom links 15:30:44 ...It would be helpful for the future 15:31:02 q+ 15:31:07 ack next 15:31:09 Lisa: I will copy that to my to-do list 15:31:21 Rain: To add to what John shared 15:31:39 q+ 15:32:22 Rain: it might be good for future TPACs to have the COGA task force look at or participate in the layout of the scheduling 15:32:28 ...to try to make it more navigable 15:32:34 +1 15:32:37 ack next 15:32:45 ack Rain 15:33:28 ack next 15:33:45 Jennie: I added difficulties I had with the calendar time zones into my feedback in the surveys. I encourage members to share as appropriate in those as well. 15:34:05 Lisa: Sounds like the conformance and harm conversation is the highest priority 15:34:17 ....Might be worth making a proposal. 15:34:40 next item 15:34:48 EA has joined #coga 15:35:09 Rain: We have significantly more qualitative information that came out of the studies than we anticipated. 15:35:22 ...We need to adjust our timing to understand it all. 15:35:35 ...I will share high level findings - from skimming through everything 15:35:41 Q+ to ask if th enalisis of all the papers? 15:35:41 ...Thank you to those who jumped in 15:35:51 present+ 15:35:51 ...Eric has been very helpful getting the group going 15:35:58 ...Alastair jumped in as well 15:36:23 ...A lot of the data will help more than just COGA 15:36:31 ...It could benefit all W3C publications. 15:36:48 ...I also had excellent conversations with Kevin White and Tamsin 15:36:55 ...to talk about the goals of the study. 15:36:58 Q+ to still requesting access 15:37:06 ...Tamsin will work with Shawn to figure out what to do 15:37:27 ...After the discussion with Kevin - there are complexities with making changes to the design style 15:37:42 ...This week: I will explore some design iterations that address the high level feedback 15:38:00 ...Then I will meet with Kevin and Tamsin to understand what the complexities are within the W3C design system 15:38:07 ...To help understand potential blocks. 15:38:21 ...Then we can bring it back to this task force for analysis 15:38:59 ack next 15:39:00 lisa, you wanted to ask if th enalisis of all the papers? and to still requesting access 15:39:18 Lisa: do you still need people to do the analysis for the user feedback? 15:39:22 Rain: yes. We have a lot. 15:39:28 Lisa: I still don't have access 15:39:40 ...I have sent another request. 15:39:58 Rain: I will make sure you have access right now. 15:40:18 https://docs.google.com/document/d/1488tG8loN-lmJ9vJT9nAlIVnbyyLVd27VeIkFferrQs/edit 15:40:37 Rain: Eric did a nice write up in a table form of the steps 15:40:38 Triage spreadsheet: https://docs.google.com/spreadsheets/d/1ivrG_nl0Ox90hoMv9yHj1yt5-pbw-pmKXmdZ_epCwz4/edit?usp=sharing 15:41:19 Lisa: I should have time next week if anyone wants a working meeting where we work at the same time. 15:41:25 ...Sometimes helpful 15:41:51 John K: I would find it helpful. 15:42:34 Rain: the spreadsheet shows who is taking on each section to triage. 15:42:46 ...Please add your name next to any you are working on. 15:42:56 ...This is up to date in real time. 15:43:33 ...There is a section in the meeting minutes which starts with "The Ask:" 15:43:43 RRSAgent, publish minutes 15:43:45 I have made the request to generate https://www.w3.org/2024/09/30-coga-minutes.html lisa 15:43:51 ...This describes the steps to triaging 15:44:08 https://docs.google.com/document/d/1488tG8loN-lmJ9vJT9nAlIVnbyyLVd27VeIkFferrQs/edit -link to the ask from stucture 15:44:38 q? 15:44:40 Rain: any other questions? 15:45:07 Rain: again, only high level overview 15:45:16 ...Themes I was able to see quickly from reviewing data 15:45:38 ...Participants: 18 which is a lot for hour long sessions 15:46:00 ...Self proclaimed role: personal interest = 15 15:46:16 ...(Rain continued reviewing the list) 15:46:39 ...Only 1 identified as care provider, however, I think that will go up because of information shared during the sessions. 15:46:49 ...This may impact other numbers as well 15:46:49 agenda? 15:47:08 John K: was the terminology of "care provider" the issue? 15:47:20 Rain: that was the short name - it was whatever we put in the survey 15:47:43 ...11 said 4 plus years in familiarity with cognitive accessibility as a concept 15:47:52 Q? 15:47:58 ...Some people dropped out which may have impacted our ability to get newer people 15:48:30 ...Familiarity with Making Content Usable: 7 very, 5some, new 6 15:48:38 ...9 text to speech users 15:48:56 ...8 each for visual reading aids or high contrast mode 15:49:17 ...There are question marks next to diagnoses disclosed during the interviews 15:49:49 ...good spread of these given this type of work. 15:50:39 ...All familiar with W3C materials shared that the improvements they were noticing would be helpful for all of the TR formatting, not just the COGA ones 15:50:56 ...High level themes: 15:51:02 tiffanyburtin has joined #coga 15:51:11 ...1: Need both TOC and the "small buckets" 15:51:24 ...that can be brought forward by the individual and put away at will 15:51:35 ...Also need the "small buckets" model - more multi-page 15:52:59 ...1 version of the small buckets: big buttons at the bottom 15:53:14 ...Having it above the fold for the majority of users would be helpful 15:53:42 ...We also had an introduction model. 15:53:50 ....This was followed by a list that was clickable. 15:53:55 ...This was helpful for people. 15:54:33 *@Lisa - ready to take over scribing? 15:55:03 thanks jennie 15:55:14 finding: people loved the roles 15:55:53 but... they didnt like the terms on the roles becuse people cant find themselves 15:56:18 so changed to stages in process, but that was worse 15:56:49 need to work on names of the roles, less jargon 15:57:15 people liked the chucking buckets 15:57:38 but scafolding as a term failed as only education know what we ment 15:57:49 navigation was also confucing rather then table of content 15:58:03 icons good, but need work 15:58:29 clarity between section helped. 15:58:47 colaping sections were good so lomg and contol f works 15:59:11 we can impove linked to sections 15:59:21 more in the doc 15:59:34 and then need to find out what is realistic 15:59:47 RRSAgent, publish minutes 15:59:49 I have made the request to generate https://www.w3.org/2024/09/30-coga-minutes.html lisa 16:00:46 also think of what is missing in the conent 16:00:54 RRSAgent, publish minutes 16:00:56 I have made the request to generate https://www.w3.org/2024/09/30-coga-minutes.html lisa 16:01:39 topic: CTaur 16:01:45 our feedback is https://docs.google.com/document/d/1dFjMfobPdWUz0a-wm6NQKN_nRXVjSLvJlHcgFF0SnHc/edit