Meeting minutes
present
Guidance plans
JJ has identified 3 sources of feedback: Sheets, Github and an earlier document
BIAK: Would prefer to follow the structure of the EN
Jamie: Since we're adding information that isn't present, we need to make sure that we include the the same criteria
Illai - we need to make sure we align with WCAG 3 since it's going to be so different
<Detlev> WCAG 3 - it will definitely longer than a couple of years...
<Mick> My vote would be to go based on the WCAG success criteria, breaking it down for each platform type. And add gaps covered in the EN guidelines.
<Jamie> +1 to Mick
<Jamie> and +1 to Illai after we publish this draft which is for WCAG 2.2
<Illai> +1 to Mick
Joe: The WG may push back if we don't follow their format
<Jamie> who approves this ultimately?>
<Detlev> https://
<Detlev> https://
These documents are being use to create understanding for web and apps
<Jamie> Detlev we are discussing WCAG 2.2 for the scope
1.3.4 Orientation - Level A
I looked up the reasons behind this criterion and I think that mobile should have this as is
Jamie: There seemed to be apprehension that it's difficult to do- and that people need to discuss it. Implementation struggles should work themselves out over time
It's not that native can't do it
<Mick> +1 Jamie - leave as is for native apps. Teams should be pushed more to do it.
Personal opinion: MVP's aren't designed for people, but for businesses
<Aashutosh> +1 to Joe
Are doing this to save business money?
Fair
I am worried about slippery slope "It's hard" can be translated to almost anything in accessibility
<Aashutosh> quintinb it does and I am facing it everyday!
Oh me too!
<Illai> w3c/
<JJ> Illai: Discussion on 1.3.4 ^
Illai - wcag group seemed to agree
+1 Illai - thanks for this!
JJ: Biggest problem in landscape is virtual keyboard takes up most of the screen
This is why you should design for accessibility, to be fair
iPhone currently doesn't support landscape in certain situations - I recommend we keep the guidance
JJ: Should we support upside down?
quintinb: +1 I think all the orientations
Jamie: iPhone just introduced phone mirroring - so you should be reorient and type in with other inputs
Jamie what do you mean by mirroring? I've been using QuickTime for years
Ok thanks - I'd love a link
Julian: Users may not pay attention to the specific direction of the phone
<Aashutosh> quintinb here is the link https://
Julian: Users may be confused
JJ: (Who uses a iPhone) had to specifically orientate his phone upside down couldn't
Joe: Keystroke passing may work similarly to ADB
<julianmka> Not to say that there aren't valid reasons to handle specific orientations - the Sonos example is a good one, or scanning a check for mobile deposit
2.1.1 Keyboard - Level A
Jamie - we are going through the SC's in alphabetical order
Jamie suggests we go through the SC on Github
<Jamie> @qinton never mind, no question
Detlev: Happy to put this on the back burner
Detlev: Do we need to confirm what is possible to require from platforms
Jamie: there is a gesture mode from full keyboard access
I am growing concerned that we're favouring platforms over people
<JJ> quintinb: passionate about supporting keyboard in WCAG/MATF for people that need to use it
<Jamie> +1 to Joe_Humbert
<julianmka> +1 Joe_Humbert
Joe_Humbert: It seems like Switch is more another interface. And there are differences between ipad and ios
Joe: The problem with cross platform is that they don't have the hooks they need
Joe: There are limited shortcuts on Android in comparison to iOS
Detlev: There needs to be better documentation
<Joe_Humbert> apple and google both need better documentation for users
<Jamie> +1 to @detlev
<Jamie> keyboard Gestures is hidden under "Commands"
Can the W3C mandate that?
There are commands to reveal the gestures
Both Android and iOS
Jamie: Would we be considering voice activation?
<julianmka> I'll bring my comment to the Github thread, gotta drop for a meeting now.
<JJ> Thanks julianmka!
<Joe_Humbert> possibly Jamie, but I have seen differences between switch and voice access ;-(
Proposal: Make guidance on discover methods
*discovery
JJ: We need to make sure that the AT is working
<Jamie> thanks all, have to drop
We may getting lost between the categories of platform vs applications
JJ: It needs to be reasonable