This document discusses developing apps that are accessible for the visually challenged. It notes that visually impaired users come in many forms, from needing corrective lenses to complete blindness, so apps need to support varied needs. It provides tips for both Android and iOS accessibility, such as using content descriptions, ensuring all elements can be navigated, and testing with accessibility services. Specific apps that help visually impaired users are also mentioned, like TalkBack on Android and VoiceOver on iOS.
2. Understand why
Challenges we do not face but they do
Little things that help
Why
3. They are different from you and are more capable is
ways we do not expect.
They can certainly use some help to make their lives
better, so can we.
You have to do this if you want to do US Govt.
Projects. Yes there is money in it.
Oracle Does a TON of tests for Accessibility.
Why
4. Myth: visually impaired users are blind.
It’s strange how common this belief is; we just implicitly
seem to assume the most extreme case. In reality, of
course, there’s an entire spectrum of visual impairment,
from the lowest prescription of corrective lenses right
through to complete blindness.
It’s worth realising that the needs of partially-sighted
users will differ from those of blind users, and so on.
Myths
5. In reality, blind and partially-sighted users make every
bit as much use of their memory of spatial location as
sighted users do, because it accelerates target
acquisition. When you decide to create a new email
message, you don’t scan the whole screen to find the
‘New Message’ button; your hand pushes the mouse
in that direction automatically.
visually impaired users access things
sequentially
6. Accessibility users listen to just enough to orient
themselves, and make a decision, and then skip to the
next element. Putting overly-verbose descriptions or
help as accessibility information is fruitless, and will
only frustrate.
Don’t skip descriptions totally they are useful!!
Myth: visually impaired users listen to
all on-screen text.
7. Engines on Android
KickBack,
TalkBack, and
SoundBack
iOS
Nuance – Huge Family( Dragon Family )
Nina
Apps that help
8. Barcode and QR Reader
Shop / Mall.
Point shoot the QR Code
Get Price , Name ,Quality
Apps that can help
9. Magnify – Android
Helps read fine print ( useful for elderly / partially
sighted)
::App::
10. Talk Back
This application is a part of Google’s Android
Accessibility Service. It is developed to assist visually
impaired people to use their cell phones easily. The
application also reads out the texts loud, while the
movements of the user are carefully evaluated and
spoken by the app. In order to enable this app, go to
Settings, Accessibility, and enable TalkBack service.
Talk Back
11. Add descriptive text to user interface controls in your
application using the android:contentDescription
attribute. Pay particular attention to ImageButton,
ImageView and CheckBox.
Make sure that all user interface elements that can
accept input (touches or typing) can be reached with
a directional controller, such as a trackball, D-pad
(physical or virtual) or navigation gestures .
Lets get our hands dirty!!
12. Make sure that audio prompts are always
accompanied by another visual prompt or
notification, to assist users who are deaf or hard of
hearing.
Test your application using only accessibility
navigation services and features. Turn on TalkBack
and Explore by Touch, and then try using your
application using only directional controls.
Not Just Visual Challenges
16. About 70-80% of your app is probably accessible
already, via the built-in VoiceOver support in UIKit.
iOS
17. Accessible elements have three primary properties
which are of interest for accessibility: an accessibility
label, an accessibility hint, and one or more
accessibility traits. Note that the accessibility label is
independent of any other label the element might
have (such as a button’s label), but that if you don’t
specify an accessibility label and your control does
have a regular label, VoiceOver will of course use it.
Adding Accessibility
18. There are three further accessibility properties (the
accessibility frame, which specifies the element’s
location and size on screen; the accessibility value,
which gives the element’s current value as a string;
and the accessibility language which
Adding iOS Acceibility