E-mail List Archives
Thread: Mobile App Accessibility
Number of posts in this thread: 11 (In chronological order)
From: McDonald, Jennifer
Date: Fri, May 20 2011 2:33PM
Subject: Mobile App Accessibility
No previous message | Next message →
Hi everyone,
Does anyone have any information about best development practices when
creating a native mobile app? I understand that devices either include
accessibility software, or software can be purchased for them, but what
can be done on a development side to make sure that the application
works well with the accessibility functions of the device. I haven't
been able to find any information online regarding this yet.
Thank you,
Jeni McDonald
--------------------------------------------------------------------------------
The information contained in this communication may be confidential, is intended
only for the use of the recipient(s) named above, and may be legally
privileged. If the reader of this message is not the intended recipient, you
are hereby notified that any dissemination, distribution, or copying of this
communication, or any of its contents, is strictly prohibited. If you have
received this communication in error, please notify the sender immediately and
destroy or delete the original message and any copy of it from your computer
system. If you have any questions concerning this message, please contact the
sender.
================================================================================
From: Léonie Watson
Date: Fri, May 20 2011 2:48PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Jeni McDonald wrote:
"Does anyone have any information about best development practices when creating a native mobile app?"
You didn't mention which variety of native app, but an article I wrote a little while ago covers some of the basics for iOS app accessibility:
http://www.nomensa.com/blog/2011/ios-app-accessibility/
Regards,
Léonie.
--
Nomensa - humanising technology
Léonie Watson, Director of Accessibility & Web Development
tel: +44 (0)117 929 7333
twitter: @we_are_Nomensa @LeonieWatson
From: Patrick Burke
Date: Fri, May 20 2011 3:00PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Hi Jenni,
W3C documents may be daunting, but they do address this issue directly.
Mobile Web Application Best Practices
http://www.w3.org/TR/mwabp/
Relationship between Mobile Web Best Practices (MWBP) and Web Content
Accessibility Guidelines (WCAG):
http://www.w3.org/TR/mwbp-wcag/
Maybe not an ideal start, but worth a shot.
Patrick
At 01:26 PM 5/20/2011, McDonald, Jennifer wrote:
>Hi everyone,
>
>Does anyone have any information about best development practices when
>creating a native mobile app? I understand that devices either include
>accessibility software, or software can be purchased for them, but what
>can be done on a development side to make sure that the application
>works well with the accessibility functions of the device. I haven't
>been able to find any information online regarding this yet.
>
>Thank you,
>
>Jeni McDonald
>
>
--
Patrick J. Burke
Coordinator
UCLA Disabilities &
Computing Program
Phone: 310 206-6004
E-mail: burke <at> ucla. edu
Department Contact: = EMAIL ADDRESS REMOVED =
From: Pratik Patel
Date: Sat, May 21 2011 5:27AM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Jeni McDonald wrote:
"Does anyone have any information about best development practices when
creating a native mobile app?"
For Apple iOS devices, you will find Apple's Human Interface Design
guidelines to be extremely useful.
http://developer.apple.com/library/ios/#documentation/UserExperience/Concept
ual/MobileHIG/Introduction/Introduction.html
For Android, the accessibility API reference is useful.
http://developer.android.com/guide/practices/design/accessibility.html
Window Phone 7 does not yet have accessibility guidelines or API's. However,
in general, using native tools and native controls for developing apps is a
good start.
Pratik
From: Jim Allan
Date: Sat, May 21 2011 7:27PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Note: for android. at a workshop at SXSW a google representative
stated that there is no requirement that the hardware platforms
include the accessibility API in the core of the OS. So it depends on
the phone and version as to whether the A11y API is installed. Writing
an accessible app on android may or may not work for the end user.
Jim
On Sat, May 21, 2011 at 6:18 AM, Pratik Patel < = EMAIL ADDRESS REMOVED = > wrote:
> Jeni McDonald wrote:
> "Does anyone have any information about best development practices when
> creating a native mobile app?"
>
> For Apple iOS devices, you will find Apple's Human Interface Design
> guidelines to be extremely useful.
> http://developer.apple.com/library/ios/#documentation/UserExperience/Concept
> ual/MobileHIG/Introduction/Introduction.html
>
> For Android, the accessibility API reference is useful.
> http://developer.android.com/guide/practices/design/accessibility.html
>
> Window Phone 7 does not yet have accessibility guidelines or API's. However,
> in general, using native tools and native controls for developing apps is a
> good start.
>
> Pratik
>
>
From: Pratik Patel
Date: Sat, May 21 2011 7:36PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Jim Wrote:
Note: for android. at a workshop at SXSW a google representative
stated that there is no requirement that the hardware platforms
include the accessibility API in the core of the OS. So it depends on
the phone and version as to whether the A11y API is installed. Writing
an accessible app on android may or may not work for the end user.
While Android's accessibility is certainly variable, the accessibility API
is not. The accessibility API is included in all Android experiences because
it's a part of the core. Google does not guarantee that the screen reader
and other access software developed by Google staff is included in the OS.
It is available to download from the Market as separate products.
That being said, Google's accessibility API is limited for now. There is
significant functionality that is lacking. Things such as focus are not
available for developers to tap into. Implementation of this API in apps
does make these apps more accessible. There are clear limitations to
Android; but apps can be made to be more accessible.
Regards,
Pratik
From: YOUNGV5
Date: Mon, May 23 2011 9:21AM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
The following PDF touches on accessibility for IOS (if it is inaccessible
I apologize for the author):
http://www.stanford.edu/class/cs193p/cgi-bin/drupal/system/files/lectures/Accessibility.pdf
I got this from the Stanford on-line IOS development course.
Vincent Young
Accessibility Manager
User Experience Team
Nationwide®
o | 614·677·5094
c | 614·607·3400
e | = EMAIL ADDRESS REMOVED =
From:
Léonie Watson < = EMAIL ADDRESS REMOVED = >
To:
WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Date:
05/20/2011 04:50 PM
Subject:
Re: [WebAIM] Mobile App Accessibility
Sent by:
= EMAIL ADDRESS REMOVED =
Jeni McDonald wrote:
"Does anyone have any information about best development practices when
creating a native mobile app?"
You didn't mention which variety of native app, but an
article I wrote a little while ago covers some of the basics for iOS app
accessibility:
http://www.nomensa.com/blog/2011/ios-app-accessibility/
Regards,
Léonie.
--
Nomensa - humanising technology
Léonie Watson, Director of Accessibility & Web Development
tel: +44 (0)117 929 7333
twitter: @we_are_Nomensa @LeonieWatson
From: McDonald, Jennifer
Date: Tue, May 24 2011 10:12AM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Thanks for the article. That was very helpful. We're looking into releasing apps in these varieties - iPhone, Android, Blackberry.
From: Paul.Adam
Date: Wed, May 25 2011 4:09PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Thanks for the Stanford link. I need to watch the video that goes along with it. I wanted to comment on this subject because mobile is one of the most exciting areas in accessibility for me currently. That and I'm hooked on all these iDevices.
I actually just gave a presentation on iPhone/iPad Web & App Accessibility at the annual AccessU accessibility conference by Knowbility in Austin, TX. It was lots of fun and I did a ton of research on everything iAccessibility.
Some topics I discussed are:
Screen Reader Costs on Smart Phone Platforms
CAPTCHA
HTML5 A11y
ARIA Support on iOS
Native App Accessibility in Xcode
iTunes
iBooks
AppleTV
http://pauljadam.com/presentations/accessu2011/index.html
Feel free to share the link with anyone interested. Right now iOS is the only truly accessible mobile platform that comes at no additional costs. I love that principle.
Paul Adam
Accessibility Specialist
Center for Policy and Innovation
= EMAIL ADDRESS REMOVED =
From: John E Brandt
Date: Thu, May 26 2011 2:21PM
Subject: Re: Mobile App Accessibility
← Previous message | Next message →
Thanks for sharing this Paul. Massive amount of work!
I hope iOS developers will use this to build/re-build more accessible apps.
I had to chuckle at your directions for building accessible e-pub doc. Sure
wish Apple would just add the capacity to add ALT text to images.
Thanks for references to accessibility issues for more than just screen
reader users.
Also, thanks for the reference to Calibre - awesome.
John E. Brandt
www.jebswebs.com
= EMAIL ADDRESS REMOVED =
207-622-7937
Augusta, Maine, USA
From: Joshue O Connor
Date: Tue, May 31 2011 1:18AM
Subject: Re: Mobile App Accessibility
← Previous message | No next message
On 26/05/2011 21:20, John E Brandt wrote:
> Thanks for sharing this Paul. Massive amount of work!
Yes, thanks Paul! Your presentation is a really useful resource in
itself :-)
Cheers
Josh
NCBI: Celebrating 80 Years
********************************************************************
National Council for the Blind of Ireland (NCBI) is a company
limited by guarantee (registered in Ireland No. 26293) .
Our registered office is at Whitworth Road, Drumcondra, Dublin 9.
NCBI is also a registered Charity (chy4626).
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************