14:51:47 RRSAgent has joined #wcag2ict 14:51:51 logging to https://www.w3.org/2023/01/26-wcag2ict-irc 14:51:51 RRSAgent, make logs Public 14:51:52 please title this meeting ("meeting: ..."), maryjom 14:51:58 zakim, clear agenda 14:51:58 agenda cleared 14:52:05 chair: Mary Jo Mueller 14:52:11 meeting: WCAG2ICT Task Force Teleconference 14:52:17 Zakim, please time speakers at 2 minutes 14:52:18 ok, maryjom 14:52:24 Agenda+ Announcements 14:52:31 Agenda+ Standup for self-assigned work 14:52:40 Agenda+ Survey: Readiness of SC 2.1.4 proposal to incorporate into editor's draft 14:53:04 zakim, clear agenda 14:53:04 agenda cleared 14:53:16 agenda ? 14:53:21 Agenda+ Announcements 14:53:28 Agenda+ Standup for self-assigned work 14:53:38 Agenda+ Survey: Readiness of Background section proposal to incorporate into editor's draft 14:53:45 Agenda+ Survey: Readiness of SC 2.1.4 proposal to incorporate into editor's draft 14:54:00 LauraBMiller has joined #WCAG2ICT 14:54:34 present+ 14:55:39 regrets: Anastasia Lanz 14:56:55 present+ 14:58:08 present+ 14:58:23 ThorstenKatzmann has joined #wcag2ict 15:00:35 bruce_bailey has joined #wcag2ict 15:00:37 Chuck has joined #wcag2ict 15:00:37 GreggVan has joined #WCAG2ICT 15:00:43 present+ 15:00:43 present+ 15:00:47 present+ 15:00:53 present+ 15:01:08 agenda? 15:01:16 ShawnT has joined #wcag2ict 15:01:29 Mike_Pluke has joined #wcag2ict 15:02:07 BryanTrogdon has joined #wcag2ict 15:02:40 Devanshu has joined #wcag2ict 15:02:40 scribe: dmontalvo 15:02:40 present+ 15:02:40 present+ 15:02:40 zakim, take up next 15:02:40 agendum 1 -- Announcements -- taken up [from maryjom] 15:02:40 present+ 15:03:08 present+ 15:03:25 MJ: Lot of SCs starting to come through. Next couple of weeks we will continue to work on some more before sending them to AGWG for review 15:03:45 ... There is still some code issues after our markdown migration that I hope we can get fixed before sending anything to AGWG 15:04:25 ... We do want to split the document into smaller chunks 15:04:27 present+ 15:04:28 zakim, take up next 15:04:28 agendum 2 -- Standup for self-assigned work -- taken up [from maryjom] 15:04:37 Sam has joined #wcag2ict 15:05:34 MJ: Working on the definitions, I will create a PR 15:05:43 present+ 15:06:09 ... There are two of the definitions that weshould ddiscuss as they are very web-based. There is also a more technical discussion. We'll have these discussions in a future meeting 15:06:20 ... Also some work on motion actuation with Sam 15:06:42 ... Loíc has an update that we will be discussing next week probably 15:08:09 Laura: We should probably discuss target size as well 15:08:09 ... The note says something about "distance from" not sure if that was added or was part of the original SC 15:08:40 MJ: This is still in the "in progress" category, so let's figure out once he is available. Let's make sure nobody is blocked now 15:09:21 MJ: Bruce, you have assigned yourself 2.5.1 15:09:46 Bruce: Not much progress yet. I am also working on the Understanding Document for AGWG 15:10:12 q+ for pointer size URL 15:10:47 Bruce: Could someone paste the URL for the target size discussion? 15:10:53 ack br 15:10:53 bruce_bailey, you wanted to discuss pointer size URL 15:10:57 https://github.com/w3c/wcag2ict/issues/80 15:11:17 zakim, take up next 15:11:17 agendum 3 -- Survey: Readiness of Background section proposal to incorporate into editor's draft -- taken up [from maryjom] 15:11:36 https://www.w3.org/2002/09/wbs/55145/WCAG2ICTBackground/results 15:12:19 MJ: 10 people responded to this. Thank you all. 15:12:54 ... We had a few people saying it is fine as-is and other that had some editorial comments 15:13:23 Chuck has joined #wcag2ict 15:13:23 ... I will start with Phil's and Chris' comments about broken markdown links 15:13:52 ... We are using Respec to generate the document 15:14:09 ... Daniel fixed an issue and these references should now be working on the editor's draft 15:14:46 I believe Micheal had a bookmarklet on his computer 15:15:00 DM: Will have a look at how to genearte a preview for each PR later 15:16:02 MJ: I had some other comment, no need to discuss these. Bruce and others indicated that they agree with my comments 15:16:19 ... Mike was a bit concerned about the "guidance" section 15:16:52 ... He suggest that strong warning as well there 15:16:56 q+ 15:16:59 +1 to Mike's proposal 15:16:59 +1 for surfacing mikes concern 15:17:01 ack gregg 15:17:33 Greg: One is that it does apply. ANother is that it rarely occurs 15:17:41 q+ 15:18:11 ... It is important because that confuses a lot of people who may think that if it rarely occurs it may mean it does not apply 15:18:46 ... For example in WCAG someone could think of a theoretical issue, but that does not mean we need to necessarily include a SC for it if it does not create real problems 15:19:29 ack Mike_Pluke 15:19:51 Mike: Hopefully adding the note conveys what you were saying, Greg 15:20:11 q+ 15:20:31 MJ: We already have text on the SCs were it does occur 15:20:50 ... Sometimes we say "set of documents" or "set of programs" 15:20:58 ... Would it be better to use that exact language? 15:21:03 \Greg: From last time? 15:21:05 MJ: Yes. 15:21:05 q+ to ask if "scope" or distinction between "applicable in theory" and "does apply" 15:21:16 ack maryjom 15:21:40 On SC where this is used: See set of documents and set of software programs in the Key Terms section of the Introduction to determine when a group of documents or pieces of software is considered a set for this success criterion. (Sets of software that meet this definition appear to be extremely rare.) 15:21:49 Greg: Sometimes it applys to documents but not to software. We need to think about each one, but using similar language or finding a way so that it is easier to understand would be good 15:22:04 ack Mike_Pluke 15:22:06 ack m 15:22:24 Mike: Not sure what the other text says 15:22:43 ack bruce_bailey 15:22:43 bruce_bailey, you wanted to ask if "scope" or distinction between "applicable in theory" and "does apply" 15:22:45 s/set of programs/set of software programs/ 15:23:08 Bruce: We get a similar dilemma for 508 15:23:49 ... Difficult to distinguish between "in scope" and "how frequent it occurs" 15:24:09 ... Trying to figure out the nuance wasn't worth the bandwidth 15:24:24 MJ: Is there anyone who is against adding something? 15:24:39 +1 to add something about set of software in "guidance" section. 15:24:40 Greg: It should not be in the background section 15:24:53 MJ: It will be in the "guidance" section 15:25:11 +1 to working it into the guidance section 15:25:32 MJ: Not hearing opposition, I will open an issue to address this. 15:25:45 Greg: It will help if we put the actual phrasing in the survey 15:25:48 MJ: We will 15:25:55 ... Good that it got brought up 15:26:47 MJ: Olyvia asks if there is some other place were we could link to the definition of normative 15:26:55 ... There is a definition in WCAG, so we could point to it 15:27:15 Greg: There are some numbers that we should probably revisit 15:27:23 MJ: Probably all of those details are not necessary 15:27:30 good catch on the numbers 15:27:43 Greg: IT is very helpful because soome people may think most of them don't apply but they really do 15:27:57 MJ: Those are part of the sections that Chris is going to be looking at 15:28:32 https://github.com/orgs/w3c/projects/13/views/2?filterQuery=assignee%3AChrisLoiselle is what I'm assigned, if that is helpful. 15:28:36 MJ: The guidance part was not new. Only the background was. 15:28:55 We have many ambitious participants! 15:28:55 Greg: Thank you, we should be looking at these two new paragraphs only for now. 15:30:16 FYI, definition to normative: https://www.w3.org/TR/WCAG21/#dfn-normative 15:30:35 Draft RESOLUTION: Incorporate the background section with the edits noted in the survey by Mary Jo and Olivia. 15:31:03 s/Olyvia/Olivia/ 15:31:31 +1 15:31:34 +1 15:31:36 +1 15:31:36 +1 15:31:37 +1 15:31:38 +1 15:31:41 +1 15:31:41 +1 15:31:44 +1 15:31:44 +1 15:31:44 +1 15:31:46 Daniel: +1 15:31:47 +1 15:31:55 RESOLUTION: Incorporate the background section with the edits noted in the survey by Mary Jo and Olivia. 15:32:20 zakim, take up next 15:32:21 agendum 4 -- Survey: Readiness of SC 2.1.4 proposal to incorporate into editor's draft -- taken up [from maryjom] 15:32:36 https://www.w3.org/2002/09/wbs/55145/WCAG2ICTCharKeyShortcuts/results 15:32:48 https://github.com/w3c/wcag2ict/issues/76#issue-1492528086 15:33:20 Minutes from last week 15:33:21 ttps://www.w3.org/2023/01/19-wcag2ict-minutes#t04 15:33:31 https://www.w3.org/2023/01/19-wcag2ict-minutes#t04 15:33:50 I can. 15:33:56 scribe: ChrisLoiselle 15:34:28 MaryJo : On notes, note 1, specifically timing. Sam had a reference on long keypress. 15:35:16 ... non character key or modifiers were discussed. Is the long key press in closed products or in native products? What is definition of keyboard shortcut? 15:35:23 Definition: keyboard shortcut alternative means of triggering an action by the pressing of one or more keys 15:36:00 MaryJo : suggested about closed products . 15:36:19 Votes to include as is, some comments on note 1. 15:36:33 Gregg: Can you refresh the page for survey? 15:37:12 scribe+ daniel-montalvo 15:37:46 MJ: Laura suggested "keyboard interface" instead of "keyboard" 15:37:52 ... In the SC is says "keyboard" 15:38:13 Laura: The word "keyboard" brings to mind a QWERTY keyboard 15:39:14 MJ: It is "keyboard shortcut" indeed. 15:39:17 Laura: OK. 15:39:58 MJ: Phil asks how to meet on a system with long presses or keystrokes 15:40:36 MJ: Mike wants to remove the first note 15:40:48 .. Greg says "shall" need to be changed to "should" 15:41:19 q+ 15:41:21 Greg: Are we removing the first note? We are supposed to be saying that "shall" is normative language, but notes are informative. We should not have "shall" in them 15:41:38 ... We are supposed to be talking about how it does or does not apply, instead of modifying what the SC says 15:42:06 q? 15:42:11 ... IF we remove it, the problems goes away entirely, but we should talk about that 15:42:12 ack ChrisLoiselle 15:42:15 ack Chuck 15:43:11 q+ 15:43:12 Chuck: Along the lines of what Greg said, when I read the notes I interpret "meet the SC" as "pass the SC". The intent should be for the SC to be applicable, not necessarily to pass or fail. 15:43:17 q+ 15:43:27 +1 to Chucks concern for "meet" versus "pass" 15:43:27 q+ to say that q+ 15:43:28 ack sam 15:43:58 Sam: There is modifier keys and there also a requirement for key repeat. That is where it came from 15:44:14 ... Another approach would be to qualify the note 15:44:32 ack maryjom 15:44:32 q+ to ask a clarifying quesiton 15:45:04 glossary term: https://www.w3.org/2002/09/wbs/55145/WCAG2ICTCharKeyShortcuts/results 15:45:12 MJ: There aer other places in WCAG2ICT where we say similar things. I would have to double check 15:45:34 ack GreggVan 15:45:34 GreggVan, you wanted to say that q+ 15:45:35 q+ to suggest that maybe what we need is to solve issues by revising the definition of "keyboard shortcut" 15:46:16 q+ 15:46:24 Greg: We have a note that is a little bit redundant 15:46:28 q+ to say adding additional ways to satisfy a SC in note seems problematic 15:46:35 ... The second note we can get rid of 15:47:10 Sorry, glossary term is: https://www.w3.org/TR/WCAG22/#dfn-satisfies 15:47:41 "the success criterion does not evaluate to 'false' when applied to the page" 15:47:41 ... The second note can be something like "keys that fare held for more than 2 seconds are not keyboard shortcuts" 15:48:25 ack Chuck 15:48:25 Chuck, you wanted to ask a clarifying quesiton 15:48:28 ... or "they apply as long as the keys don't have to be pressed for more than 2 seconds" 15:49:02 +1 to Gregg's point and Daniel's suggestion 15:49:14 ack Sam 15:49:16 Chuck: Agree for note 2. Regarding note 1, is it the intent that if there is a 2 second period that actually pass or it means that is a different mechanism? 15:49:45 Sam: It was the intent for an alternative way instead of turning it off entirely. But I like Greg's suggestion 15:50:16 q+ to say "this applies with xxxxx replacing xxx as long as keys that are held down for 2 seconds or more before activation are not considered keyboard shortcuts. 15:50:29 ack loicmn 15:50:29 loicmn, you wanted to suggest that maybe what we need is to solve issues by revising the definition of "keyboard shortcut" 15:50:38 .. For note 2, its intent was more specific in the sense that you ahve specific modes where keyboard shortcuts may behave differently 15:51:03 ack bruce 15:51:03 bruce_bailey, you wanted to say adding additional ways to satisfy a SC in note seems problematic 15:51:15 Loíc: We can accept this SC as-is and come back to it later on 15:51:32 q+ to say "this applies with xxxxx replacing xxx as long as the definition of keybaord shortcut does not include keys that are held down for 2 seconds or more before activation" 15:51:38 ack GreggVan 15:51:38 GreggVan, you wanted to say "this applies with xxxxx replacing xxx as long as keys that are held down for 2 seconds or more before activation are not considered keyboard 15:51:41 ... shortcuts. and to say "this applies with xxxxx replacing xxx as long as the definition of keybaord shortcut does not include keys that are held down for 2 seconds or more 15:51:41 ... before activation" 15:51:51 Bruce: I think it is better to address based on the current definitions rather than searching for alternative ways 15:52:32 Greg: We could say "This applies [...] as long as the definition of shortcut does not include keystrokes that have to be pressed for more than 2 seconds" 15:52:59 ... I think it is useful to have the note so that it points people to the actual definition 15:53:22 +1 for note highlighting need to look at definition for keyboard shortcut 15:54:24 ... Do we need to highlight the scenario where all keyboard shortcuts can be turned off? 15:54:50 q+ 15:54:57 ack GreggVan 15:55:00 Sam: We meant you don't have to have a mechanism for each of the shortcuts, you could have one for all 15:55:58 Greg: We could add that the Task Force interpreted the first bullet as if there does not need to be one mechanism for each of the keyboard shortcuts 15:56:17 Poll: Clarify second note that individual or all at once turning off satisfies..., add Gregg's proposed note regarding definition and address in the definition of keyboard shortcuts. 15:56:28 I have hard stop at top of hour. 15:57:26 -1 to note in turning off all at one (no need, it is not specific to non-web) 15:57:33 + 1 to Gregg's "reminder" 15:57:34 "NOTE: The task force interpreted that the turn off option included both turning off an individual shortcut or a mechanism that turned them all off. 15:57:36 +1 15:57:56 +0 to first, +1 to second 15:58:00 -1 15:58:11 +1 15:58:12 I think this is going to require more conversation in a subsequent call. 15:58:19 -1 15:58:29 +0 15:58:42 MJ: We can work on some proposed language and discuss next week 15:58:58 https://github.com/w3c/wcag2ict/issues/76 15:59:02 rrsagent, make minutes v1 15:59:04 I have made the request to generate https://www.w3.org/2023/01/26-wcag2ict-minutes.html daniel-montalvo 15:59:44 present+ 15:59:44 thank you 15:59:46 Thank you 16:23:05 Regrets+: Phil Day 16:23:11 rrsagent, make minutes 16:23:12 I have made the request to generate https://www.w3.org/2023/01/26-wcag2ict-minutes.html maryjom