WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Any specific Guidance on evaluation methods for WCAG 2.1 SC on Native/hybrid mobile apps?

for

From: glen walker
Date: Sep 19, 2021 11:57PM

Many success criteria specifically mention "web" in the definition which
technically would rule out native apps. However, many of those SC would
still benefit native app users so it's still helpful to follow as much WCAG
as possible even if it implies the SC is for the web.

In your specific list, 1.3.5 says "The content is implemented using
technologies with support for identifying the expected meaning for form
input data." For native ios and android apps, you can often set the type
of field, such as plain text, numeric, email, phone number, so that the
appropriate onscreen keyboard displays but that's not exactly identifying
the input purpose. So those technologies don't have any support for 1.3.5

1.4.10 doesn't apply since you can't change your mobile device's viewport.

1.4.12 says "In content implemented using markup languages". While that
doesn't imply "web", most markup languages, such as HTML, are typically for
web. I suppose you could have the app written with something like React
Native, but that's essentially a javascript-like language and not really
considered a "markup" language, so it also wouldn't apply.

So your VPAT/ACR could have NA for those guidelines.

Note that the instructions for the ITIC VPAT also say you can put
"supports" instead of NA. It says:

"Note: When filling in the WCAG tables, a response may use 'Supports' where
one might otherwise be inclined to use 'Not Applicable'. This is in
keeping with WCAG 2.0 Understanding Conformance: This means that if there
is no content to which a success criterion applies, the success criterion
is satisfied."


On Sun, Sep 19, 2021 at 10:49 PM Ramakrishnan Subramanian <
<EMAIL REMOVED> > wrote:

> Hi
> I am sorry if the following topic is already discussed in this group.
> I tried searching in the archives but could not find the discussions
> happened on this topic.
> Any specific Guidance on evaluation methods for following WCAG 2.1 SC
> on Native/hybrid mobile apps? In case if there is no appropriate
> method to test these requirements how it is supposed to be mentioned
> in the ACR against these SC? Can it be marked as ‘NA" instead of ‘Not
> supported'?
> 1.3.5 Identify Input Purpose (AA)
> 1.4.10 Reflow (AA)
> 1.4.12 Text Spacing (AA)
>
>
>
>
>
> --
>
> Thanks and Regards
> Ramakrishnan
> > > > >