WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Android app recorder focussing issue - which WCAG Success Criterion?

for

From: Patrick H. Lauke
Date: Oct 13, 2016 4:33AM

I usually report issues relating to focus being moved incorrectly, not returning to the right place after a change, etc as failures under 2.4.3 as well.

May not be explicitly outlined in 2.4.3, but there IS a set of sufficient techniques relating to "Changing a Web page dynamically", which I take to then cover these scenarios.

P
--
Patrick H. Lauke


> On 13 Oct 2016, at 11:31, Detlev Fischer < <EMAIL REMOVED> > wrote:
>
> Hi,
>
> another question to WCAG testers. An Android recording app has focusable controls when using TalkBack. Once you start a recording, the auto-updating display of time elapsed (or something else) seems to remove focus at close intervals so you can't swipe to the stop button in a predictable way - you only get to activate it by chance.
>
> What SC would you call?
>
> 2.4.3 Focus order?
> 2.1.1 Keyboard (extended to 'touch with AT')?
> 2.2.2 Pause, stop, hide?
>
> All of them seem affected but none of them seem entirely appropriate seen from the main focus of the SC.
>
> 2.4.3: The focus order ist OK in principle.
> 2.1.1: All items can in prinmciple be activated via swipe and double tap
> 2.2.2 There *is* a way to stop the movement (wave display / incrementing timer) which in the case of the recorder is actually essential to the function.
>
> An added compication that finding and activating the stop button via touch explore works.
> Any thoughts?
>
> Thanks in advance,
> Detlev
>
>
>
> --
> Detlev Fischer
> testkreis c/o feld.wald.wiese
> Thedestr. 2, 22767 Hamburg
>
> Mobil +49 (0)157 57 57 57 45
> Fax +49 (0)40 439 10 68-5
>
> http://www.testkreis.de
> Beratung, Tests und Schulungen für barrierefreie Websites
> > > >