12:56:12 RRSAgent has joined #matf 12:56:17 logging to https://www.w3.org/2026/04/22-matf-irc 12:56:17 RRSAgent, make logs Public 12:56:18 please title this meeting ("meeting: ..."), JJ 12:56:20 Zakim, this is MATF 22 April 2026 12:56:20 got it, JJ 12:56:28 Meeting: MATF 22 April 2026 12:56:33 chair+ 12:58:21 agenda+ 3.1.1 Language of Page proposal 12:58:28 agenda+ 2.5.7 Dragging Movements proposal 12:58:35 shoobe01 has joined #matf 12:58:36 agenda+ 2.4.11 Focus Not Obscured (Minimum) proposal 12:58:41 agenda+ Software layers 12:58:48 agenda+ 2.5.8 Target Size (Minimum) 12:58:53 agenda+ 2.4.2 Page Titled updated proposal 12:58:58 agenda+ 2.5.3 Label in Name updated proposal 13:00:36 present+ 13:01:19 pauljadam has joined #matf 13:02:14 RobW has joined #matf 13:02:21 present+ 13:04:04 sam_estoesta has joined #matf 13:04:20 Zakim, nominate a scribe 13:04:20 Not knowing who is chairing or who scribed recently, I propose RobW 13:04:51 tayef has joined #matf 13:05:08 move to next agendum 13:05:08 agendum 1 -- 3.1.1 Language of Page proposal -- taken up [from JJ] 13:05:53 Tanya has joined #matf 13:05:58 present+ 13:06:02 https://github.com/w3c/matf/issues/14#issuecomment-4242723808 13:07:34 Joe_Humbert has joined #matf 13:08:05 Code for Android to set accessibility language: https://github.com/appt-org/screenreader-android/commit/e51803136b8be00dab6b0e5d8e62aa958f0851ec 13:09:20 JJ historically this was possible on iOS but not Android. This has changed in a recent update allowing switching languages for an app, this is repeated by TalkBack. 13:09:52 *respected 13:09:53 present+ 13:11:00 present+ 13:11:10 present+ 13:12:04 q+ 13:12:27 https://developer.android.com/guide/topics/resources/app-languages#use-localeconfig 13:12:35 Tanya implementing app language on Android is a developer choice. Can be tested by changing the app language in device settings. Some apps have language settings in the app. 13:14:09 ack shoobe 13:14:17 present+ 13:15:17 @jj Changing the language using an in-app switcher doesn't change the speech synthesiser so is not respected by TalkBack, so testing the system setting is required. 13:15:18 locale is android term 13:15:42 I'm not sure we need to talk about how you set the language, just that you do set the language 13:16:03 q+ 13:16:04 q+ 13:17:11 ack RobW 13:18:06 RobW: setting language at system level will change the language of speech synthesizer. When you change the language in the app, it will only change from which language the strings are loaded - it does not affect the speech synthesizer. 13:18:10 ack pauljadam 13:18:19 Locale is an iOS term 13:18:49 https://developer.apple.com/documentation/foundation/locale 13:18:58 https://developer.android.com/reference/java/util/Locale 13:20:28 Ok I guess I was not thinking about Locale on iOS becaues the property you use is called .languageIdentifier() 13:20:32 q? 13:21:13 move to next agendum 13:21:13 agendum 2 -- 2.5.7 Dragging Movements proposal -- taken up [from JJ] 13:21:23 https://github.com/w3c/matf/issues/53#issuecomment-4178692737 13:21:48 Does Locale on iOS make VoiceOver speak the proper synthesizer? I've not tried it before I don't think. 13:25:04 q+ 13:25:21 ack shoobe 13:25:50 @pauljadam - yes it does if you set it at UIApplication level 13:26:35 shoobe01 Single pointer is a weird term. Is this useful to inherit? 13:26:48 Thanks! I need to make a technique / demo on Locale then :) 13:26:51 https://w3c.github.io/matf/#success-criterion-2-5-7-dragging-movements 13:27:48 Single pointer is a finger or a mouse or a stylus, Pointer Events is a web term also 13:28:19 q? 13:28:40 I had always understood 'finger tap' to be included in 'single pointer' 13:29:34 q+ 13:30:19 ack shoobe 13:30:32 That's why they call it your "Pointer Finger" :) 13:31:11 q+ 13:31:29 ack RobW 13:32:20 JJ WCAG2ICT "Single pointer" definition specifies a single finger tap. 13:33:02 move to the next agendum 13:33:08 Zakim, move to the next agendum 13:33:08 I don't understand 'move to the next agendum', JJ 13:33:17 move to next agendum 13:33:17 agendum 3 -- 2.4.11 Focus Not Obscured (Minimum) proposal -- taken up [from JJ] 13:36:20 q+ 13:36:47 q+ 13:37:01 ack pauljadam 13:37:07 https://github.com/w3c/matf/issues/52#issuecomment-4240803989 13:37:17 q+ 13:38:08 pauljadam SC only says keyboard focus, not AT. AT can focus on things keyboards can't and uses a separate focus engine. 13:38:41 q? 13:38:46 ack RobW 13:40:26 You don't need something to be keyboard accessible for it to be screen reader operable on a web site 13:40:32 ack Joe_Humbert 13:42:05 Some WCAG SCs say "focus" only like On Focus and then some say "keyboard focus" specifically like Focus Not Obscured. 13:42:26 Joe_Humbert The SC references 'Keyboard focus', it should be clear that this doesn't matter how keyboard focus is being done. 13:43:03 Good clarification, thanks pauljadam 13:45:07 ACTION: Check if it is possible to cover AT focus, or if AT focus is always visible, even if focusing on content that is "hidden" behind a modal or dialog 13:45:15 move to next agendum 13:45:15 agendum 4 -- Software layers -- taken up [from JJ] 13:45:27 https://github.com/w3c/matf/issues/270#issuecomment-4069206285 13:46:55 RobW: Took a look at everything in the Miro board and all the comments, tried to distill that into text content that meets the established requirements 13:48:00 q+ 13:48:18 ack shoobe 13:49:17 ACTION: Have a look at definition proposals at https://github.com/w3c/matf/issues/270#issuecomment-4284139543 13:50:10 move to next agendum 13:50:10 agendum 5 -- 2.5.8 Target Size (Minimum) -- taken up [from JJ] 13:51:34 q+ 13:51:44 ack shoobe 13:52:29 Full Keyboard Access on iOS you can fully obscure the focus if you have a dialog displayed and you don't prevent moving focus underneath the dialog. The werid part is that Full Keyboard Access shows 2 focus outlines, one around the entire scroll view container and then another around the actual element with focus like a button on the body of scroll 13:52:29 view. So the thing with the acutal keyboard focus can be fully obscured and then you can only see that focus is somwhere inside the scroll view. Not sure if that counts as "fully obscured" though since WCAG left that wiggle room 🤦🏻‍♂️ 13:53:36 https://www.w3.org/2026/04/21-ag-minutes.html AG WG minutes including MATF + scoping questions 13:54:37 Scoping Poll results: https://www.w3.org/wbs/35422/scope_exercise/results/ 13:55:56 q+ 13:56:49 watch app uses the same code as a phone app 13:58:29 ack shoobe 13:58:34 zakim, close the queue 13:58:34 ok, JJ, the speaker queue is closed 13:58:40 Platforms for WCAG3 discussion https://github.com/w3c/wcag3/discussions/647 14:01:53 Zakim, list participants 14:01:53 As of this point the attendees have been shoobe, RobW, Tanya, Joe_Humbert, tayef, sam_estoesta, pauljadam 14:01:59 scribe: RobW 14:02:01 rrsagent, make minutes 14:02:03 I have made the request to generate https://www.w3.org/2026/04/22-matf-minutes.html JJ 14:05:43 rrsagent, bye 14:05:43 I see 2 open action items saved in https://www.w3.org/2026/04/22-matf-actions.rdf : 14:05:43 ACTION: Check if it is possible to cover AT focus, or if AT focus is always visible, even if focusing on content that is "hidden" behind a modal or dialog [1] 14:05:43 recorded in https://www.w3.org/2026/04/22-matf-irc#T13-45-07 14:05:43 ACTION: Have a look at definition proposals at https://github.com/w3c/matf/issues/270#issuecomment-4284139543 [2] 14:05:43 recorded in https://www.w3.org/2026/04/22-matf-irc#T13-49-17 14:05:50 zakim, bye 14:05:50 leaving. As of this point the attendees have been shoobe, RobW, Tanya, Joe_Humbert, tayef, sam_estoesta, pauljadam 14:05:50 Zakim has left #matf