Re: Applicability of few WCAG 2.1 SC’s for Native mobile apps:

Hi Ramakrishnan,

In general I like Jonathan's suggestion about EN 301 549 Annex C, but in
this case it doesn't add any hints for your specific questions. For
example, EN 301 549 Annex C clause C.11.1.3.5.1 offers only this test
procedure: "Check that the software does not fail WCAG 2.1 Success
Criterion 1.3.5 Identify Input Purpose." We end up returning to WCAG itself
for all three of your specific questions.

For WCAG 1.3.4 Identify Input Purpose, the first thing to ask is whether
the native software platform has "support for identifying the expected
meaning for form input data." In my experience no native software platforms
offer such support, so 1.3.5 always passes for native software. (I wonder,
are any developers of operating systems and native software technologies
working on adding this support?)

WCAG 1.4.12 Text Spacing is limited to "content implemented using markup
languages that support the [enumerated] text style properties". The WCAG
"Understanding" doc and further discussion in Github issue 884
<https://github.com/w3c/wcag/issues/884> address the question of author
responsibility vs. user responsibility. I conclude that 1.4.12 gets a
technical pass in this common scenario: (1) the native software contains a
web view, implemented using a markup language; and (2) the software, acting
as a user agent, does not give users a mechanism to adjust the text style
properties.

For WCAG 1.4.10 Reflow, I agree with Marc Haunschild's evaluation technique
for native apps on a phone. However, the evaluation technique is less clear
for a tablet app (and for desktop native apps for that matter). Here again
I look to the Understanding doc and relevant Github issues
<https://github.com/w3c/wcag/issues?q=is%3Aissue+1.4.10>.

Mitchell Evan
+1 (510) 375-6104
mtchllvn@gmail.com
Twitter @mitchellrevan
https://www.linkedin.com/in/mitchellrevan/


On Thu, Jul 9, 2020 at 12:01 PM Gijs Veyfeyken <gijs@anysurfer.be> wrote:

> Hi,
>
> In case you're having a hard time finding it. The link to the standard (in
> PDF) is
>
> https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.01.01_60/en_301549v030101p.pdf
>
> Kind regards,
>
> Gijs
>
> Op 7 jul. 2020, om 16:28 heeft Jonathan Avila <jon.avila@levelaccess.com>
> het volgende geschreven:
>
> It may be helpful to look at these criterion in terms of the standards
> such as EN 301 549 v 3.1.1 that apply them to native mobile apps.  That
> standard has a Annex C which provides test procedures and addresses
> inapplicability specific items.
>
> Jonathan
>
> -----Original Message-----
> From: Marc Haunschild <haunschild@mhis.onmicrosoft.de>
> Sent: Tuesday, July 7, 2020 8:52 AM
> To: Ramakrishnan Subramanian <ram.eict2013@gmail.com>; w3c-wai-ig@w3.org
> Subject: Re: Applicability of few WCAG 2.1 SC’s for Native mobile apps:
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Because nobody answered yet a brief answer from me:
>
> The WCAG is not limited to certain techniques.
>
> If your App has to be WCAG compliant, it must meet all criterions.
>
> How to request these requirements? Change text spacing, open your App on a
> 320px wide device (reflow) and so on...
>
> On 07.07.20, 06:04, "Ramakrishnan Subramanian" <ram.eict2013@gmail.com>
> wrote:
>
>    Dear Members,
>    I request your thoughts on the applicability of the following SC’s for
>    a Native mobile app in both IOS and Android platforms.
>    1.3.5 Identify Input Purpose (AA)
>    1.4.10 Reflow (AA)
>    1.4.12 Text Spacing (AA)
>    1. Whether these apply to native mobile app?
>    2. If Yes, how does one validate a mobile app against the requirements
>    of these SC’s?
>    3. How to meet the requirements?
>
>
>
>
>
>
>
>    --
>
>    Thanks and Regards
>    Ramakrishnan
>
>
>
>