13:23:10 RRSAgent has joined #coga 13:23:14 logging to https://www.w3.org/2024/03/11-coga-irc 13:23:14 RRSAgent, make logs Public 13:23:15 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 13:23:21 scribe: becca 13:23:35 scribe+ Becca 13:32:03 agenda+ 13:32:15 agenda+ rminder calls: see https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2024Mar/0022.html 13:35:09 agenda+ Please look at Supported Decision Making - Issue Paper . Is there a section you want to work on? We will go over the structure next week (hopefully) . See https://docs.google.com/document/d/1g9N-_3l-d6t0ppZcIIZ98k00x7ZE7h3ayq0OCX9Ycu4/edit#heading=h.rhs6n8lpznbz 13:35:45 agenda+ Review mental health propsal at https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit . do we want to recommend more or less levels in a site, . Current proposal is not make a change or recommend site depth, but we want to bring up again with larger group 13:36:03 ow do we write up citations in issue papers? Options : Reference the line number Links Full citations https://www.w3.org/Guide/manual-of-style/ 13:36:42 agenda+ does anyone need agenda time in two weeks time? 13:36:52 agenda+ AG summary 13:37:06 Agenda+ if time - ow do we write up citations in issue papers? Options : Reference the line number Links Full citations https://www.w3.org/Guide/manual-of-style/ 14:48:43 lisa has joined #coga 14:48:47 RRSAgent, publish minutes 14:48:48 I have made the request to generate https://www.w3.org/2024/03/11-coga-minutes.html lisa 14:48:55 agenda? 14:51:09 agenda order is 1, 2,5, 3, 4, 6 14:52:14 scribe+ Becca 14:52:50 regrets+ Julie, Rain 14:52:58 close item 5 14:59:19 q? 15:00:25 rashmi has joined #coga 15:00:56 Becca_Monteleone has joined #coga 15:00:57 JMcSorley has joined #coga 15:01:02 present+ 15:01:04 present+ Jan 15:01:17 Eric_hind has joined #coga 15:01:30 Jennie has joined #coga 15:01:35 present+ 15:01:37 next item 15:01:40 scribe+ Becca_Monteleone 15:02:41 Lisa: Reminder for Github Editor training call tomorrow, 7 March 15:03:25 Lisa: Added training section to main COGA wiki page, including link to IRC training, Github for editors, Github for members 15:03:33 jeanne_ec has joined #coga 15:03:45 present+ 15:03:58 present+ 15:04:26 Lisa: Github for Editors training includes key terms and processes for on- and offline editing 15:05:27 Lisa: Github for Members training page links to AG primer, as well as key terms for basic processes 15:06:24 tburtin has joined #coga 15:06:47 present+ 15:07:05 kirkwood has joined #COGA 15:07:13 Github Editor training tomorrow, 7 March, EST 9:00 AM CET 2:00 PM Uk 1:00 PM Israel 3:00 PM 15:07:30 Can we record the call tomorrow so that we have that available for review later? 15:07:54 Q? 15:07:58 present+ 15:08:21 +1 for the recording 15:08:28 present+ 15:08:36 present+ 15:08:42 Lisa: Will try to record tomorrow 15:08:43 Frankie has joined #coga 15:08:45 next item 15:10:22 EA has joined #coga 15:10:24 Lisa: Last week voted to make separate issue paper on supported decision-making. Lisa has started to compile elements of this paper from other documents and draft a structure. 15:10:32 Present+ 15:11:58 Lisa: Created "to-do" tags on the document so people can contribute small sections at a time 15:12:12 Q? 15:12:19 Lisa: Will review structure next week. 15:12:33 next item 15:14:43 q+ 15:15:32 ack lisa 15:15:33 Rashmi: New proposal #13: Findability. Suggesting change in text re: appropriate type of hierarchy 15:16:35 Lisa: This suggestion comes from a lot of research in mental health about findability. There is conflicting research about deep vs. flat hierarchies 15:17:35 Lisa: current pattern 4.3.2 does not make reference to how deep a hierarchy should be 15:18:08 q? 15:18:09 Lisa: Recommendation is to suggest testing with users based on the site's content 15:19:25 John: Suggest focusing on methods for making things more findability (e.g. in-line search) rather than only focusing on hierarchy - since how flat or how deep is findable depends on individual cognitive load. 15:20:33 John: There are conflicting access needs, so pointing to tools for finding vs. how to chunk seems important 15:21:27 q+ 15:21:58 John will look at current pattern on findability 15:22:11 https://www.w3.org/TR/coga-usable/#make-the-site-hierarchy-easy-to-understand-and-navigate-pattern 15:22:46 https://www.w3.org/TR/coga-usable/#objective-2-help-users-find-what-they-need-0 15:22:47 q+ 15:22:55 ack next 15:22:56 Lisa: Do we also need to recommend site maps? 15:24:21 Tiffany: Utilizing multiple ways to navigate raises concerns about wording - on flat pages, can still be hard to find the correct information even with headings and find function 15:25:02 ack next 15:25:09 Lisa: Can Tiffany and John come to next Mental Health subgroup to create a new proposal? 15:26:21 Jan: has research explored utility of user being able to convert a modular design to a flat design? Making sure semantic markup follows - also interested in discussing the research on this 15:26:21 q- 15:28:06 Lisa: Current proposal does already reference redundant ways of finding content, which addresses some of these concerns 15:29:12 Rashmi: research says that deeper hierarchy it is easier for users to go back; users more likely to get lost in flatter hierarchy 15:29:53 Research tracking doc https://docs.google.com/spreadsheets/d/1eKNrofGubnpQE6mO-vxmI-1MW5nA2LDj0LxebREPRGA/edit?resourcekey#gid=1686096268 15:30:46 Lisa: reviewing current research, there is not consensus, which led subgroup to think it is more about the content. 15:31:13 proposal 8 15:31:14 https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.lhdm88jj5cym 15:33:14 Rashmi: revised proposal 8 - 8.1 recommends making it easy to go to starting directly. 8.2 deals with multistep processes. 15:35:53 Q? 15:36:42 John: question the word "starting point" for 8.1 instead of "homepage." Starting point more relevant for process (8.2) 15:37:23 q+ 15:37:42 q- 15:37:58 Lisa: Will replace starting point with home page in 8.1 15:39:41 Rashmi: reviewing proposed pattern 8.2: https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit#heading=h.z6oo3zn072u6 15:39:59 Q? 15:40:27 John: Getting back to first step or just where you were in the process? 15:40:36 proposal 15:40:38 8.1: Make it easy to return/go directly to home page of a site or sub- site. 15:41:01 +1 is agree, 0 more time, -1 real issue 15:41:13 +1 15:41:16 +1 15:41:18 +1 15:41:22 +1 15:41:24 +1 15:41:24 +1 15:41:25 +1 15:41:29 +1 15:41:31 +1 15:41:34 I have questions about the wording. 15:42:44 Tiffany: language around "returning to a subpage" is not clear to me. 15:43:42 Lisa: Subsite in 8.1 refers to different homepages nested in a larger site (e.g. departments in a university). Both should be clear to navigate to. 15:45:48 Tiffany: wording around clear menu navigation or page navigation? 15:46:17 Lisa: Already covered in content usable Objective 2 15:46:40 Lisa: This new proposed objective specifically calls out homepage and/or first step 15:48:18 Tiffany: The word subsite is still not clear in 8.1. Sounds like these are major navigation sections. 15:48:31 Lisa: Call for suggestions for a clearer term to differentiate 15:49:02 Tiffany: major navigation page, landing page? 15:49:27 q+ 15:49:27 Jan: Landing page and home page are the same to me. 15:50:19 Lisa: We are trying to call attention to when there is a new template for a specific section of a site. 15:50:21 "A landing page is a standalone web page that a person "lands" on after clicking through from an email, ad, or other digital location" https://mailchimp.com/marketing-glossary/landing-pages Seems to have several meanings! 15:50:57 q+ 15:51:39 Lisa: want to be able to recommend not only going to homepage of website, but first page of specific section 15:52:00 ack next 15:53:25 Jennie: one place this comes up was the employment section of an organization's website. Like "relevant landing page" but maybe add additional explanation - like "for a major section" or "a group of webpages" 15:53:26 maybe "section landing pages?" 15:53:55 I think the use of the term "relevant" might be confusing 15:54:07 ack Jennie 15:54:11 Jennie: make a note that we should use the same language as WCAG 3 15:54:44 i like: a landing page of a section of a site 15:55:14 q? 15:55:50 +1 to John's wording on landing page 15:56:16 Rashmi: some confusion around "landing page" for when you go to a page through an external link. 15:56:23 q+ 15:56:41 I agree with Rashmi - the use of the term landing page can be the same as a home page 15:56:53 Lisa: will define landing page. 15:57:00 ack next 15:57:04 ack next 15:57:37 ack Jennie 15:57:45 Jennie: to a user, landing page is the place they arrived at; to a designer, it may be different because of site design. 15:58:12 * Rashmi - I am glad you brought up that perspective. 15:58:26 +1 Jennie I recognize balancing the definition between user and developer/designer. 15:58:33 Make it easy to return/go directly to the home page of a site or relevant landing page of a set of Web pages. (to change with wcag 15:58:40 +1 is agree, 0 more time, -1 real issue 15:58:49 +1 15:58:53 +1 15:58:59 +1 15:59:00 +1 15:59:01 +1 15:59:10 +1 15:59:21 +1 15:59:23 I need to leave for another meeting - sorry! 15:59:40 New Pattern 8.2: Allow the user to return directly to the starting point of a multistep process 15:59:49 +1 is agree, 0 more time, -1 real issue 16:00:06 +1 16:00:11 +1 16:00:24 +1 16:00:39 +1 16:00:59 +1 16:01:24 Trying to catch up but I think +1 16:02:14 +1 16:02:16 john thinks it is ok, but we need to look at objective 2 all together as a draft 16:03:09 RRSAgent, publish minutes 16:03:11 I have made the request to generate https://www.w3.org/2024/03/11-coga-minutes.html lisa 16:18:49 kirkwood has joined #COGA 17:47:15 kirkwood has joined #COGA 18:58:30 kirkwood has joined #COGA 20:58:28 kirkwood has joined #COGA 21:16:47 kirkwood has joined #COGA 21:35:09 kirkwood has joined #COGA 23:30:10 kirkwood has joined #COGA