13:02:08 RRSAgent has joined #a11y-functional 13:02:08 logging to https://www.w3.org/2022/05/17-a11y-functional-irc 13:02:19 present+ 13:02:27 present+ JakeAbma, ToddL 13:03:17 Joshue108_ has joined #a11y-functional 13:03:23 present+ Josh 13:03:35 meeting: Accessibility Functional Needs 13:03:39 rrsagent, make log world 13:03:53 agenda: https://lists.w3.org/Archives/Public/public-a11y-functional-needs/2022May/0011.html 13:03:57 chair: Josh 13:04:25 scribe: ToddL 13:04:46 Joshue108: Feedback on COGA call. Any thoughhts? 13:05:06 Joshue108_: How we felt it went, was it useful? 13:05:47 JakeAbma: Always useful. Felt like they thought they had something else than us, I don't think that's the case. We're not that far apart. 13:06:16 JakeAbma: Would be good for them to give feedback on FN list 13:10:26 Joshue108_: Usefule, constructive meeting, and open to their ideas and input. 13:10:35 Scope has to be managed. 13:16:30 Not this one? https://www.w3.org/TR/coga-usable/ 13:18:20 https://www.w3.org/WAI/WCAG2/supplemental/#cognitiveaccessibilityguidance 13:18:22 https://w3c.github.io/coga/user-research/ 13:19:39 JOC: I really like this https://www.w3.org/WAI/WCAG2/supplemental/#cognitiveaccessibilityguidance 13:19:52 Useful, clear, terse 13:22:58 + 1 to using this - nice way of adding these COGA requirements into our Matrix 13:26:32 Have to step away for a minute 13:27:52 13:28:05 JOC: Next steps on COGA 13:29:12 JOC: Lets invote COGA again in a month, Josh to reach out to Rain and Lisa and we can discuss approaches to using the Suppl guidance doc 13:30:33 JOC: I thought it would be interesting to hear their perspective on our Deceptive Patterns work 13:30:44 We can add that our agenda for next time. 13:30:55 TOPIC: Review of Jeanne and Mary Jo's feedback 13:31:15 Review of Jeanne and Mary Jo's feedback 13:31:23 https://docs.google.com/document/d/16ZeCqTRTY0lmWvp1Xv_wO0iH1OzyECBa1UXQ_UeocjQ/edit#heading=h.4jiwp8jpc143 13:31:33 They've added comments on our doc- lets discuss 13:31:43 Main Functional Needs - Main User Needs - Main Outcomes 13:32:14 Joshue108_: Walking through wwhat Jeanne and Mary Jo left in their feedback 13:34:46 Joshue108_: Can walk through comments left in the doc 13:37:53 13:38:21 JakeAbma: Big problem with intersections 13:38:48 Josh, I missed that, I've got fires at work I'm trying to contain 13:40:10 MC: Safety is a general user need and not a functional need as such 13:40:19 Thanks Josh. 13:40:20 We could on that basis remove 13:40:45 JA: I have an issue with some of these intersections - we should review 13:41:12 MC: Discussion of user needs for Deafblind 13:41:55 JA: Some blind users may not know braille- or have their needs covered in other places 13:42:25 JA: There are potentially endless amounts of intersection, so we have to be careful 13:42:41 MC: Right, we should not create intersections because we can 13:42:51 I'm inclined to be minimal 13:43:18 MC: Lets keep it simple, if we can avoid some intersectional joinings 13:43:34 JOC: It's an issue of coverage 13:44:09 So the question is do we still need this "Essential Use without physical harm or risk (to self or others within a physical environment)" 13:44:33 MC: We should bring Charles back in. 13:44:40 JOC: Do know harm *grin 13:44:47 I think it was XR related 13:45:23 MC: What about multiple disabilities? 13:45:34 JOC: Right, and competing user needs. 13:47:16 JA: In this case - we should ask people to prove something is an issue, or the requirements of the intersection doesn't work 13:47:38 This would be a trigger to see if it is something that we should actually document 13:47:42 MC: Makes sense 13:48:07 MC: So not abandoning the possibility of an intersection but expecting them to be exceptional 13:51:01 JOC: I'll ping Charles and see where he is at 13:53:42 13:55:50 JA: This could already be covered by the existing functional need - on memory etc 14:03:51 rrsagent, draft minutes 14:03:51 I have made the request to generate https://www.w3.org/2022/05/17-a11y-functional-minutes.html Joshue108_ 14:04:03 rrsagent, make logs world