E-mail List Archives
Thread: Native Mobile apps and WCAG
Number of posts in this thread: 3 (In chronological order)
From: Birkir R. Gunnarsson
Date: Thu, Oct 06 2016 7:36AM
Subject: Native Mobile apps and WCAG
No previous message | Next message →
For those of you who have had to prepare arguments for making mobile
apps accessible, and what that means, how have you gone about it?
WCAG 2.0 is the only accessibility standard out there, really (at
least from a legal perspective), but it is designed for the web (most
of it can be applied to mobile apps, I am aware of the WCAG to ICT
project).
BBC also did fantastic work developing mobile accessibility gudelines,
but obviously that is not an official standard.
So if your client or your boss or even a colleague asks you if they
should make their mobile app accessible or just the responsive version
of their webpage, how would you convince them to do the mobile, and
how would you explain how WCAG works with OS guides.
Cheers
-B
--
Work hard. Have fun. Make history.
From: JP Jamous
Date: Thu, Oct 06 2016 7:46AM
Subject: Re: Native Mobile apps and WCAG
← Previous message | Next message →
It is an arm wrestle. I have dealtmobile app that has some parts that are inaccessible.
My only solution at this point is to follow UX standards and Section 508 of ensuring that any digital application must be accessible to comply with reasonable accommodations.
From: Jim Homme
Date: Mon, Oct 10 2016 2:47PM
Subject: Re: Native Mobile apps and WCAG
← Previous message | No next message
Hi,
Have you tried to bring in Section 508 Desktop standards to argue for using native controls and things like avoiding interfering with the accessibility features of the OS?
Thanks.
Jim
=========Jim Homme,
Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O