RE: MATF Minutes 20 October 2016

> I would think that this scenario would already currently fail 2.1.2 assuming that the carousel is operable with the keyboard, so I *think* this scenarios is already covered (at least in spirit) by 2.1.2 (but we may suggest, separately from actual new SC submission, to slightly broaden the definition of 2.1.2 for WCAG 2.1 to cover keyboard and AT focus rather than just keyboard focus?)

Yes, I think that is what I was getting at.  There might be a keystroke to get out of the trap but if that key is not available on mobile then you could be stuck.

Ultimately it's harder on the web to actually control AT focus as the swipe gestures are controlled by the AT -- so I think this is an edge case.

Jonathan


-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Thursday, October 27, 2016 5:53 PM
To: public-mobile-a11y-tf@w3.org
Subject: Re: MATF Minutes 20 October 2016

On 27/10/2016 17:09, Kim Patch wrote:

>       focus trap
>
> Kathy: Patrick's note – added to this but not sure it's needed ... 
> Detlev shares the concern as well ... thoughts on this. I don't think 
> I've come across a situation where this is a problem, but I wanted to 
> see if someone else has a scenario that's not covered
>
> David: several the success criterion's are largely theoretical. This 
> is in that category
>
> Kathy: Patrick's thought is to merge into 2.1.2
>
> Jon: in theory somehow controlling the screen reader's order
>
> Kathy: is there any situation whether we're talking about touch or 
> pointer or anything with or without AT where we could have a focus 
> trap that we need to solve ... is there a scenario where we actually 
> need this?
> ... Jon the scenario you mentioned, is that an iOS bug?
>
> Jon: yes. Another example. Carousel with hundreds of items or explore 
> by touch to get out of it. There may be some way to jump past it that 
> I can also envision a carousel that just keeps wrapping you around. 
> More of a native app problem. I'm willing to drop it – other issues more important.

I would think that this scenario would already currently fail 2.1.2 assuming that the carousel is operable with the keyboard, so I *think* this scenarios is already covered (at least in spirit) by 2.1.2 (but we may suggest, separately from actual new SC submission, to slightly broaden the definition of 2.1.2 for WCAG 2.1 to cover keyboard and AT focus rather than just keyboard focus?)


>  2. drop M7 No Focus Trap for 2.1
>     
> <https://www.w3.org/2016/10/27-mobile-a11y-minutes.html#resolution02>

Removed this one from the GitHub repo now.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com

twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Friday, 28 October 2016 14:04:40 UTC