13:51:40 RRSAgent has joined #COGA 13:51:40 logging to https://www.w3.org/2019/09/12-COGA-irc 13:51:42 RRSAgent, make logs 389 13:51:45 Meeting: Cognitive Accessibility Task Force Teleconference 13:51:45 Date: 12 September 2019 13:52:01 agenda+ action items 13:52:52 agenda- 13:53:05 zakim takeup next item 13:53:49 zakim, take up item 1 13:53:49 agendum 1. "actions - see https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Actions" taken up [from LisaSeemanKest] 13:54:01 zakim, take up item 2 13:54:01 agendum 2. "priorities at https://docs.google.com/spreadsheets/d/1YH4YETBmAdhfL9p8FK5ATUiXDGibeJh66psQCSUAvLQ/edit#gid=0" taken up [from LisaSeemanKest] 13:54:11 zakim, take up item 3 13:54:11 agendum 3. "editing update at https://docs.google.com/spreadsheets/d/1Rt51xg57oZW56mfTw_t33T9zlPDOV7o4Za6veCCqDtI/edit#gid=0" taken up [from LisaSeemanKest] 13:54:15 zakim, take up item 4 13:54:15 agendum 4. "silver feedback https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2019Sep/0010.html" taken up [from LisaSeemanKest] 13:54:19 zakim, take up item 6 13:54:19 agendum 6. "action items" taken up [from Rachael] 13:54:23 zakim, take up item 5 13:54:23 agendum 5. "persona todo list : https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Persona_to_do_list" taken up [from LisaSeemanKest] 13:55:39 LisaSeemanKest_ has joined #coga 13:55:49 agenda+ action items 13:56:04 agenda+ Review github feedback and responses (Steve) 13:56:15 agenda+ Mental Health Paper 13:56:33 agenda+ WCAG 2.2 SC Check In 13:56:49 agenda + Finalize silver response 13:56:56 agenda+ EU Review 13:57:15 agenda+ Working Group Note 13:59:09 Jennie has joined #coga 14:00:51 present+ 14:01:48 present+ 14:03:21 regrets+ John Kirkwood 14:03:36 regrets+ Abi 14:03:40 regrets+ EA 14:04:34 Justine has joined #coga 14:05:47 agenda? 14:07:16 scribe: Jennie 14:07:26 zakim, takeup item 8 14:07:26 I don't understand 'takeup item 8', Rachael 14:07:37 Steve: everyone once in a while COGA gets a Github message that there is a message which requires a response. 14:07:43 zakim, take up item 8 14:07:43 agendum 8. "Review github feedback and responses (Steve)" taken up [from Rachael] 14:07:59 Steve: I will monitor this, and add important discussion pieces to the list and bring it up in meetings. 14:08:08 Steve: e.g. 1 was about a missing link. 14:08:28 Steve: we should not just remove URLs, and we will in the future be careful how we do that. 14:08:30 q+ 14:08:42 ack f 14:08:56 ack lis 14:09:08 Lisa: I think the response of the issue should go through the task force. 14:09:28 ...then people can say "hang on, I'm not ok with that." Especially when you get rid of a URI 14:09:34 ...the old URI needs a note. 14:09:46 Steve: that's what I asked Roy to do. 14:09:54 Lisa: it should say this has been moved to here. 14:09:59 Steve: Has he done that? 14:10:23 Lisa: I don't know. Then the response can just be "Thanks for pointing that out. We have followed up." 14:10:50 ...and in general I think it is better that whoever is doing the issues, it is a 2 second discussion, indicating which ones you want to answer and how 14:11:05 Steve: How long should I wait? 14:11:12 Lisa: it depends on the issue. 14:11:31 Lisa: It depends on what you have put as the title, which helps me understand if I need to read it in depth. 14:12:13 Lisa: If you are writing an issue to the list, maybe that is how we want to handle it. And Rachael and I should decide if they get closed. 14:12:21 Rachael: is everyone else comfortable with this? 14:12:24 +1 14:12:48 Steve: I created a work flows page, and can add this to the work flow. 14:13:06 Lisa: I didn't know there is a work flow page. 14:13:32 Steve: I always state that I have created them, so I'm not sure what has gone wrong. I post it on the list. 14:13:43 Rachael: maybe this can be an issue for the planning call? 14:13:45 Lisa: yes please. 14:14:11 Rachael: Sounds like we will post the issue to the list, bring it up in the meeting once, and then close the issue. 14:14:17 Lisa: that sounds good. 14:14:25 Steve: what about when something can be resolved on the list? 14:14:33 Lisa: I think it is better to bring it up on the call. 14:14:55 Rachael: I think it can be part of the actions so people are aware. It doesn't have to be a detailed review - just a "heads up." 14:14:59 Lisa: I agree. 14:15:12 +1 14:15:19 Justine: that sounds reasonable. 14:15:27 Steve: it would nice to have people be more engaged. 14:16:12 zakim, take up item 9 14:16:12 agendum 9. "Mental Health Paper" taken up [from Rachael] 14:16:13 Rachael: item 9 - none of those people are here. 14:16:36 Lisa: Thadeus worked on this in the past, and he added some comments. 14:16:50 Lisa: is there anyone else we want to reach out to, like Renaldo? 14:17:06 https://www.w3.org/WAI/GL/task-forces/coga/wiki/Workflows 14:17:15 Lisa: I can take the action to reach out to those who have been involved. 14:17:24 zakim, take up item 10 14:17:24 agendum 10. "WCAG 2.2 SC Check In" taken up [from Rachael] 14:17:34 https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit#gid=0 14:17:50 Rachael: we are doing very well, in my opinion. We are in second drafts on most of these. 14:18:22 ...we have a 1st draft on the no memorization, but there was a conversation about this at the AG meeting. 14:18:56 jennie: At the AG meeting (which had technical difficulties dropping people) they asked for a reference to research on cognitive fatigue. 14:19:28 ...they were discussing the SC on do not rely on user memory. One member asked if there was reserach on the phrase about mental fatique. They would like 1-2 studies referenced to back up the statement 14:19:34 q+ 14:19:53 https://www.w3.org/TR/coga-usable/#pattern-do-not-rely-on-users-memorizing-information 14:19:58 ack LisaSeemanKest_ 14:20:13 Lisa: we had things like with Dyslexia, your skills decrease as you get more tired. 14:20:16 +1 14:20:49 *that +1 was accidental 14:20:52 q+ 14:21:01 q+ 14:21:02 https://docs.google.com/document/d/1e46eqQnVYqdSyqo29pyJoY1QynRH9v95YW8soTTbfsU/edit 14:21:31 ack justine 14:21:43 Justine: I was reviewing the SCs 14:22:08 ...the part I was questioning in particular where it says "stress blocks the brain..." 14:22:30 Rachael: it is a plain english summary from the SC 14:22:45 Rachael: David wrote this, and we can ask him to clarify. 14:22:49 q? 14:24:03 Lisa: I'm not sure why this is here. 14:24:19 ...it does not seem to be related to cognitive disabilities. 14:24:27 Rachael: it may be worth you reviewing this SC. 14:24:39 ...I was going to set up a meeting for you, me and David. 14:24:41 Lisa: yes. 14:25:15 ...he might be getting at is in brain injury when people are relearning mental skills, so they may not be able to do. 14:25:29 ack Jennie 14:26:35 jennie: I did previous research on cognitive load and stress. I wonder if David is trying to demonstrate that in certain situations with hard forms it can increase the issue that the person has. I wonder if this needs rephrasing. 14:26:49 q? 14:26:51 *looks great! 14:27:14 Rachael: I'm going to set up a meeting with Lisa, Rachael, Jennie, David 14:27:31 ...we can look at the wording and see if we can adjust it to meet the concerns. 14:27:44 ...I don't think any of the SCs proposed are in danger of being cut. 14:27:46 q+ 14:27:53 ack Jennie 14:28:41 can u put a link in the channel 14:29:21 q? 14:29:37 https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1fX4Iw169OGUny5RTd70S8qAneYy5e0hr7zupE21gPBM%2Fedit&data=02%7C01%7Cjennie.delisi%40state.mn.us%7Cb5ad966c913147defe8908d73565dfe9%7Ceb14b04624c445198f26b89c2159828c%7C0%7C0%7C637036583984543636&sdata=1ARIsxAY8PTPnGgIT9p18b83zgKK%2FD4VW5mo47AuiOY%3D&reserved=0 14:30:27 Steve and I worked on updating the SC for Findable Help, and removed some language that we knew would not pass. 14:30:42 We need the group to review, and give feedback. If by end of Sunday, that would be great. 14:30:48 Rachael: I can review 14:31:02 ...we will put out a note by end of day on Sunday. 14:31:58 q+ 14:32:05 Lisa: what was removed? 14:32:15 Jennie: the location 14:32:31 Rachael: what we did with ours was to add an either or 14:32:44 ...location on the page, or personalization. 14:32:51 ...I met with Alastair on this, and John Folio 14:33:14 ...personalization should have a draft out, and a secondary spec does something similar. 14:33:15 q+ 14:33:21 ack Rachael 14:33:25 ack Rachael 14:33:41 Lisa: what is the date for this? There is actually only module 1. 14:33:59 Rachael: the current schedule worked - there was enough information to use it for the SC 14:34:06 q+ 14:34:06 ...it was tight, but it was ok. 14:34:25 Lisa: what is exactly needed? I think we have consensus on those modules. 14:34:38 Rachael: for us it was marking the importance. 14:34:48 ...for Jennie it would be location. 14:34:57 ...John Folio is aware. 14:35:03 q? 14:35:05 ack Jennie 14:35:46 Jennie: Feedback from EA was interesting. Why I'm hoping more people will comment. There are other user groups who have identified other locations. Screen reader users are used to finding help in the footer. 14:35:57 ...EA's point is that there is a standard practice in use that this would disrupt. 14:36:59 q+ 14:36:59 ...if we go to the root of this, the intent is that it is reliable. That reliable would be something most people would find. Taking the risk of personalization. If that becomes what stops this from being passed, would we be better going for the intent that help is findable? 14:37:00 ack stevelee 14:37:03 Steve: I think EA is correct, that contact is typically in the footer 14:37:18 ...I think we state following existing patterns. 14:37:46 ...this may apply to the other SC as well. If there is an explicit standard/pattern, we don't want to tell people advice that stops them from doing that 14:38:02 q+ 14:38:10 q? 14:38:11 Lisa: how about something like "on every page help can be programatically determined or as it at the top of every page." 14:38:21 Steve: that then breaks it 14:38:41 ack LisaSeemanKest_ 14:38:52 q? 14:39:04 q+ Rachael 14:39:06 Lisa: in general, you never get it ever at the extent that you want it, so getting it in at all is fantastic. 14:39:43 ...you can put a lot in the advisory, and if you are using testing, always test that people can find the help and use it properly, but that can't be in the SC. Having something in is a really good hook. 14:39:59 ...don't feel too bad if you get it into the SC. 14:40:10 Steve: we did clarify the types of help. 14:40:24 Lisa: WCAG 1.0 got criticized for being too vague. 14:40:54 Steve: you showed me SCs that said context help is available, but this would provide more information. 14:41:04 Lisa: there is the understanding section, so people read this. 14:41:23 ...even just ask someone you know with forgetfulness to see if they can find the help. 14:41:32 ack Justine 14:41:41 steve here is wcag 1.0 https://www.w3.org/TR/WAI-WEBCONTENT/ 14:42:26 Justine: a related comment is that we might want to consider an essential exception. Examples like testing - how to respond when accessing the help during timed questions may need to be addressed. 14:42:29 +1 14:42:53 Lisa: can you explain more? 14:43:49 Justine: in the example of standardized assessment, a student with a cognitive disability may have an accommodation like extra time; and if the timing of the assessment negatively gets impacted by them accessing the help 14:43:56 q? 14:44:01 q- 14:44:04 Lisa: I don't think that will be a factor 14:44:06 q+ 14:44:17 *I just lost connection 14:44:19 q+ stevelee 14:45:01 lisa: I wondering why we should say. There are a lot of shortcuts. you don't have to access it but its available. 14:45:15 *I'm back 14:45:17 Justine: the help might be avaible through another mechanism like labeled buttons. 14:45:52 Lisa: I know that this example you want to is not a requirement, you don't have to use the help. 14:46:27 Lisa: this one is often where people use but people who need the help often can't find it. 14:46:57 ...they have an online option for practicing sometimes but this may not enable them to practice with their AT 14:47:06 ...and people do worse because of it. 14:47:37 ...FAQs, for example. 14:47:46 q? 14:47:51 ack Jennie 14:49:12 Jennie: I had +1 to Justine's comment but Lisa makes a good point. How to use the interface causes problems here. I wonder if we need to go back to the standards document but then usability testing needs to occur. 14:49:44 stevelee: Justine had suggested help buttons but does context specific help address that? 14:50:09 Jennie: It is different. 14:50:44 Justine: there seems to be an overlap here, between the context specific help. We may be able achieve some of this the same way. 14:51:04 Steve: I think this is when a person is stuck beyond what they can find in that context specific help. 14:51:05 q? 14:51:13 ...not how you use the user interface. 14:51:18 ack stevelee 14:51:19 q+ 14:52:09 steve: How long do we give the group to respond? 14:52:23 Jennie: It sounds like we'll give it to Sunday and then review it Monday. 14:52:35 ..I think we agreed that would be ok. 14:52:46 Lisa: Ask for an agenda item in the call when you need review. 14:52:57 ..and tell us it needs to be this week. 14:53:28 ack LisaSeemanKest_ 14:54:11 Lisa: I had something that I wanted to note: I would love it if it would say instead of just human contact details, details that take you directly to a human, self help option, 14:54:13 q+ 14:54:32 Steve: what do you mean direct? A telephone number that would go directly to a person? 14:54:52 Lisa: like a telephone system that goes into a menuing system 14:55:11 Steve: we have an item about chat bots 14:55:22 ack Jennie 14:55:26 Lisa: but I am referring more to another system 14:56:28 Jennie: Concern it will be difficult to implement and the phone system is out of scope 14:56:57 Lisa: Can we add it to the understanding document. 14:57:14 Jennie: Please provide more comments through any mechanism 14:57:43 Zakim take up item 12 14:57:49 zakim, takeup item 12 14:57:49 I don't understand 'takeup item 12', Rachael 14:57:58 Lisa: I sent an email to the list about what the EU commission wants to fund as research and innovation projects. 14:58:02 ...I can make suggestions 14:58:06 zakim, take up item 12 14:58:06 agendum 12. "EU Review" taken up [from Rachael] 14:58:18 ...we should think: if this got funded, this could make a huge difference to us. 14:58:25 laura has joined #coga 14:58:31 ...we wouldn't personally get the funding, but a university somewhere would fund it. 14:58:58 ...if there are automatic testing tools for this, authoring tools, it is that much more likely that it would go through the WCAG process. 14:59:13 ...we would be in a stronger position to get through WCAG process next time. 14:59:19 q+ 14:59:21 ...are there other things like this that people feel we need. 14:59:30 ack Rachael 14:59:33 Rachael: are you including personalization, tools that take advantage of it? 14:59:37 Lisa: yes. 14:59:40 q? 14:59:54 Lisa: that is unlikely to get in because it was funded by the Easy Reading project. 15:00:04 Rachael: we will wrap this up. 15:00:12 Lisa: comments on the list would be great. 15:00:39 Rachael: I will have a hard time making the editors meeting - shall we cancel? 15:01:00 * I have to sign off - can someone else wrap up the minutes? 15:01:34 Steve: Action update, working on the divs 15:04:07 rrsagent, make log world 15:04:26 rrsagent, generate minutes 15:04:26 I have made the request to generate https://www.w3.org/2019/09/12-COGA-minutes.html Rachael 15:04:39 trackbot end meeting 15:04:39 Zakim, list attendees 15:04:39 As of this point the attendees have been Fazio, stevelee_, Rachael, Jennie, stevelee 15:04:47 RRSAgent, please draft minutes 15:04:47 I have made the request to generate https://www.w3.org/2019/09/12-COGA-minutes.html trackbot 15:04:48 RRSAgent, bye 15:04:48 I see no action items