Meeting minutes
3.1.1 Language of Page proposal
<JJ> Code for Android to set accessibility language: https://
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.
*respected
<JJ> https://
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.
@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.
<pauljadam> locale is android term
<pauljadam> I'm not sure we need to talk about how you set the language, just that you do set the language
<JJ> 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.
Locale is an iOS term
<JJ> https://
<JJ> https://
<pauljadam> Ok I guess I was not thinking about Locale on iOS becaues the property you use is called .languageIdentifier()
2.5.7 Dragging Movements proposal
<pauljadam> Does Locale on iOS make VoiceOver speak the proper synthesizer? I've not tried it before I don't think.
<JJ> @pauljadam - yes it does if you set it at UIApplication level
shoobe01 Single pointer is a weird term. Is this useful to inherit?
<pauljadam> Thanks! I need to make a technique / demo on Locale then :)
<JJ> https://
<pauljadam> Single pointer is a finger or a mouse or a stylus, Pointer Events is a web term also
I had always understood 'finger tap' to be included in 'single pointer'
<pauljadam> That's why they call it your "Pointer Finger" :)
JJ WCAG2ICT "Single pointer" definition specifies a single finger tap.
<JJ> move to the next agendum
2.4.11 Focus Not Obscured (Minimum) proposal
pauljadam SC only says keyboard focus, not AT. AT can focus on things keyboards can't and uses a separate focus engine.
<pauljadam> You don't need something to be keyboard accessible for it to be screen reader operable on a web site
<pauljadam> Some WCAG SCs say "focus" only like On Focus and then some say "keyboard focus" specifically like Focus Not Obscured.
Joe_Humbert The SC references 'Keyboard focus', it should be clear that this doesn't matter how keyboard focus is being done.
Good clarification, thanks pauljadam
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
Software layers
<JJ> 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
ACTION: Have a look at definition proposals at w3c/
2.5.8 Target Size (Minimum)
<pauljadam> 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
<pauljadam> 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 🤦🏻♂️
<JJ> https://
<JJ> Scoping Poll results: https://
<pauljadam> watch app uses the same code as a phone app
<shoobe01> Platforms for WCAG3 discussion https://