– DRAFT –
MATF 10 December 2025

<JJ> Virtual keyboard

Mobile operating systems

<JJ> w3c/matf#102

JJ: discussing the question about which operating systems are considered for this guidance

JJ: should we say specific operating systems like android and iOS or should it be broader, there was a suggestion to avoid specifying operating systems

JJ: we could mention specific operating systems in definitions relating to a11y support on that platform

JJ: may mention some specific behaviors of operating systems

JJ: reading all the different types of mobile operating systems like android, iOS, iPadOS, chromeos, harmony, ubuntu touch, feature phones, windows, game devices?

JJ: our group has focused on mostly android, iOS, iPad os

JJ: discussions about potential wearables like watch os

<JJ> w3c/matf#281

JJ: related issue linked above

JJ: question asking for clarification on specific range of devices, asking If we are covering watches, tablets, and non-traditional devices

JJ: mobile os needs to be defined, and we need to mention that our focus has been android iOS and iPad, and we have not considered certain type of mobile os

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

Tanya: asking what should be included because when the MATF started, it's a question of phrasing we should add something general what is expected that we tried to apply this criteria on a broad range of OS but we focused on the 2 main OS android and iOS because they are most widely used

JJ: WCAG2ICT introduced the term platform software

JJ: reading examples of platforms, desktop, mobile, embedded, web browser, plugins

JJ: we might also need mobile operating system definition and have a note about what platform software we have considered in our guidance, platform software is used 57 times in the WCAG2ICT guidance

JJ: term operating system is used in the platform software example, used in Reflow, keyboard has reference to operating systems, in multiple ways, pointer cancellation, css pixels, applying to non web documents and software, we can reuse this platform software term

JJ: 2 people have raised the issue that it is not clear which devices or OS are considered in our guidance so we need to mention it somewhere in our document where people would read it to end the confusion

JJ: need to figure out where to put the clarification

Joe_Humbert: put it in the introduction where that is the place it would be most read other than in the SC

Joe_Humbert: or include in into but not directly by including reference to platform software in the intro and linked

Joe_Humbert: wording "we focused on android and iOS but this guidance can apply to any mobile os that works like these and it primarily touch base"

Joe_Humbert: chrome os does not operate on phones and is not touch, it's desktop like chrome books likes steam os

Joe_Humbert: any operating system that supports touch input could complicate our guidance with too many to consider

JJ: Background, guidance in document section could be potential spot to put, or excluded from scope to list what we consider out of scope

JJ: mention what is out of scope during our discussions but does not mean it does not apply to that os

Tanya: question about definition of SC, looking at WCAG3 some times because we are trying to make WCAG 2 more applicable to mobile apps, but WCAG 3 will be coming at some point and they will look at our work

Tanya: if we're looking into WCAG 3 they dont have a definition of platform software

Tanya: is it good to look at WCAG 3 to reference definitions there ?

<JJ> https://w3c.github.io/wcag3/guidelines/#dfn-platform

JJ: WCAG 3 is tricky, now they have a platform definition, look at the future where WCAG 3 is heading,

JJ: they just call it platform

JJ: software or collection of layers of software which is vague

JJ: subject software is a new term

JJ: they do have 2 references to relying on operating system and example of one

rachaely: like what Joe said about message that we focus on android and iOS and iPad os

rachaely: also TV operating system

rachaely: maybe make primary is the touch interface which differences between a TV ok that uses a remote control to operate

JJ: could mention forks of android like android TV or android Car might share same things to make it accessible

JJ: agree add that we focus on primary touch input

I wonder more about watch or if we just say all iOS guidance applies to Apple Watch too?

Detlev: many of the terms like platform definitions will still be changing because its still an early working draft may things still under discussion with WCAG 3 so we should not really reference it, we can keep our definitions for now and then change later

JJ: what will happen to MATF in the future and WCAG 2 MOBILE

JJ: ideally in WCAG 3 it will be written so we dont need different guidance to apply to mobile

JJ: at TPAC they were evaluating what task forces need to be extended and did see the need to extend mobile a11y task force

JJ: more collaboration with us to give input on mobile part coming up

JJ: take 5 to 10 years to finish WCAG 3

JJ: and more years before it is law and more years before people actually use it, very far out

JJ: until then we use WCAG 2.2

JJ: we tell people how to interpret WCAG 2.2 and align as closely as possible to WCAG2ICT

JJ: put the in the introduction were we say what mobile os apply to our guidance

<JJ> github.com/w3c/matf/issues/91

JJ: WCAG2ICT virtual keyboard

JJ: on-screen keyboard full keyboard access android iOS, what is a virtual keyboard

JJ: can we use virtual keyboard definition or do we need to modify

<JJ> https://w3c.github.io/wcag2ict/#dfn-keyboard-interface

JJ: keyboard interface definition can be confusing with virtual keyboard etc.

