13:55:10 RRSAgent has joined #coga 13:55:14 logging to https://www.w3.org/2023/08/14-coga-irc 13:55:14 RRSAgent, make logs Public 13:55:45 Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference 13:55:46 regrets+ EA , Rain 13:55:46 aagenda? 13:55:46 agenda? 13:56:32 clear agenda 13:57:14 agenda+ updates, Github WCAG 3 training , ISO standard, etc 13:59:28 agenda+ New versions of issue papers (by Becca) on conversational interfaces https://docs.google.com/document/u/0/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit 13:59:42 agenda+ New versions of issue papers (by Becca) on conversational interfaces https://docs.google.com/document/u/0/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit [from lisa] 14:00:39 agenda+ Issues in github see https://github.com/w3c/coga/issues?q=is%3Aissue+is%3Aopen+ 14:01:16 agenda+ subgrpu[s https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit#heading=h.plt9g4kok1rb 14:01:50 RRSAgent, publish minutes 14:01:51 I have made the request to generate https://www.w3.org/2023/08/14-coga-minutes.html Lisa 14:01:59 regrets+ EA , Rain, Jennie 14:08:28 agenda 2 = wayfinding (see https://docs.google.com/document/u/0/d/1TDtuC_iMyS_X6nXwyEEAu4Abp2tXHb86/edit 14:17:10 Agenda? 14:54:37 Lisa has joined #coga 14:54:38 agenda? 14:54:55 RRSAgent, publish minutes 14:54:57 I have made the request to generate https://www.w3.org/2023/08/14-coga-minutes.html Lisa 14:59:39 JustineP has joined #coga 14:59:48 Rain has joined #coga 14:59:50 present+ 15:00:32 Eric_hind has joined #coga 15:00:45 Becca_Monteleone has joined #coga 15:00:52 present+ 15:01:21 present+ 15:01:24 present+ 15:01:27 next item 15:01:35 abbey has joined #coga 15:02:03 scribe+ eric, lisa 15:02:06 tburtin has joined #coga 15:02:33 q+ 15:02:46 ack item 15:02:51 ack next 15:04:23 Becca and Eric: Found github training useful. There will be more training tomorrow (and follow up screenreader training after that ). 15:04:53 present+ 15:05:05 julierawe has joined #coga 15:05:09 present+ 15:05:32 I also attended the github training and found it helpful. I will likely join the second call too. 15:05:36 Lisa: Will be doing refresher on COGA processes and documents after main call 15:06:37 q? 15:07:20 agenda? 15:07:33 take up item 4 15:08:33 https://docs.google.com/document/d/1KvEnKdXe30e9BUxcR8RYEOB3PqM7Z9nbLGL8gG-vVW4/edit 15:10:06 eric leading the discussion 15:10:48 ping us in 20 15:12:09 tags are editorial or disscusion in erics docs 15:13:12 are we ok with fixing broken links 15:13:14 +1 15:13:28 +1 15:13:29 +1 15:13:29 +1 15:13:30 +1 15:13:43 and objections 15:13:46 +1 15:13:46 ? 15:13:58 no objections 15:14:17 324: to more ors in a sentence 15:14:48 +1 to requesting bullet pointed list 15:15:01 q+ 15:15:13 +1 to bullet points as well. 15:15:24 editorial without change in meening. such as braking it into a list 15:15:30 ack next 15:16:20 rain: when there is long sentence , many cluses . limit each line to one idea 15:16:55 +1 15:16:58 without changing the content 15:17:14 +1 15:17:19 with a second person cheking ideas and meening is not changed? 15:17:22 +1 15:17:24 +1 15:17:25 +1 15:17:30 any objections? 15:18:21 issue 323 - wrong user need 15:18:21 Sorry, but no Tracker is associated with this channel. 15:22:25 link to task mangment (same user need,) 15:22:34 +1 15:22:35 +1 15:22:36 +1 15:22:36 +1 15:22:38 any objections? 15:22:39 +1 15:22:39 +1 15:22:44 +1 15:22:44 +1 15:27:52 322 user need points to the wrong user need becuse titles are confucing (support, and help) which is which 15:28:13 rain: we need to resucture and come out with clear buckets 15:28:17 q? 15:29:00 but diffrent work streem to what we are doing now in our subgroup 15:30:27 Lisa: Titles at the more granular level can be confusing... we have branched as a way to get changes in before major markups or versions? Alternatively, we could gather up items and forward to newer structures? 15:30:55 rain: yes move forward with editorial changes in erics branch 15:31:40 Rain: Editorial changes will help right now. Given the mapping isn't 1:1, referencing the public version will be a good thing as the most current could be referenced. 15:31:43 lisa: can you tell us when we need to stop editorial changes in a diffrent branch 15:33:08 q? 15:33:08 Lisa: We need to coordinate branching so new structure pulls from the right time and place. 15:34:28 Lisa: Add document marker about decisions (e.g. # of +1s to change somthing in this issue) 15:34:34 +1 15:34:44 +1 15:34:50 +1 15:34:53 +1 15:35:01 +1 15:35:01 are we ok with changing the mapping, and opening a new issue that help and support are confucing titles 15:35:15 (as diffrent user stories) 15:35:23 no objections 15:38:07 +1 15:38:16 Proposed: Change Use Tapered prompts To : Use prompts that adapt with the user’s behavior (Tapered Prompts). 15:38:16 +1 15:38:23 issue 321 15:38:23 Sorry, but no Tracker is associated with this channel. 15:38:29 +1 15:38:38 any objections 15:39:15 320 4.6.2.1 User Need has content from 3.2.2 Searchable (User Story) but link says Distractions (3.5.1). 15:41:11 findable makes more sense to me… 15:41:34 320, might need more work 15:42:51 ds to be researched again and validated. (like search feature - searchable) Also, could review user needs and be sure they’re in the right place.. 15:43:57 319 has simmilar issue 15:44:26 maybe we need a good review of user needs , titles and user stories are clear 15:44:38 +1 15:44:43 q? 15:44:53 q+ 15:45:08 ack next 15:45:17 rain is concerned that we have too much 15:45:51 streched too thin 15:47:30 eric can take that action, lisa may help 15:48:54 318 318 4.5.6.4 More Details include reference to title that is not clear Context of ‘Title’ is not clear. Recommend (per comment) text be changed from “titles” to “title attributes (HTML)” - this seems to match the intended meaning. Change and add reference to HTML 15:49:26 any objections 15:50:46 rain: say html titles and alternitve text 15:50:53 +1 15:50:57 heading too? 15:51:01 +1 15:51:05 +1 15:51:08 +1 15:51:21 +1 15:53:18 +1 15:53:20 +1 15:53:22 317 Section 4 Design Guide Related User Story links are missing number heading (e.g. Clear Operation but should be 3.1.2 Clear Operation) Links are missing number heading Update Section 4. Design guide to include number headings. Proposal : do not add more numbers by created user stories. It is fine without. Send to list in email with a bunch of things that are low level Draft reply to issue Some feedback has been that people find the document is t[CUT] 15:53:28 +1 15:53:32 +1 15:53:33 q? 15:53:33 +1 15:53:35 +1 15:53:38 +1 15:53:40 any objections 15:54:12 can eric fix clear typos 15:54:14 +1 15:54:16 +1 15:54:17 +1 15:54:19 +1 15:54:22 +1 15:54:24 +1 and a thank you! 15:54:28 +1 15:55:18 306 Use Github action instead of Travis CI - we feel this is not our issue 15:55:23 any objections? 15:56:23 clear editoral issues like sentences repepted 15:56:33 can eric just remove it? 15:56:34 +1 15:56:40 +1 with someone double checking 15:57:13 things that are aleready adressed -can we say thank you and close it ? 15:57:17 +1 15:57:19 +1 15:57:21 +1 15:57:21 +1 15:57:23 +1 15:58:26 305 Underserved users described as “High Potential” 15:58:37 Julieawr mentioned that High Potential might be best replaced. Open discussion item as not clear if high potential infers high value to a business (e.g. CEO) or a m 15:58:45 q+ 15:59:02 defining it may be a can of worms 15:59:40 what we want to say, people who are stugling with increadible potential 16:00:47 q? 16:00:47 Instead of "high potential" could we instead simply use "users"? 16:00:59 ack Rain 16:01:02 ack next 16:01:24 Thanks, everyone! 16:01:57 RRSAgent, publish minutes 16:01:58 I have made the request to generate https://www.w3.org/2023/08/14-coga-minutes.html Lisa 16:40:27 https://www.w3.org/WAI/GL/task-forces/coga/wiki/Main_Page