search

prabhjas / npr-android-app

Automatically exported from code.google.com/p/npr-android-app
0 stars 0 forks source link

all buttons in the app should be labelled to provide access for blind users #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 

Here is an accessibility complaint we have received from a blind listener (I 
have responded to the user with info on how to stop the streaming when they 
exit the app - although it is worth noting that this also further illustrates 
the confusion caused by not having a dedicated Exit button): 

"I am blind and use the accessibility settings on my device to interact with 
the phone. i am having some problems with this application. There are some 
unlabeled buttons that I cannot figure out what they do.  These need to be 
labeled according to the guidelines for accessibility.  The other concern is 
that I cannot stop a stream from within the application.  I am sure there is a 
way but it is not accessible using hardware keyboard navigation.  The only way 
I 
have found to stop a stream is to use the task killer application.
Other parts of the program seem accessible but I have only used it for a few 
hours.

For information on how to make this application accessible, see the Eyes-Free 
project on Google. I am a very devoted NPR listener and contributor since the 
first broadcasts.  I know NPR wants to include everyone, including people who 
are blind in its features and services.  Just a few minutes of programming will 
make this 
application one of the most accessible and, more importantly, useable for 
people who are blind.  There is a very active blind user community on the web 
and they keep a close watch on which applications are accessible.  I always 
look to NPR as a leader in the modern media and have faith that NPR's 
leadership will keep this role."

Original issue reported on code.google.com by jlucas....@gmail.com on 7 Apr 2011 at 7:39

GoogleCodeExporter commented 9 years ago 
Don't disagree with this, but have other issues that need to be addressed for 
larger segments of our audience. Will place in backlog.

Original comment by jpenn...@gmail.com on 19 May 2011 at 7:48

GoogleCodeExporter commented 9 years ago 
Guidelines here: 
http://developer.android.com/guide/topics/ui/accessibility/index.html

Original comment by jpenn...@gmail.com on 12 Apr 2012 at 7:10

GoogleCodeExporter commented 9 years ago 
Justin, can you give an LOE on this?

Original comment by jpenn...@gmail.com on 12 Apr 2012 at 8:46

GoogleCodeExporter commented 9 years ago 
Suggestion from twitter as to a method/standard to do this:

http://komodoopenlab.com/tecla/

Original comment by jpenn...@gmail.com on 2 May 2012 at 10:00

GoogleCodeExporter commented 9 years ago

Original comment by jpenn...@gmail.com on 2 May 2012 at 10:00

GoogleCodeExporter commented 9 years ago 
Just to clarify, Tecla does not target blind users (though it helps with 
general accessibility). The main target user for Tecla is someone with a 
mobility impairment that uses switches to access technology. Think Prof. 
Stephen Hawkins. For more information about how these users control their 
Android devices with Tecla see the following video playlist:
http://bit.ly/Tecla4AndroidPlaylist

Should this be reported separately?

Original comment by jsilva.k...@gmail.com on 3 May 2012 at 12:25

GoogleCodeExporter commented 9 years ago 
Fixed by Carmello Siciliano and merged into the main trunk line.

Original comment by justinfr...@gmail.com on 17 Jul 2012 at 11:29