E-mail List Archives
Thread: SC 3.2.2 and native mobile apps
Number of posts in this thread: 6 (In chronological order)
From: Geethavani.Shamanna
Date: Tue, Mar 14 2023 1:55PM
Subject: SC 3.2.2 and native mobile apps
No previous message | Next message →
Hello all,
The native mobile app I am currently testing contains a Sort button. On activating it, radio buttons are presented to sort courses by code, course name, etc. Using VoiceOver, On double-tapping to select the desired radio button, focus automatically shifts to the course list, presented in the selected sort order.
Does SC 3.2.2 (on input) apply to native mobile apps as well? Ideally the app should provide an Apply button to apply the selection, or present the sort options in a picklist.
Many thanks.
Geetha
From: Patrick H. Lauke
Date: Tue, Mar 14 2023 8:14PM
Subject: Re: SC 3.2.2 and native mobile apps
← Previous message | Next message →
On 14/03/2023 19:55, Geethavani.Shamanna wrote:
[...]
> Does SC 3.2.2 (on input) apply to native mobile apps as well?
What makes you think that it doesn't?
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Mosley, Leigh
Date: Wed, Mar 15 2023 6:22AM
Subject: Re: SC 3.2.2 and native mobile apps
← Previous message | Next message →
I have often wondered about this as well. If a native app isn't built using web-based programming languages, does it fall under a Web Content Accessibility Guideline? And if it does, how can I really evaluate it without access to the code behind the application?
Leigh Mosley
Accessibility Coordinator
University of Tennessee Libraries
1015 Volunteer Boulevard
Knoxville, TN 37996-1000
865-974-0011
= EMAIL ADDRESS REMOVED =
From: Sean Murphy
Date: Wed, Mar 15 2023 7:46AM
Subject: Re: SC 3.2.2 and native mobile apps
← Previous message | Next message →
Yes it does and does desktop apps
My experience is the part
> On 15 Mar 2023, at 11:23 pm, Mosley, Leigh via WebAIM-Forum < = EMAIL ADDRESS REMOVED = > wrote:
>
> I have often wondered about this as well. If a native app isn't built using web-based programming languages, does it fall under a Web Content Accessibility Guideline? And if it does, how can I really evaluate it without access to the code behind the application?
>
>
> Leigh Mosley
> Accessibility Coordinator
> University of Tennessee Libraries
> 1015 Volunteer Boulevard
> Knoxville, TN 37996-1000
> 865-974-0011
> = EMAIL ADDRESS REMOVED =
>
>
>
>
From: Patrick H. Lauke
Date: Wed, Mar 15 2023 7:53AM
Subject: Re: SC 3.2.2 and native mobile apps
← Previous message | Next message →
On 15/03/2023 13:46, Sean Murphy wrote:
> Yes it does and does desktop apps
Or, perhaps more accurately, WCAG is applied in principle even to
software/ICT that WCAG was not originally meant to cover.
https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: glen walker
Date: Wed, Mar 15 2023 8:54AM
Subject: Re: SC 3.2.2 and native mobile apps
← Previous message | No next message
Similar to Patrick's link but a bit older. It refers to WCAG 2.0.
"Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to
Mobile"
https://www.w3.org/TR/mobile-accessibility-mapping/
On Wed, Mar 15, 2023 at 7:53 AM Patrick H. Lauke < = EMAIL ADDRESS REMOVED = >
wrote:
>
> Or, perhaps more accurately, WCAG is applied in principle even to
> software/ICT that WCAG was not originally meant to cover.
>
> https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/
>
> P
> --
> Patrick H. Lauke
>
>