13:21:34 <pauljadam> That's a container title not a page title. 13:21:58 <Detlev> JJ: we don't have title attribute - it might not be visible 13:22:22 <Detlev> JJ: a web view title would nob (generally) be visible 13:22:26 <pauljadam> good example that would fail if you don't add a visible title to the web view inside a native app 13:22:41 <shoobe01> We're getting back to the problem of not being able to define what a Page is again. Webview, dialog, overlay, panel, drawer... which need a title? May not be solvable because of this limit to our scope 13:23:13 <pauljadam> Often the terms and conditions page is in a web view in the app so that page would need a visible title that usually would be the H1 13:23:18 <Detlev> JJ: it title is not visible, is it reasonable to mandate visible title of a webview? 13:23:49 <pauljadam> Luckily most pages need a H1 so that usually is the visible title too :) 13:23:55 <Detlev> JJ: Most voted for must - but there might be edge case that we have missed 13:24:24 <JJ> move to next agendum 13:24:24 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:24:29 <shoobe01> Have had issues of embedded webviews, both two titles and screenreader not properly interpreting H1 in the webview as only title etc. It's fraught. 13:24:37 <Detlev> JJ: both should and must might work - need to look at survey results 13:24:47 <JJ> Label in name proposal moved to next week 13:24:53 <JJ> move to next agendum 13:24:53 <Zakim> agendum 2 was just opened, JJ 13:25:01 <Detlev> JJ: HAd no time to look at 2.5.3 move to next week 13:25:01 <JJ> open agendum 3 13:25:21 <JJ> https://github.com/w3c/matf/issues/14#issuecomment-4242723808 13:25:24 <pauljadam> screen reader in a web view will read the <title> as the title, the visible title or heading text would be read as a heading 13:25:43 <Detlev> JJ: We have draft from Tanya and feedback from shoobe01 13:25:58 <shoobe01> The end of my notes has proposed revision text. 13:26:01 <Detlev> ...repacing web page with page 13:26:28 <Detlev> ...we need a note for auditors to check the default language of an app 13:26:48 <Detlev> ...need the screen reader to check whioch speech engine is used 13:27:07 <Detlev> JJ: (reads from 3.1.1 draft) 13:27:26 <Detlev> ...feedback from Steven 13:27:30 <JJ> https://github.com/w3c/matf/issues/14#issuecomment-4296662885 13:28:02 <Detlev> shoobe01: need layers model to show how locale language is inherited 13:28:05 <pauljadam> I updated the Language.md docs explaining how to use locale on iOS and added a language of page good bad demo https://github.com/cvs-health/ios-swiftui-accessibility-techniques/blob/main/iOSswiftUIa11yTechniques/Documentation/Language.md 13:28:50 <Detlev> shoobe01: you could shange language on a page even though it generally applies to whole app 13:29:26 <Detlev> JJ: language is set at the platform level, apps inherit that 13:30:10 <Detlev> ...if OS language is not used by app, it needs to be overwritten to use its own language 13:30:17 <pauljadam> Could mention that you set the language of page using the correct Locale during your localization process or something like that. 13:30:53 <Detlev> shoobe01: You can change language for one page but you should better do it the right way 13:31:24 <shoobe01> pauljadam I tried to say this in the proposal "In mobile applications, the language is typically set at the platform (OS) level as part of the localization service" unless I am missing some nuance 13:32:40 <pauljadam> You could make a bad app example by creating it with the wrong locale that is different than the language text the screen reader is focused on. Like if I say the app Locale is Spanish but the text is English then it will speak with a Spanish accent. 13:33:35 <Detlev> JJ: not all screen reader (Android) use the right language - case: content in Dutch, role set to button, translated term (Knopf) pronounced in English 13:33:58 <pauljadam> That's one thing the Locale also does it makes an element's trait like "Heading" say whatever that word means in the set language. So it won't say Heading. 13:34:13 <shoobe01> Was gonna go queue plus to say what pauljadam just typed. It isn't gonna read in english, but try to read what is on screen from the english reader. It is BAD. 13:34:36 <Detlev> JJ: one way to set a female voice for the local language and a male one would render things not localized 13:34:40 <shoobe01> +1 on "it's not hard!" 13:35:01 <Detlev> JJ: Normally the language is set just once at the app level 13:35:08 <JJ> q? 13:35:26 <shoobe01> q+ 13:35:42 <JJ> ack shoobe 13:36:39 <Detlev> shoobe01: The app will not support any language - do we care about that problem - say, if local is not supported and the app falls back to english 13:36:48 <pauljadam> If the app shows English text then that text needs the language set right for the screen reader. 13:37:11 <pauljadam> programmatically setting the language 13:37:33 <JJ> move to next agendum 13:37:33 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:37:38 <Detlev> JJ: na check WCAG to be consistent with usage 13:37:38 <JJ> move to next agendum 13:37:38 <Zakim> agendum 2 was just opened, JJ 13:37:45 <JJ> move to agenda item 3 13:37:49 <JJ> move to agenda 3 13:37:52 <JJ> move to next agendum 13:37:52 <Zakim> agendum 3 was just opened, JJ 13:38:22 <JJ> move to next agendum 13:38:22 <Zakim> agendum 3 was just opened, JJ 13:38:23 <JJ> move to next agendum 13:38:23 <Zakim> agendum 3 was just opened, JJ 13:38:52 <Detlev> JJ: dragging movements is the next one 13:39:07 <shoobe01> Transcription has looked good to me. I have been following and not found anything needing correction Detlev. Thanks for interpreting my firehose of talking :) 13:39:11 <Detlev> JJ: Detlev question why should we change it 13:39:18 <JJ> move to next agendum 13:39:18 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:39:25 <JJ> move to next agendum 13:39:25 <Zakim> agendum 2 was just opened, JJ 13:39:47 <JJ> take up agendum 4 13:40:02 <Detlev> shoobe01: Did not like the term "single pointer" 13:41:04 <JJ> https://www.w3.org/TR/2024/REC-WCAG22-20241212/#dfn-single-pointer 13:41:09 <Detlev> Detlev: ..single pointer does not apply to the action 13:41:39 <Detlev> JJ: looks at WCAG single pointer definition 13:42:44 <Detlev> shoobe01: pointer sounded as if it was inherited from desktop / mouse 13:43:30 <shoobe01> (and I am talking super fast again....) 13:43:33 <Detlev> shoobe01: not good case to deviate 13:43:46 <Detlev> JJ: move back to single pointer 13:44:13 <shoobe01> q+ 13:44:28 <Detlev> JJ: exception for "deteriming by the user agent - describe natively supported dragging movements in mobile context 13:44:32 <JJ> ack shoobe 13:45:08 <Detlev> shoobe01: JJ had a comment - should we have a note? 13:45:25 <Detlev> JJ: the WCAG note is already there 13:45:46 <Detlev> ...may not be necessary 13:46:20 <JJ> q? 13:46:35 <Sam-Estoesta> Best practice for policy writing is to use references, so link would suffice here. 13:47:45 <JJ> ACTION: Consider adding note to 2.5.8 to clarify single pointer for mobile app developers 13:48:37 <shoobe01> afk 13:49:03 <JJ> ACTION: Include examples for 2.5.8 with dragging movements taken care of by the platform 13:49:40 <shoobe01> rtk 13:50:37 <JJ> Detlev: explains the needs auditors like himself would need for this SC 13:50:40 <JJ> q? 13:51:38 <pauljadam> Native iOS List view that is recordable is not accessible to single pointer taps 13:51:39 <Detlev> Check OS supported methods for dragging, reordering etc - where it uses native drag-n-drop 13:51:56 <JJ> take up agendum 5 13:51:59 <Detlev> JJ: provide examples of native patterns that would be exempt 13:52:05 <JJ> https://github.com/w3c/matf/issues/52#issuecomment-4240803989 13:52:45 <Joe_Humbert> q+ 13:53:11 <Detlev> JJ: Feedback in last week's meeting was that SC is ready for draft - wemay add a third note but last week indicated we can leave out note 3 so we can keep it the way it is 13:53:18 <JJ> https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum#intent 13:54:04 <Detlev> JJ: has exceptions for repositioned content, and for things explictly brought up by user 13:54:19 <Detlev> JJ: can be applied as is 13:54:24 <JJ> q? 13:54:34 <JJ> ack Joe_Humbert 13:55:25 <Detlev> Joe_Humbert: SC already in first draft - was brought back because people had questions about it 13:56:02 <Detlev> JJ: Based on last week, we should close this one. 13:56:39 <JJ> ACTION: Close issue 52 for SC 2.4.11 - it is already in the draft using the same text as discussed in recent meetings 13:56:50 <Detlev> JJ: no comments... will close issue. 13:58:12 <Detlev> JJ. Will work on SCs in the agenda, then move on to software layers and possible deviation for target size 13:58:34 <Detlev> larger target size may just remain a note pointing to OS recomms 13:59:54 <shoobe01> Agree, I read the transcript and minutes to assure I didn't miss anything and it looked good today! 14:00:07 <shoobe01> present- 14:00:45 <JJ> Zakim, list participants 14:00:45 <Zakim> As of this point the attendees have been shoobe, Detlev, Joe_Humbert, Sam-Estoesta, tayef, present 14:00:57 <JJ> rrsagent, make minutes 14:00:58 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/29-matf-minutes.html JJ 14:10:00 <JJ> regrets+ Tanya 14:10:29 <JJ> rrsagent, make minutes 14:10:31 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/29-matf-minutes.html JJ 14:11:05 <JJ> rrsagent, bye 14:11:05 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2026/04/29-matf-actions.rdf : 14:11:05 <RRSAgent> ACTION: Consider adding note to 2.5.8 to clarify single pointer for mobile app developers [1] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-47-45 14:11:05 <RRSAgent> ACTION: Include examples for 2.5.8 with dragging movements taken care of by the platform [2] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-49-03 14:11:05 <RRSAgent> ACTION: Close issue 52 for SC 2.4.11 - it is already in the draft using the same text as discussed in recent meetings [3] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-56-39 14:11:16 <JJ> zakim, bye 14:11:16 <Zakim> leaving. As of this point the attendees have been shoobe, Detlev, Joe_Humbert, Sam-Estoesta, tayef, present 14:11:16 <Zakim> Zakim has left #matf

