12:31:01 RRSAgent has joined #matf 12:31:05 logging to https://www.w3.org/2024/09/18-matf-irc 12:31:05 RRSAgent, make logs Public 12:31:06 please title this meeting ("meeting: ..."), Joe_Humbert 12:31:32 Zakim, this is MATF 18 September 2024 12:31:32 got it, Joe_Humbert 12:31:49 Meeting: MATF 18 September 2024 12:31:58 present+ 12:32:26 regrets+ Gleidson Ramos 12:33:42 agenda+ 2.5.4 - Motion Actuation 12:34:04 agenda+ Review 2nd round of voting on SCs that required little or no modification from WCAG2ICT 12:34:26 agenda+ 2.4.11 - Focus Not Obscured (Minimum) 12:35:12 zakim, agenda? 12:35:12 I see 3 items remaining on the agenda: 12:35:12 1. 2.5.4 - Motion Actuation [from Joe_Humbert] 12:35:12 2. Review 2nd round of voting on SCs that required little or no modification from WCAG2ICT [from Joe_Humbert] 12:35:12 3. 2.4.11 - Focus Not Obscured (Minimum) [from Joe_Humbert] 12:57:50 julianmka has joined #MATF 13:00:00 AlainVagner has joined #matf 13:00:06 present+ 13:00:36 quintinb has joined #MATF 13:00:41 present+ 13:01:03 github-bot has joined #matf 13:01:05 Illai has joined #matf 13:01:22 scribe: quintinb 13:01:26 Aashutosh has joined #matf 13:01:33 present+ 13:01:46 RacheleD has joined #MATF 13:01:55 move to next agendum 13:01:55 agendum 1 -- 2.5.4 - Motion Actuation -- taken up [from Joe_Humbert] 13:02:00 present+ 13:02:06 Detlev has joined #matf 13:02:06 present+ 13:02:09 Please ensure I properly represent you - if you want to correct me I welcome the feedback! 13:02:13 present+ 13:02:15 present + 13:03:05 Mick has joined #MATF 13:03:08 Jamie has joined #matf 13:03:15 present+ 13:03:52 present+ 13:04:48 Joe_Humbert We may need to add some sections - he's going through it and will share it out with us on slack and email (action items in progress) 13:06:03 q+ 13:06:15 ack julianmka 13:06:35 https://github.com/w3c/matf/issues/40 13:06:38 julianmka: This one is refreshingly straightforward as it seems to have been made with mobile in mind 13:06:41 +1 13:06:55 +1 13:07:02 +1 13:08:04 +1 13:08:08 !+ 13:08:13 1+ 13:08:17 +1 13:08:18 +1 13:08:31 +1 13:08:57 +1 13:09:20 move to next agendum 13:09:20 agendum 2 -- Review 2nd round of voting on SCs that required little or no modification from WCAG2ICT -- taken up [from Joe_Humbert] 13:09:23 ACTION: Accept proposed language in 2.5.4 Github issue 13:09:50 Devanshu has joined #matf 13:09:58 present+ 13:11:57 +1 13:11:59 +1 13:12:01 +1 13:12:02 +1 13:12:06 +1 13:12:07 +1 13:12:07 +` 13:12:09 +1 to accept 2.5.3 as written from WCAG2ICT 13:12:10 +1 13:12:15 +1 13:12:28 2.5.4 sorry 13:12:46 ACTION: accept 2.5.4 as written from WCAG2ICT 13:12:47 2.5.3 quintinb 13:12:59 accept 2.5.4 as written from WCAG2ICT 13:13:05 both 13:13:19 [ACTION] accept 2.5.3 as written from WCAG2ICT 13:13:26 ACTION: accept 2.5.3 as written from WCAG2ICT 13:16:40 q+ 13:17:47 My only concern with errors in dialogs is that they are generally removed once the user dismissing them. Ideally the error doesn't get removed until it's resolved. Hence I think inline provides more value. 13:17:49 Jamie: There was a question raised about the words "in text" - does the error need to be in the same location (as opposed to a dialog)? 13:18:38 Joe_Humbert indicated from the intent page seems to show that the mechanism of display is not covered 13:20:03 q+ 13:20:11 +1 Mick - although persistant error messages may not update if they are repeated 13:20:14 ack julianmka 13:21:44 The SC is about the content itself 13:21:47 q+ 13:21:48 julianmka: We do need to consider that we are used to nuances. We should probably advocate for multiple mechanisms of showing errors (if we are going to do it) 13:21:55 ack Detlev 13:21:58 +1 to julianmka 13:23:54 Detlev: The "in text" statement probably means that the error should be more than just an image - that it could be detectable by different assistive technologies as text. 13:24:33 q+ 13:24:51 +1 to julianmka , but it is probably should be a part of a document like the "Understanding" part not a part of the SC 13:25:13 I interoperate the same as Joe 13:25:16 Agreed, Illai 13:25:36 +1 Illai, no variation needed in this moment 13:25:47 ack Jamie 13:27:35 Jamie This is in the understanding section and is about the content of the error. It can look like that some of the errors are identified by it's location. The content may not need to have specific placement. Focus is on the understanding section. Location is not in the criteria 13:29:07 Jamie placement could be an additional SC - it's a different angle to consider. I'm suggesting to not make any changes to the SC as is 13:29:58 +1 13:29:59 +1 13:30:00 +1 13:30:01 +1 13:30:01 +1 13:30:02 +1 13:30:05 +1 13:30:06 +1 13:30:09 +1 13:30:10 ACTION: accept 3.3.1 as written from WCAG2ICT 13:30:41 q+ 13:31:07 ack detlev 13:32:10 Detlev If you have a multi-field form with an error message - to identify the error you would need to describe which field. In this case it would not just be location. Perhaps by label or something. This would come from the general understanding 13:33:19 q+ 13:33:28 ack Jamie 13:34:45 Jamie Question of functionality in native: "If an input error is automatically detected" - could there be a mechanism to "bypass" the intention of the criteria because it was not automatically detected 13:36:18 Joe_Humbert An error message would not display if it was not automatically detected 13:37:33 Detlev if there is no automation, then this probably isn't a reason for the SC 13:38:03 +1 to accept 3.3.3 as is 13:38:07 +1 13:38:10 +1 13:38:11 +1 13:38:12 +1 13:38:15 +1 13:38:17 +1 13:38:25 +2 13:38:27 +1 13:38:38 ACTION: accept 3.3.3 as written from WCAG2ICT 13:38:59 Very enthusiastic I am, lol 13:39:02 +1 13:39:45 q+ 13:40:06 ack julianmka 13:40:39 julianmka no question! 13:41:06 +1 to accept 3.3.4 as is (save the "web" word) from WCAG2ICT 13:41:17 +1 13:41:18 +1 13:41:18 +1 13:41:18 +1 13:41:19 +1 13:41:21 +1 13:41:23 +1 13:41:28 Who does web anyway? 13:41:29 +1 13:41:37 lol 13:41:40 ACTION: accept 3.3.4 as written (save the word "Web") from WCAG2ICT 13:42:13 Joe_Humbert new labels will be added when permissions are given 13:42:33 FYI I'm having zoom issues so now entirely IRC 13:42:47 Any comments on 3.3.7? 13:43:26 Happy to accept 3.3.7 as is from WCAG2ICT? 13:43:30 not to do WCAG 2.3 yet? 13:43:35 2.2 i mean 13:43:35 +1 13:43:38 +1 13:43:39 +1 13:43:39 +1 13:43:46 +1 13:43:46 +1 13:43:46 +1 13:43:46 +1 13:43:50 +1 13:43:54 ACTION: accept 3.3.7 as written from WCAG2ICT 13:46:37 q+ 13:46:47 ack quintinb 13:47:17 q+ 13:47:42 summary quintinb? 13:48:28 topic Joe_Humbert? 13:48:29 q+ 13:48:44 quintinb with custom versions of Android (AOSP) this may present problems? Does this apply to the operating system? 13:49:45 Joe_Humbert we can't apply this to operating systems 13:49:51 quintinb +1 13:50:00 which SC are we discussing? 13:50:05 3.3.8 13:50:08 +1 quintinb 13:50:55 Sorry I meant to +1 Joe_Humbert, not myself, lol 13:51:03 Nothing more from me 13:51:05 q? 13:51:13 q- 13:51:16 ack julianmka 13:51:22 ack detlev 13:51:48 Detlev I think we should focus on the author and not the OS, we should focus on the app developer and not the OS 13:52:08 +1 Detlev 13:52:22 +1 Detlev 13:52:45 +1 Detlev 13:53:04 +1 to accept 3.3.8 as written from WCAG2ICT, with leaving out the notes 13:53:06 change from "web" in the WCAG2ICT language proposal 13:53:48 +1 13:53:49 +1 13:53:51 +1 13:53:51 +1 13:53:54 +1 13:53:55 +1 13:53:56 +1 13:53:57 +1 13:54:06 ACTION: accept 3.3.8 as a first draft from WCAG2ICT, with leaving out the notes and removing "web" references 13:55:13 End early! its already late in Singapore! 13:55:21 let's have it next meeting 13:55:32 Or we could spend 10 minutes discussing whether to end early 13:55:39 2.4.11 13:55:39 :D 13:55:42 We can always start discussing in the comments :D 13:56:08 ACTION: add 2.4.11 to agenda for next time 13:56:38 Aashutosh has left #matf 13:57:27 Zakim, list participants 13:57:27 As of this point the attendees have been Joe_Humbert, AlainVagner, quintinb, Aashutosh, RacheleD, julianmka, Detlev, Jamie, Mick, Devanshu, ` 13:58:02 rrsagent, make minutes 13:58:04 I have made the request to generate https://www.w3.org/2024/09/18-matf-minutes.html Joe_Humbert 13:59:31 rrsagent, bye 13:59:31 I see 9 open action items saved in https://www.w3.org/2024/09/18-matf-actions.rdf : 13:59:31 ACTION: Accept proposed language in 2.5.4 Github issue [1] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-09-23 13:59:31 ACTION: accept 2.5.4 as written from WCAG2ICT [2] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-12-46 13:59:31 ACTION: accept 2.5.3 as written from WCAG2ICT [3] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-13-26 13:59:31 ACTION: accept 3.3.1 as written from WCAG2ICT [4] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-30-10 13:59:31 ACTION: accept 3.3.3 as written from WCAG2ICT [5] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-38-38 13:59:31 ACTION: accept 3.3.4 as written (save the word "Web") from WCAG2ICT [6] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-41-40 13:59:31 ACTION: accept 3.3.7 as written from WCAG2ICT [7] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-43-54 13:59:31 ACTION: accept 3.3.8 as a first draft from WCAG2ICT, with leaving out the notes and removing "web" references [8] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-54-06 13:59:31 ACTION: add 2.4.11 to agenda for next time [9] 13:59:31 recorded in https://www.w3.org/2024/09/18-matf-irc#T13-56-08