– DRAFT –
MATF 18 February 2026

<shoobe01> Nope, changed audio for a thing and I broke it. NM for now.

<shoobe01> I'll type and you can catch up while I work it out

Software layers (User Agent, Platform Software, etc.)

<JJ> https://miro.com/welcomeonboard/R0dUeHp3dUd1Nmp4ZG5lWVo4eG5kekY4dHlTbHZWMzh2TS91WTZJSTRQTDJYKzVTd3Q3RU9KSC9RMGRJN1lrM3dCRnBHdDRrRHhNVkxrWEZ5ZGh6TVpsVnVJY2tXR2hwVm5GU3Y4VFJramI1bjgyNmdBcmd3WG9zemRZRkR1cU9hWWluRVAxeXRuUUgwWDl3Mk1qRGVRPT0hdjE=?share_link_id=386230017222

<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

Actually live captions are pretty great just for being able to catch up

<shoobe01> My brain is on several tracks so I love having the full transcript, often go back and forth reading it during the meeting.

<JJ> Diagram from W3C: https://www.w3.org/WAI/fundamentals/components/

Oooh I like that diagram

<shoobe01> I have tossed it and the link to source into the MIro so we can discuss live as the other diagrams are.

yay!

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

^ shoobe01

shoobe01 we could just let it be complicated. Isn't a web view on top of the app? Are these layers ordered correctly?

Keyboard interface + Accessibility interface + Virtual keyboard

I find it interfacing

<JJ> Keyboard interface: w3c/matf#66 (comment)

<JJ> Accessibility interface: w3c/matf#247 (comment)

<JJ> Virtual keyboard: w3c/matf#91 (comment)

quintinb: So the A11y interface is to ensure all assistive tech is represented in the success criteria?

<JJ> https://www.w3.org/TR/wcag2ict-22/#keyboard

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?

shoobe01 keyboards are not the only a11y interface, as dynamic as they are. We should talk about the types of devices

<JJ> Poll: Broaden keyboard interface in 2.1.1 and 2.1.2 to accessibility interface to include more types of assistive technologies?

<shoobe01> +1

<tayef> +1

<Tim> +1

<Joe_Humbert> +1

<JatinV> +1

<quintinb> +1

<pauljadam> 0

<JJ> Results: 6x +1 and 1x 0 -> mostly positive

ACTION: Broaden keyboard interface in 2.1.1 and 2.1.2 to accessibility interface to include more types of assistive technologies

I would like to hear from pauljadam - he's the Keyboard King

pauljadam not sure I'm informed enough to vote, but I think I would keep it as keyboard

Mobile operating system

<JJ> w3c/matf#102

Does TV and XR have guidance?

XR= Extended Reality

<Joe_Humbert> quintinb XR has some guidance

shoobe01I like the focus - but the touch aspect as being the differentiator could be a problem for OS's like Windows

Don't worry shoobe01, in a year everyone will be on linux

<JJ> not "primarily touch based" but something along the lines of "supports touch based"

As long as we don't get "touchy"

Set of Webpages

ACTION: Create guide for Pull Request / Content creation for MATF

<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)

<JJ> w3c/matf#11 (comment)

<JJ> Set of Pages seems pretty much good to go

Page Titled

<JJ> w3c/matf#9 (comment)

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

<3