13:57:47 <RRSAgent> RRSAgent has joined #matf
13:57:51 <RRSAgent> logging to https://www.w3.org/2026/02/18-matf-irc
13:57:51 <Zakim> RRSAgent, make logs Public
13:57:52 <Zakim> please title this meeting ("meeting: ..."), JJ
13:57:54 <JJ> Zakim, this is MATF 18 February 2026
13:57:54 <Zakim> got it, JJ
13:57:57 <shoobe01> shoobe01 has joined #matf
13:57:59 <JJ> Meeting: MATF 18 February 2026
13:58:03 <JJ> chair+
13:58:19 <JJ> agenda+ Software layers (User Agent, Platform Software, etc.)
13:58:25 <JJ> agenda+ Keyboard interface + Accessibility interface + Virtual keyboard
13:58:25 <shoobe01> Present+
13:58:33 <JJ> agenda+ Mobile operating system
13:58:38 <JJ> agenda+ Set of Webpages
13:58:42 <JJ> agenda+ Page Titled
13:59:26 <JJ> zakim, agenda?
13:59:26 <Zakim> I see 5 items remaining on the agenda:
13:59:27 <Zakim> 1. Software layers (User Agent, Platform Software, etc.) [from JJ]
13:59:27 <Zakim> 2. Keyboard interface + Accessibility interface + Virtual keyboard [from JJ]
13:59:27 <Zakim> 3. Mobile operating system [from JJ]
13:59:27 <Zakim> 4. Set of Webpages [from JJ]
13:59:28 <Zakim> 5. Page Titled [from JJ]
14:00:39 <tayef> tayef has joined #matf
14:02:13 <JatinV> JatinV has joined #matf
14:03:20 <JJ> regrets+ Tanya
14:03:32 <tayef> present+
14:03:42 <JatinV> present+
14:03:52 <quintinb> quintinb has joined #MATF
14:04:03 <quintinb> present+
14:04:05 <JJ> scribe: quintinb
14:04:47 <Joe_Humbert> Joe_Humbert has joined #matf
14:05:15 <shoobe01> q+
14:05:26 <JJ> ack shoobe
14:05:26 <pauljadam> pauljadam has joined #matf
14:05:49 <shoobe01> Nope, changed audio for a thing and I broke it. NM for now.
14:05:50 <Tim> Tim has joined #matf
14:05:57 <shoobe01> I'll type and you can catch up while I work it out
14:06:02 <Joe_Humbert> present+
14:06:23 <JJ> move to next agendum
14:06:23 <Zakim> agendum 1 -- Software layers (User Agent, Platform Software, etc.) -- taken up [from JJ]
14:06:24 <JJ> https://miro.com/welcomeonboard/R0dUeHp3dUd1Nmp4ZG5lWVo4eG5kekY4dHlTbHZWMzh2TS91WTZJSTRQTDJYKzVTd3Q3RU9KSC9RMGRJN1lrM3dCRnBHdDRrRHhNVkxrWEZ5ZGh6TVpsVnVJY2tXR2hwVm5GU3Y4VFJramI1bjgyNmdBcmd3WG9zemRZRkR1cU9hWWluRVAxeXRuUUgwWDl3Mk1qRGVRPT0hdjE=?share_link_id=386230017222
14:06:40 <shoobe01> "Software Layers" It's overall layers, we are way outside software. What is the actual name of the topic/definition we're working on? Want to make sure makes sense for the scope of discussion
14:06:43 <quintinb> Actually live captions are pretty great just for being able to catch up
14:08:20 <shoobe01> My brain is on several tracks so I love having the full transcript, often go back and forth reading it during the meeting.
14:09:54 <shoobe01> q+
14:10:58 <shoobe01> q-
14:11:33 <JJ> Diagram from W3C: https://www.w3.org/WAI/fundamentals/components/
14:12:13 <quintinb> Oooh I like that diagram
14:16:09 <shoobe01> I have tossed it and the link to source into the MIro so we can discuss live as the other diagrams are.
14:17:13 <shoobe01> q+
14:17:47 <JJ> ack shoobe
14:17:53 <quintinb> yay!
14:19:35 <quintinb> I like the concept - the concern is complexity - we need to make this simple for all readers. It would be nice if we could show some layer skipping, without cluttering the diagram
14:19:44 <quintinb> ^ shoobe01
14:21:25 <quintinb> shoobe01 we could just let it be complicated. Isn't a web view on top of the app? Are these layers ordered correctly?
14:29:20 <JJ> move to next agendum
14:29:20 <Zakim> agendum 2 -- Keyboard interface + Accessibility interface + Virtual keyboard -- taken up [from JJ]
14:29:38 <quintinb> I find it interfacing
14:31:23 <quintinb> q+
14:31:34 <JJ> ack quintinb
14:31:47 <JJ> Keyboard interface: https://github.com/w3c/matf/issues/66#issuecomment-3553194380
14:31:54 <JJ> Accessibility interface: https://github.com/w3c/matf/issues/247#issuecomment-3227673242
14:32:02 <JJ> Virtual keyboard: https://github.com/w3c/matf/issues/91#issuecomment-3717984460
14:32:49 <quintinb> quintinb: So the A11y interface is to ensure all assistive tech is represented in the success criteria?
14:32:52 <JJ> https://www.w3.org/TR/wcag2ict-22/#keyboard
14:34:47 <shoobe01> q+
14:37:17 <JJ> ack shoobe
14:38:25 <quintinb> shoobe01 It doesn't seem to mean interface in the way he understands it - we need to be clear in what we end up writing. Also, what are these three elements?
14:40:40 <quintinb> shoobe01 keyboards are not the only a11y interface, as dynamic as they are. We should talk about the types of devices
14:45:52 <JJ> q?
14:46:25 <JJ> Poll: Broaden keyboard interface in 2.1.1 and 2.1.2 to accessibility interface to include more types of assistive technologies?
14:46:35 <shoobe01> +1
14:46:39 <tayef> +1
14:46:47 <Tim> +1
14:46:52 <Joe_Humbert> +1
14:46:54 <JatinV> +1
14:47:29 <quintinb> +1
14:47:36 <pauljadam> 0
14:48:05 <JJ> Results: 6x +1 and 1x 0 -> mostly positive
14:48:19 <JJ> ACTION: Broaden keyboard interface in 2.1.1 and 2.1.2 to accessibility interface to include more types of assistive technologies
14:48:27 <quintinb> I would like to hear from pauljadam - he's the Keyboard King
14:49:13 <quintinb> pauljadam not sure I'm informed enough to vote, but I think I would keep it as keyboard
14:50:07 <JJ> move to next agendum
14:50:07 <Zakim> agendum 3 -- Mobile operating system -- taken up [from JJ]
14:50:20 <JJ> https://github.com/w3c/matf/issues/102
14:52:29 <shoobe01> q+
14:52:33 <quintinb> Does TV and XR have guidance?
14:52:45 <quintinb> XR= Extended Reality
14:52:53 <JJ> ack shoobe
14:52:58 <Joe_Humbert> quintinb XR has some guidance
14:54:04 <quintinb> shoobe01I like the focus  - but the touch aspect as being the differentiator could be a problem for OS's like Windows
14:54:18 <quintinb> Don't worry shoobe01, in a year everyone will be on linux
14:54:49 <JJ> not "primarily touch based" but something along the lines of "supports touch based"
14:55:02 <quintinb> As long as we don't get "touchy"
14:55:04 <JJ> move to next agendum
14:55:04 <Zakim> agendum 4 -- Set of Webpages -- taken up [from JJ]
14:55:33 <JJ> ACTION: Create guide for Pull Request / Content creation for MATF
14:55:39 <Joe_Humbert> quintinb TV is more a wild west and has some guidance from individual manufacturers directly to devs. But many TV apps are "Webviews" (native app wrapping an all HTML content. Example: YouTube)
14:56:16 <JJ> https://github.com/w3c/matf/issues/11#issuecomment-3717960911
14:56:26 <JJ> Set of Pages seems pretty much good to go
14:56:32 <JJ> move to next agendum
14:56:34 <Zakim> agendum 5 -- Page Titled -- taken up [from JJ]
14:56:42 <JJ> https://github.com/w3c/matf/issues/9#issuecomment-3504088263
14:57:01 <quintinb> Joe_Humbert thanks - yeah I know Spotify implemented a lot of TV stuff in Web because there was too much to support regarding "TV" - e.g. Playstation, etc
14:59:50 <quintinb> <3
15:00:21 <JJ> rrsagent, make minutes
15:00:23 <RRSAgent> I have made the request to generate https://www.w3.org/2026/02/18-matf-minutes.html JJ
15:01:43 <JJ> rrsagent, bye
15:01:43 <RRSAgent> I see 2 open action items saved in https://www.w3.org/2026/02/18-matf-actions.rdf :
15:01:43 <RRSAgent> ACTION: Broaden keyboard interface in 2.1.1 and 2.1.2 to accessibility interface to include more types of assistive technologies [1]
15:01:43 <RRSAgent>   recorded in https://www.w3.org/2026/02/18-matf-irc#T14-48-19
15:01:43 <RRSAgent> ACTION: Create guide for Pull Request / Content creation for MATF [2]
15:01:43 <RRSAgent>   recorded in https://www.w3.org/2026/02/18-matf-irc#T14-55-33