10:34:53 RRSAgent has joined #coga 10:34:58 logging to https://www.w3.org/2024/01/22-coga-irc 10:34:58 RRSAgent, make logs Public 10:35:29 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 10:35:29 agenda? 10:35:29 clear agenda 10:35:34 read agenda from https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2024Jan/0030.html 10:35:41 agenda? 10:35:51 read agenda from 10:35:55 agenda? 10:37:30 agenda+ 10:37:36 agenda+ Sort out agenda for next week's meeting with AG 10:37:56 agenda+ Revised Mental health proposals at Proposed pattern and changes for Content-Usable version 3 10:38:21 agenda+ How to put changes into the next draft of content useable. 10:38:50 agenda+ New timeline. Lets take some pressure off. See our new time line 10:39:33 agenda+ 5 minutes on AG summary 10:45:50 scribe: Eric 10:46:28 agenda? 12:30:07 kirkwood has joined #COGA 12:57:51 Roy has joined #coga 13:19:27 Roy has joined #coga 14:49:08 Roy has joined #coga 15:39:06 lisa has joined #coga 15:41:15 lisa_ has joined #coga 15:41:21 agenda? 15:41:27 Q? 15:55:09 regrets: jennie 15:57:02 rashmi has joined #coga 16:00:08 Eric_hind has joined #coga 16:00:29 present+ 16:00:44 present+ 16:01:09 Becca_Monteleone has joined #coga 16:02:08 Rain has joined #coga 16:02:12 present+ 16:02:13 julierawe has joined #coga 16:02:17 present+ 16:02:38 present+ 16:03:00 JustineP has joined #coga 16:03:29 scribe: ric 16:03:33 scribe: eric 16:03:38 next item 16:03:42 present+ 16:03:47 tburtin has joined #coga 16:03:54 present+ 16:04:19 DavidSwallow has joined #coga 16:04:22 Lisa: Next weeks agenda includes mix discussion between content usable and WCAG 3 16:04:27 present+ 16:04:34 https://docs.google.com/document/d/1UAFHZuxmyhYAjZZyWxp_rvhIHuXmeWQosgVZD5LcxmM/edit#heading=h.kv0usnbv00t 16:05:00 Is this during our regular COGA meeting next week? 16:05:08 kirkwood has joined #COGA 16:06:21 Lisa: Topics include Subgroups, WCAG 3, outcomes, AG terminology coherence 16:06:47 confirming that the plan sounds good to me 16:07:00 Lisa: All COGA are invited to next meeting where this will be discussed (next week) 16:07:57 Julie: Good conversation to have on Clear language from our perspective versus WCAG 3 16:08:34 JMcSorley has joined #coga 16:08:42 present+ Jan 16:08:53 next item 16:08:59 present+ 16:09:57 agenda? 16:10:08 https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173714 16:10:16 take up item 5 16:11:33 Julie: Note currently there is voting on discussion Github; publishing starting point from links. What's new versus picking up from 2.2, guidelines, conformance model, etc. Github issues can be voted on. 16:11:45 AG debate about how to approach publishing WCAG 3: Here is a link to a summary of the Jan 16th discussion: https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173714 16:11:52 There are 4 main debates. Each one has its own GitHub comment that you can thumbs up or thumbs down. I am highlighting two of these debates: 16:11:59 The starting point should be the WCAG 3 outcomes. If you think the starting point should be publishing new WCAG 3 outcomes, then click thumbs up in this comment. If you think the starting point should be showing how WCAG 3 is compatible with WCAG 2.2, click thumbs down. https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173718 16:12:04 We should focus on guidelines (rather than conformance) for a while, then come back to conformance / structural updates. Thumbs up for "yes", down for "no, we should keep working on conformance / structure at the same time". https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173720 16:12:06 Rachael: Read the issues at a summary level if you can as a starting point. 16:13:47 q+ 16:13:54 Rachael: Two ways to move forward; take WCAG 2.2 and make changes and republish. Not from Silver. Other option is start from Silver and work from fall efforts. 16:14:50 This is the direct link to the comment that is most impactful. https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173718 16:15:53 ack j 16:15:59 When you click the link, wait for the page to fully load and the comment at the top is the one to focus on. 16:16:52 John: Fundamentally huge question with a lot of positive and negative for either choice. 16:18:48 Add a thumbs up to this comment: https://github.com/w3c/wcag3/discussions/33#discussioncomment-8173718 16:19:13 q+ 16:19:45 Julie: Link provided is main thumbs up/down perspective 16:19:59 ack next 16:20:07 ack next 16:20:11 q- 16:21:20 Rachael: Can offer a call to discuss the complexities; which she will (tomorrow) and will email COGA on meeting availability 16:21:23 take up item 2 16:22:29 https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.lhdm88jj5cym 16:23:19 Rashmi: Proposal 8 discussion New Pattern, Make it easy to return to the starting point (of a site hierarchy or multistep process) 16:23:34 Q? 16:26:26 q+ 16:26:27 Rashmi: Losing track of home page can be aggravated by stress, mental health and cognitive overload - disorienting. Reorientation can be assisted by providing affordances related to helping 16:26:38 ack next 16:27:34 +1 to Rain, re: homepage vs start of process 16:27:39 ? 16:27:40 Rain: Concern on differentiation of home page and start of a flow - perhaps they need to be split up in complex sites. 16:30:11 Lisa: We do have Making Step Clear already; could add further clarity related to this? We may also want to split home page/start of flow in other sections. Propose drafting this as a note. 16:30:39 proposal we put it in with a note that they split and / or also get meged into other patterns 16:30:54 +1 that makes sense for the current setup 16:31:04 +1 16:31:05 +1 16:31:11 +1 16:31:29 +1 16:31:35 +1 16:32:17 Lisa: Vote to include editors note on splitting this as a future instruction; voted positively by those present 16:32:24 Q? 16:34:13 Rashmi: Proposal 10, make Simplify complex purchasing processes (adding to current 4.6.2 Short Critical Path) 16:34:24 +1 16:34:26 +1 16:34:28 +1 16:34:30 +1 16:34:39 +1 16:34:42 any objections? 16:34:51 or more time to think 16:34:51 Lisa: Voted to include as example, no objections. 16:34:52 q+ 16:35:03 ack next 16:36:12 Rain: Concern on how to act on it - not as prescriptive as it might be. 16:36:32 Lisa: Clarify that this part of a set of examples 16:37:18 John: Recommend adding more text here around reduce cognitive load - Lisa added to proposal 16:37:29 +1 16:38:00 +1 16:38:05 q? 16:38:06 +1 16:38:10 +1 16:38:15 any objections? or more time to think 16:38:21 Lisa: Voted to include additional text, no objections. 16:38:29 abbey has joined #coga 16:40:25 Rashmi: Proposal 11: Clearly identify controls and their use or Make the relationship clear between controls and the content they affect. Make links and controls explicit; less/no inference required 16:45:03 Lisa: proposal is to add this text suggestion to 4.2.6.2 What to do as part of existing; 4.2.5 Make the relationship clear between controls and the content they affect (pattern). 16:45:10 happy with the edits? 16:45:20 +1 16:45:23 +1 16:45:29 +1 16:45:36 +1 16:45:41 +1 16:46:04 Lisa: Voted to include adjusted text, no objections. 16:46:27 agenda? 16:46:54 next item 16:47:02 Lisa: How to put changes in the next draft of content usable - discussion 16:48:02 Lisa: github folder structure review/branches.. proposes regular pull request. 16:48:43 Lisa: Proposal: Merge and resynch much more regularly. 16:49:38 q+ 16:50:11 ack next 16:51:01 Rain: This does make sense; I could plan out the larger change over to content usable in a few months. 16:51:51 q+ 16:52:03 ack next 16:54:49 Rashmi: Will need some help/experience with pull requests, Jan can help with the process, but there should be a coordinated effort to know/learn about branch process. 16:55:29 interersted in attending 16:56:03 Lisa: Jan to create some written process and work with someone from W3C 16:56:03 agenda? 16:56:46 +1 sounds good 16:56:58 next item 16:57:14 Lisa: We can plan out a code freeze (more or less) when Rain is ready to do the large merge. 16:57:27 https://docs.google.com/document/d/1XBu9OhGoMG4lLDBRaRFZZxGoNWW-aDkKkVKrypfPvVc/edit#heading=h.ykqwx9vsxdya 16:58:04 “Timeline for v3 of Content Usable” 16:58:42 Lisa: Topic, timeline to take pressure off, new structure, mental health, placeholders, images, etc and literary reviews. (Phase 1 Jan-April 2024) 17:00:34 where do editorial reviews fit in the schedule? 17:01:01 Lisa: Looking to get local (docs) style drafts, we can have lightweight placeholders, and similar draft level items as a way to remove pressure from the formal draft. 17:02:26 Have to drop, thanks! 17:02:39 Lisa: Do people want scheduled working meeting where we do literary reviews together? 17:03:01 +1 17:03:01 do we want a working meeting for lit reviews? 17:03:05 would be helpful 17:03:12 +1 17:03:21 I could do it if it was at the time of this meeting 17:03:33 And it would be helpful! 17:03:41 I could do either during this meeting or after this meeting. 17:03:42 Same, I could do at this time of the meeting. 17:03:51 Mornings EST fine by me 17:05:16 RRSAgent, publish minutes 17:05:17 I have made the request to generate https://www.w3.org/2024/01/22-coga-minutes.html lisa_ 18:15:00 kirkwood has joined #COGA 19:36:04 kirkwood has joined #COGA 19:39:57 kirkwood has joined #COGA 20:01:08 kirkwood has joined #COGA 20:47:47 kirkwood has joined #COGA