12:54:41 RRSAgent has joined #matf 12:54:45 logging to https://www.w3.org/2026/04/29-matf-irc 12:54:45 RRSAgent, make logs Public 12:54:46 please title this meeting ("meeting: ..."), JJ 12:54:46 Zakim, this is MATF 29 April 2026 12:54:46 got it, JJ 12:54:51 Meeting: MATF 29 April 2026 12:55:16 agenda+ 2.4.2 Page Titled updated proposal 12:55:22 agenda+ 2.5.3 Label in Name updated proposal 12:55:26 agenda+ 3.1.1 Language of Page updated proposal 12:55:29 agenda+ 2.5.7 Dragging Movements updated proposal 12:55:33 agenda+ 2.4.11 Focus Not Obscured (Minimum) updated proposal 12:55:37 agenda+ Software layers 12:55:40 agenda+ 2.5.8 Target Size (Minimum) 12:57:52 shoobe01 has joined #matf 12:58:02 Present+ 13:02:32 tayef has joined #matf 13:04:04 Joe_Humbert has joined #matf 13:05:24 move to next agendum 13:05:24 agendum 1 -- 2.4.2 Page Titled updated proposal -- taken up [from JJ] 13:05:36 Detlev has joined #matf 13:05:41 presnet+ 13:05:45 present+ 13:05:48 scribe: Detlev 13:05:48 Sam-Estoesta has joined #matf 13:06:27 Agenda: Page titled, label in name usw. (see agenda) 13:06:33 present+ 13:06:33 https://github.com/w3c/matf/issues/9#issuecomment-4242557542 13:06:36 present+ 13:06:50 JJ: First item page titled - proposal from Tanya 13:06:53 present+ 13:07:04 ..biggest difference: page instead of web page 13:07:36 pauljadam has joined #matf 13:07:42 JJ: A note clarifies how title can be supplied (in difference to web) 13:07:46 +present 13:08:06 JJ: not updating this anymore 13:08:19 ...before submission of new draft 13:08:26 JJ: Tanya commented 13:08:28 Updated proposal by Tanya: https://github.com/w3c/matf/issues/9#issuecomment-4296338896 13:09:00 JJ: She has removed "when phyiscal title is not feasible" 13:09:22 ...heading requirement removed (would fall under 1.3.1) 13:09:46 JJ: (reads from issue on page titled) 13:10:15 JJ: note on should / must usage 13:10:16 Should it say a "selected" tab instead of a "highlighted" tab? I get the meaning either way. 13:10:35 or it's not that the tab is selected each page has a tab and you can see the tab title 13:10:59 JJ: agrees "selected" might be clearer 13:11:14 q+ 13:11:25 pauljadam: but you see the text of unselected tabs so it may not be clearer 13:11:54 JJ: will read "should be provided" - but "must be specific" 13:12:18 ack shoobe 13:12:25 JJ: question if it can be invisible 13:12:26 could say "a page title is provided through visible text" 13:13:20 shoobe01: shows position in the system - highlighted tab 13:13:22 All of the page title examples we used are visible 13:13:39 "active" tab instead of "highlighted" or "selected" 13:14:08 shoobe01: selected implies action, highlighted is better therefore 13:14:18 But just having a tab that has a title on the tab button makes the tab have a visible title. The user could think the title of the tab is the title of the page unless you provide another page title on the page then it might be seen as a sub page of that tab. 13:14:19 1+ to active 13:15:20 JJ: most apps shoulf be able to comply b yhaving some visible text - so that could become a must? 13:16:23 If you call it a dialog then it is not required to have a page title but if you call it a page then it needs a page title. 13:16:28 how to exempt views that are interim steps? 13:16:46 JJ: through page definition that might exclude those modal views or steps 13:17:34 JJ: ...if part of a flow that would probably be sufficiently exempted 13:18:13 Poll: do we write "must" to require the page title text to be visible, or keep "should" meaning it is recommended to be visible? 13:18:17 Detlev: so now clear fail if it is invisible? 13:18:36 must 13:18:37 should 13:19:01 must 13:19:07 if you cant see the title then there is no title :) 13:19:29 must 13:20:11 that's why having good and bad techniques / examples are important, like show us a good example where a page title is not visible ? 13:20:54 JJ: Web content could be difficult - like in webviews that have title but are invisible 13:21:11 But there are probably not any browsers that don't show the page 13:21:34 <pauljadam> That's a container title not a page title. 13:21:58 <Detlev> JJ: we don't have title attribute - it might not be visible 13:22:22 <Detlev> JJ: a web view title would nob (generally) be visible 13:22:26 <pauljadam> good example that would fail if you don't add a visible title to the web view inside a native app 13:22:41 <shoobe01> We're getting back to the problem of not being able to define what a Page is again. Webview, dialog, overlay, panel, drawer... which need a title? May not be solvable because of this limit to our scope 13:23:13 <pauljadam> Often the terms and conditions page is in a web view in the app so that page would need a visible title that usually would be the H1 13:23:18 <Detlev> JJ: it title is not visible, is it reasonable to mandate visible title of a webview? 13:23:49 <pauljadam> Luckily most pages need a H1 so that usually is the visible title too :) 13:23:55 <Detlev> JJ: Most voted for must - but there might be edge case that we have missed 13:24:24 <JJ> move to next agendum 13:24:24 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:24:29 <shoobe01> Have had issues of embedded webviews, both two titles and screenreader not properly interpreting H1 in the webview as only title etc. It's fraught. 13:24:37 <Detlev> JJ: both should and must might work - need to look at survey results 13:24:47 <JJ> Label in name proposal moved to next week 13:24:53 <JJ> move to next agendum 13:24:53 <Zakim> agendum 2 was just opened, JJ 13:25:01 <Detlev> JJ: HAd no time to look at 2.5.3 move to next week 13:25:01 <JJ> open agendum 3 13:25:21 <JJ> https://github.com/w3c/matf/issues/14#issuecomment-4242723808 13:25:24 <pauljadam> screen reader in a web view will read the <title> as the title, the visible title or heading text would be read as a heading 13:25:43 <Detlev> JJ: We have draft from Tanya and feedback from shoobe01 13:25:58 <shoobe01> The end of my notes has proposed revision text. 13:26:01 <Detlev> ...repacing web page with page 13:26:28 <Detlev> ...we need a note for auditors to check the default language of an app 13:26:48 <Detlev> ...need the screen reader to check whioch speech engine is used 13:27:07 <Detlev> JJ: (reads from 3.1.1 draft) 13:27:26 <Detlev> ...feedback from Steven 13:27:30 <JJ> https://github.com/w3c/matf/issues/14#issuecomment-4296662885 13:28:02 <Detlev> shoobe01: need layers model to show how locale language is inherited 13:28:05 <pauljadam> I updated the Language.md docs explaining how to use locale on iOS and added a language of page good bad demo https://github.com/cvs-health/ios-swiftui-accessibility-techniques/blob/main/iOSswiftUIa11yTechniques/Documentation/Language.md 13:28:50 <Detlev> shoobe01: you could shange language on a page even though it generally applies to whole app 13:29:26 <Detlev> JJ: language is set at the platform level, apps inherit that 13:30:10 <Detlev> ...if OS language is not used by app, it needs to be overwritten to use its own language 13:30:17 <pauljadam> Could mention that you set the language of page using the correct Locale during your localization process or something like that. 13:30:53 <Detlev> shoobe01: You can change language for one page but you should better do it the right way 13:31:24 <shoobe01> pauljadam I tried to say this in the proposal "In mobile applications, the language is typically set at the platform (OS) level as part of the localization service" unless I am missing some nuance 13:32:40 <pauljadam> You could make a bad app example by creating it with the wrong locale that is different than the language text the screen reader is focused on. Like if I say the app Locale is Spanish but the text is English then it will speak with a Spanish accent. 13:33:35 <Detlev> JJ: not all screen reader (Android) use the right language - case: content in Dutch, role set to button, translated term (Knopf) pronounced in English 13:33:58 <pauljadam> That's one thing the Locale also does it makes an element's trait like "Heading" say whatever that word means in the set language. So it won't say Heading. 13:34:13 <shoobe01> Was gonna go queue plus to say what pauljadam just typed. It isn't gonna read in english, but try to read what is on screen from the english reader. It is BAD. 13:34:36 <Detlev> JJ: one way to set a female voice for the local language and a male one would render things not localized 13:34:40 <shoobe01> +1 on "it's not hard!" 13:35:01 <Detlev> JJ: Normally the language is set just once at the app level 13:35:08 <JJ> q? 13:35:26 <shoobe01> q+ 13:35:42 <JJ> ack shoobe 13:36:39 <Detlev> shoobe01: The app will not support any language - do we care about that problem - say, if local is not supported and the app falls back to english 13:36:48 <pauljadam> If the app shows English text then that text needs the language set right for the screen reader. 13:37:11 <pauljadam> programmatically setting the language 13:37:33 <JJ> move to next agendum 13:37:33 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:37:38 <Detlev> JJ: na check WCAG to be consistent with usage 13:37:38 <JJ> move to next agendum 13:37:38 <Zakim> agendum 2 was just opened, JJ 13:37:45 <JJ> move to agenda item 3 13:37:49 <JJ> move to agenda 3 13:37:52 <JJ> move to next agendum 13:37:52 <Zakim> agendum 3 was just opened, JJ 13:38:22 <JJ> move to next agendum 13:38:22 <Zakim> agendum 3 was just opened, JJ 13:38:23 <JJ> move to next agendum 13:38:23 <Zakim> agendum 3 was just opened, JJ 13:38:52 <Detlev> JJ: dragging movements is the next one 13:39:07 <shoobe01> Transcription has looked good to me. I have been following and not found anything needing correction Detlev. Thanks for interpreting my firehose of talking :) 13:39:11 <Detlev> JJ: Detlev question why should we change it 13:39:18 <JJ> move to next agendum 13:39:18 <Zakim> agendum 2 -- 2.5.3 Label in Name updated proposal -- taken up [from JJ] 13:39:25 <JJ> move to next agendum 13:39:25 <Zakim> agendum 2 was just opened, JJ 13:39:47 <JJ> take up agendum 4 13:40:02 <Detlev> shoobe01: Did not like the term "single pointer" 13:41:04 <JJ> https://www.w3.org/TR/2024/REC-WCAG22-20241212/#dfn-single-pointer 13:41:09 <Detlev> Detlev: ..single pointer does not apply to the action 13:41:39 <Detlev> JJ: looks at WCAG single pointer definition 13:42:44 <Detlev> shoobe01: pointer sounded as if it was inherited from desktop / mouse 13:43:30 <shoobe01> (and I am talking super fast again....) 13:43:33 <Detlev> shoobe01: not good case to deviate 13:43:46 <Detlev> JJ: move back to single pointer 13:44:13 <shoobe01> q+ 13:44:28 <Detlev> JJ: exception for "deteriming by the user agent - describe natively supported dragging movements in mobile context 13:44:32 <JJ> ack shoobe 13:45:08 <Detlev> shoobe01: JJ had a comment - should we have a note? 13:45:25 <Detlev> JJ: the WCAG note is already there 13:45:46 <Detlev> ...may not be necessary 13:46:20 <JJ> q? 13:46:35 <Sam-Estoesta> Best practice for policy writing is to use references, so link would suffice here. 13:47:45 <JJ> ACTION: Consider adding note to 2.5.8 to clarify single pointer for mobile app developers 13:48:37 <shoobe01> afk 13:49:03 <JJ> ACTION: Include examples for 2.5.8 with dragging movements taken care of by the platform 13:49:40 <shoobe01> rtk 13:50:37 <JJ> Detlev: explains the needs auditors like himself would need for this SC 13:50:40 <JJ> q? 13:51:38 <pauljadam> Native iOS List view that is recordable is not accessible to single pointer taps 13:51:39 <Detlev> Check OS supported methods for dragging, reordering etc - where it uses native drag-n-drop 13:51:56 <JJ> take up agendum 5 13:51:59 <Detlev> JJ: provide examples of native patterns that would be exempt 13:52:05 <JJ> https://github.com/w3c/matf/issues/52#issuecomment-4240803989 13:52:45 <Joe_Humbert> q+ 13:53:11 <Detlev> JJ: Feedback in last week's meeting was that SC is ready for draft - wemay add a third note but last week indicated we can leave out note 3 so we can keep it the way it is 13:53:18 <JJ> https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum#intent 13:54:04 <Detlev> JJ: has exceptions for repositioned content, and for things explictly brought up by user 13:54:19 <Detlev> JJ: can be applied as is 13:54:24 <JJ> q? 13:54:34 <JJ> ack Joe_Humbert 13:55:25 <Detlev> Joe_Humbert: SC already in first draft - was brought back because people had questions about it 13:56:02 <Detlev> JJ: Based on last week, we should close this one. 13:56:39 <JJ> ACTION: Close issue 52 for SC 2.4.11 - it is already in the draft using the same text as discussed in recent meetings 13:56:50 <Detlev> JJ: no comments... will close issue. 13:58:12 <Detlev> JJ. Will work on SCs in the agenda, then move on to software layers and possible deviation for target size 13:58:34 <Detlev> larger target size may just remain a note pointing to OS recomms 13:59:54 <shoobe01> Agree, I read the transcript and minutes to assure I didn't miss anything and it looked good today! 14:00:07 <shoobe01> present- 14:00:45 <JJ> Zakim, list participants 14:00:45 <Zakim> As of this point the attendees have been shoobe, Detlev, Joe_Humbert, Sam-Estoesta, tayef, present 14:00:57 <JJ> rrsagent, make minutes 14:00:58 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/29-matf-minutes.html JJ 14:10:00 <JJ> regrets+ Tanya 14:10:29 <JJ> rrsagent, make minutes 14:10:31 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/29-matf-minutes.html JJ 14:11:05 <JJ> rrsagent, bye 14:11:05 <RRSAgent> I see 3 open action items saved in https://www.w3.org/2026/04/29-matf-actions.rdf : 14:11:05 <RRSAgent> ACTION: Consider adding note to 2.5.8 to clarify single pointer for mobile app developers [1] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-47-45 14:11:05 <RRSAgent> ACTION: Include examples for 2.5.8 with dragging movements taken care of by the platform [2] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-49-03 14:11:05 <RRSAgent> ACTION: Close issue 52 for SC 2.4.11 - it is already in the draft using the same text as discussed in recent meetings [3] 14:11:05 <RRSAgent> recorded in https://www.w3.org/2026/04/29-matf-irc#T13-56-39 14:11:16 <JJ> zakim, bye 14:11:16 <Zakim> leaving. As of this point the attendees have been shoobe, Detlev, Joe_Humbert, Sam-Estoesta, tayef, present 14:11:16 <Zakim> Zakim has left #matf