JJ: keyboard interface definition

JJ: note 2 references virtual keyboard definition

JJ: do we need to modify virtual keyboard def or can we just apply it as is

<JJ> Poll: Keep virtual keyboard definition as is?

<Detlev> 0

<rachaely> 0

<Tanya> 0

<Joe_Humbert> -1

<tayef> 0

Joe_Humbert: concerned about it saying any software that acts as keyboard is too vague

Joe_Humbert: very complex definition may be fine as is but concern its too broad

JJ: interesting they mention software but then say switches which is hardware

Detlev: we do check that everything works with an external keybaord

Detlev: the note may give wrong signal that we dont need to support keyboard

Detlev: risk that people thing we only need virtual keyboard and not hardware keyboard

I agree

<JJ> Note 2 in https://w3c.github.io/wcag2ict/#applying-keyboard-interface-to-non-web-documents-and-software

Detlev: their note may be about kiosk or moving a virtual mouse to use a virtual keyboard or using a hardware wheel thing might be their reason

Joe_Humbert: might need to just remove because cant think of mobile os where we would not want to support keyboard interface, would be like switches

Joe_Humbert: for kiosks if there is no keyboard and if there is another mouse pointer if that's how there is input and there is no text input but for us there is always a need regardless of device to support a hardware keyboard or keyboard interface or virtual keyboard in some way

JJ: our target OS has a11y layer or a11y events so our guidance may be different

JJ: making note about directly su port a keybaord

<JJ> note 2 of keyboard interface is copied from note 4 for 2.1.1 - https://w3c.github.io/wcag2ict/#applying-sc-2-1-1-keyboard-to-non-web-software

I agree we need to emphasize that keyboard requires hardware keyboard support or devices like switch etc.

Detlev: get clarity on optional virtual keyboard, dont think virtual keyboard can meet keyboard SC

Detlev: because you operate it with touch

Detlev: we need keyboard keyboard interface and virtual keyboard is out side of that

I agree virtual keyboard is not hardware keyboard

Detlev: make sure people can't pass by only having an on screen keyboard need to be clear they need hardware keybard

JJ: making action about this

ACTION: Check if we can remove note 2 from keyboard interface? Do we need virtual keyboard at all?

Cross-platform framework

<JJ> w3c/matf#84

JJ: need definition for cross platform framework

JJ: mostly for exceptions

JJ: clarify things for layers where developers write layer of code, flutter, flutter then makes iOS or Android app

JJ: responsibility for defect but in cross platform framework is that acceptable in audit

JJ: who gets a pass dev or no or what

JJ: is it platform software os framework layer above that might not support and who is responsible here for the defect basically

JJ: end users would not be able to use feature because of decision to use cross platform

JJ: this is about one code base that renders across different platforms to a native app

JJ: flutter might draw all UI elements, others might render native components, both creat ea native app, also compose multi platform etc. some make <canvas> and fully draw their custom UI

<JJ> w3c/matf#270 (comment)

JJ: underlaying layer

JJ: os lowest layer

JJ: operating system, native app, native app might host view from cross platform framework

JJ: relationships between cross platform and underlying layer definition and user agent exceptions platform software that might be exempt for certain things like non text contrast

JJ: mention some of the frameworks but where do it do it and how does it relate to our guidance

JJ: could be part of underling layer

JJ: where as a group do we benefit to put it

JJ: cros platform dont always have best a11y support

JJ: how to we help people who want to make those apps accessible e

rachaely: if cross platform framework may not have access to certain a11y API, usually they can write a native component and workaround their bad cross platform framework support, so developer should still be accountable because they use flutter they should not have a get out of jail free card

JJ: just like on web if you choose an framework with a 11y issues then you are still required to fix or workaround them

JJ: thinks its fair to require developers to work around cross platform framework a11y fails

Tanya: developers would like to often use exceptions to get out of cross platform a11y work they would have to do

Tanya: developers should solve the a11y issues on the cross platform frameworks

Tanya: if dev company has flutter app and wants to claim conformance they should have zero issues in audit and if flutter is the framework problem and dev cant fix then like keyboard focus issue on iOS full keyboard access was not working in flutter but flutter dev could not solve that

Tanya: they can only ask flutter to fix but that is long process and difficult

JJ: if something not a11y supported like can't mark heading in flutter or bug in android then maybe developer written native code and android causes the bug

JJ: in flutter if you make a heading recent change it broke the behavior

JJ: recent flutter apps may not have headings because flutter bug

JJ: how do yo deal with this in audit who is the cause of the problem dow we only account for certain layers like os or what

😅

JJ: cancelled meeting on December 24 and 31

JJ: next meeting is next week final for this year

<JJ> s///

<JJ> s|s/Virtual keyboard||

<JJ> s|s/Virtual keyboard//||