Developing Apps for the
Visually Challenged
iOS and Android.
 Understand why
 Challenges we do not face but they do
 Little things that help
Why
 They are different from you and are more capable is
ways we do not expect.
 They can certainly use some help to make th...
 Myth: visually impaired users are blind.
 It’s strange how common this belief is; we just implicitly
seem to assume the...
 In reality, blind and partially-sighted users make every
bit as much use of their memory of spatial location as
sighted ...
 Accessibility users listen to just enough to orient
themselves, and make a decision, and then skip to the
next element. ...
 Engines on Android
 KickBack,
 TalkBack, and
 SoundBack
 iOS
 Nuance – Huge Family( Dragon Family )
 Nina
Apps tha...
 Barcode and QR Reader
 Shop / Mall.
 Point shoot the QR Code
 Get Price , Name ,Quality
Apps that can help
 Magnify – Android
 Helps read fine print ( useful for elderly / partially
sighted)
::App::
 Talk Back
 This application is a part of Google’s Android
Accessibility Service. It is developed to assist visually
imp...
 Add descriptive text to user interface controls in your
application using the android:contentDescription
attribute. Pay ...
 Make sure that audio prompts are always
accompanied by another visual prompt or
notification, to assist users who are de...
 <ImageButton
android:id=”@+id/add_note_button”
android:src=”@drawable/add_note”
android:contentDescription=”@string/add_...
 Careful when you develop custom views.
 You will need to do some extra work
 Use :AccessibilityEvent
Achtung!
 public boolean onKeyUp (int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_DPAD_LEFT) {
mCurrentValue--; // ...
 About 70-80% of your app is probably accessible
already, via the built-in VoiceOver support in UIKit.
iOS
 Accessible elements have three primary properties
which are of interest for accessibility: an accessibility
label, an ac...
 There are three further accessibility properties (the
accessibility frame, which specifies the element’s
location and si...
Enable Accessiblity
 Remesh Govind
 @rgnmenon
 rgnmenon@gmail.com
Reach Me
Upcoming SlideShare
Loading in …5
×

Vc info park

338 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
338
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Vc info park

  1. 1. Developing Apps for the Visually Challenged iOS and Android.
  2. 2.  Understand why  Challenges we do not face but they do  Little things that help Why
  3. 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. 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. 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. 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. 7.  Engines on Android  KickBack,  TalkBack, and  SoundBack  iOS  Nuance – Huge Family( Dragon Family )  Nina Apps that help
  8. 8.  Barcode and QR Reader  Shop / Mall.  Point shoot the QR Code  Get Price , Name ,Quality Apps that can help
  9. 9.  Magnify – Android  Helps read fine print ( useful for elderly / partially sighted) ::App::
  10. 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. 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. 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
  13. 13.  <ImageButton android:id=”@+id/add_note_button” android:src=”@drawable/add_note” android:contentDescription=”@string/add_note”/> Adding Content Decription
  14. 14.  Careful when you develop custom views.  You will need to do some extra work  Use :AccessibilityEvent Achtung!
  15. 15.  public boolean onKeyUp (int keyCode, KeyEvent event) { if (keyCode == KeyEvent.KEYCODE_DPAD_LEFT) { mCurrentValue--; // assuming text got udpated sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_ TEXT_CHANGED); return true; } ... } Accessibility Event sample
  16. 16.  About 70-80% of your app is probably accessible already, via the built-in VoiceOver support in UIKit. iOS
  17. 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. 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
  19. 19. Enable Accessiblity
  20. 20.  Remesh Govind  @rgnmenon  rgnmenon@gmail.com Reach Me

×