E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Detlev Fischer
Date: Tue, Oct 11 2016 8:04AM
Subject: Instructions for interaction covered by WCAG Success Criterion 3.3.2 Labels or Instructions?
No previous message | Next message →

WCAG testers: Just wondering whether you think on-screen hints for interaction in mobile apps (like 'swipe down with one finger to update content') would be covered by WCAG SC 3.3.2 Labels or Instructions. All examples in "Understanding" relate to input fields. In some cases (as when the screen reader is turned on) the gesture might not work, i.e. the instruction does not help. Would you call this a failure or an issue? If so, under which SC?

My current guess is that this issue is not really covered - maybe one can even expect SR users to know that such interaction hints do not apply to them as they use another two step interaction mode. A related issue is whether alternative ways would need to be available to activate the same thing (here, update content) that do not require users to carry out the gesture described.

--
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

From: Patrick H. Lauke
Date: Tue, Oct 11 2016 8:44AM
Subject: Re: Instructions for interaction covered by WCAG Success Criterion 3.3.2 Labels or Instructions?
← Previous message | Next message →

On 11/10/2016 16:04, Detlev Fischer wrote:
> WCAG testers: Just wondering whether you think on-screen hints for
> interaction in mobile apps (like 'swipe down with one finger to
> update content') would be covered by WCAG SC 3.3.2 Labels or
> Instructions. All examples in "Understanding" relate to input fields.
> In some cases (as when the screen reader is turned on) the gesture
> might not work, i.e. the instruction does not help. Would you call
> this a failure or an issue? If so, under which SC?
>
> My current guess is that this issue is not really covered - maybe one
> can even expect SR users to know that such interaction hints do not
> apply to them as they use another two step interaction mode.

The latter would be my interpretation/assumption.

> A
> related issue is whether alternative ways would need to be available
> to activate the same thing (here, update content) that do not require
> users to carry out the gesture described.

Currently I don't think this is covered (beyond making it "keyboard
accessible") in WCAG 2, hence why we're going to propose a new SC
relating to this in mobile a11y TF? ;)

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

From: Birkir R. Gunnarsson
Date: Sun, Oct 16 2016 12:19PM
Subject: Re: Instructions for interaction covered by WCAG Success Criterion 3.3.2 Labels or Instructions?
← Previous message | No next message

I have always wondered if we can stretch "2.1.1 - keyboard" to swipe getures.
Mobile accessibility is a tricky beast.


On 10/11/16, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = > wrote:
>
>
> On 11/10/2016 16:04, Detlev Fischer wrote:
>> WCAG testers: Just wondering whether you think on-screen hints for
>> interaction in mobile apps (like 'swipe down with one finger to
>> update content') would be covered by WCAG SC 3.3.2 Labels or
>> Instructions. All examples in "Understanding" relate to input fields.
>> In some cases (as when the screen reader is turned on) the gesture
>> might not work, i.e. the instruction does not help. Would you call
>> this a failure or an issue? If so, under which SC?
>>
>> My current guess is that this issue is not really covered - maybe one
>> can even expect SR users to know that such interaction hints do not
>> apply to them as they use another two step interaction mode.
>
> The latter would be my interpretation/assumption.
>
>> A
>> related issue is whether alternative ways would need to be available
>> to activate the same thing (here, update content) that do not require
>> users to carry out the gesture described.
>
> Currently I don't think this is covered (beyond making it "keyboard
> accessible") in WCAG 2, hence why we're going to propose a new SC
> relating to this in mobile a11y TF? ;)
>
> 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
> > > > >


--
Work hard. Have fun. Make history.