$30 off During Our Annual Pro Sale. View Details »

Mobile Application Accessibility

Mobile Application Accessibility

A presentation given in February 2013 summarizing challenges and solutions to increase the accessibility of mobile applications.

Adrian Kosmaczewski
PRO

February 19, 2013
Tweet

More Decks by Adrian Kosmaczewski

Other Decks in Technology

Transcript

  1. Mobile Accessibility

  2. Adrian Kosmaczewski

  3. None
  4. None
  5. None
  6. None
  7. None
  8. What is “Accessibility”?

  9. “The degree to which a product, device, service, or environment

    is available to as many people as possible.” http://en.wikipedia.org/wiki/Accessibility
  10. Accessibility  ≠ Usability

  11. Accessibility is about everyone

  12. Accessibility is about everything

  13. Transportation

  14. http://www.openideo.com/open/voting/inspiration/enhanced-urban-mobility-the-people-s-way Architecture and Urbanism

  15. http://www.georgiancollege.ca/news/wp-content/uploads/2010/01/ACCESSIBILITY-003-300x281.jpg Employment

  16. Example: Conferences

  17. •Wheelchair access? •Restrooms? •Copies of papers? •Sign language interpreters? •Quiet

    places for conversations? •Braille copies of the printed material? •Volunteers to describe and guide? •Food allergies or religious preferences? •Flashing lights?
  18. Legal Implications

  19. None
  20. Article 4.g

  21. To undertake or promote research and development of (…) new

    technologies, including information and communications technologies, mobility aids, devices and assistive technologies, suitable for persons with disabilities, giving priority to technologies at an affordable cost; http://www.un.org/disabilities/convention/conventionfull.shtml
  22. Switzerland?

  23. http://en.wikipedia.org/wiki/Convention_on_the_Rights_of_Persons_with_Disabilities

  24. http://www.admin.ch/ch/d/sr/151_31/index.html

  25. http://www.admin.ch/ch/f/rs/151_31/index.html

  26. Article 10

  27. None
  28. None
  29. Mobile Technologies

  30. Disruption

  31. http://www.flickr.com/photos/oskay/365607662/

  32. http://www.flickr.com/photos/justdrew1985/4348527596/

  33. Lifestyle change

  34. http://www.flickr.com/photos/garryknight/4659579077/ http://www.flickr.com/photos/aidanmcmichael/295397071/ http://www.flickr.com/photos/lwr/27361510/

  35. for everyone

  36. http://www.flickr.com/photos/luc/6800884507/ http://www.flickr.com/photos/faceme/3578347527/

  37. Mobile developers?

  38. http://www.flickr.com/photos/digital_femme/4979749085/ http://www.flickr.com/photos/jenniferconley/6897584703/ http://www.flickr.com/photos/digital_femme/4979750047/

  39. Demographics

  40. Male

  41. Healthy

  42. http://www.flickr.com/photos/slworking/5757370044/ (sorta)

  43. 20 - 40 years old

  44. Medium to high income

  45. Not a good start

  46. Anecdote

  47. iPhone Dev Days London 2010

  48. “10 Commandments for iOS Developers”

  49. Attendee

  50. Blind

  51. “You forgot the 11th”

  52. Accessibility

  53. None
  54. Mobile Paradox

  55. Mobile technologies enable users

  56. •Focused •Immediate •Geolocalized •Cameras •Accelerometer •Compass •Gyroscope •Microphone •Cheaper

  57. Mobile technologies disable users

  58. •Small screen •Small keyboard •On-screen keyboard •Poor battery life •Small

    font sizes •Operated with one hand •Stripped-down contents
  59. None
  60. Axis of mobile accessibility

  61. •Types of content •Types of user needs •Types of challenges

    posed by mobile devices
  62. 1. Mobile content

  63. •Websites •Apps

  64. 2. User needs

  65. •Visual •Motor/Mobility •Auditory •Seizures •Cognitive/ Intellectual •Localization and cultural issues

  66. •Temporary •Permanent

  67. 3. Challenges

  68. •Small devices •Different form factors •Touch screens •Diverse UI designs

    •Lack of expandability •Outdoor use http://www.flickr.com/photos/solgrundy/5365304165/ http://www.flickr.com/photos/johanl/6798184016/
  69. None
  70. How?

  71. http://www.flickr.com/photos/jenniferconley/6897571105/ Include Accessibility in the Design Process

  72. Considerations

  73. •Standards •Platforms •Guidelines •APIs •… end users

  74. 7 Guidelines

  75. 1. Descriptive Text in UI Controls

  76. A short, localized word or phrase that succinctly describes the

    control or view, but does not identify the element’s type. A brief, localized phrase that describes the results of an action on an element.
  77. None
  78. Source: developer.apple.com (akos.ma/hnw)

  79. 2. Do not convey meaning with color alone

  80. http://www.cultofmac.com/200268/clear-for-mac-a-refreshingly-fun-and-simple-task-manager-inspired-by-ios-review/

  81. 3. Minimize text input

  82. 4. Semantic HTML markup

  83. 5. Avoid scrolling

  84. 6. Do not use gestures alone

  85. 7. Allow zooming

  86. http://www.flickr.com/photos/79578508@N08/8381182759/

  87. None
  88. Summary

  89. 1. Descriptive text in UI controls 2. Do not convey

    meaning with color 3. Minimize text input 4. Semantic HTML markup 5. Avoid scrolling 6. Do not use gestures alone 7. Allow zooming
  90. And remember

  91. Think accessible!

  92. Thanks!

  93. Contains elements adapted from 
 “Mobile Accessibility - Challenges and

    Best Practices” 
 by Shyamala Prayaga" http://akos.ma/sj7" " " Copyright © 2013 Adrian Kosmaczewski" All Rights Reserved