[Resul Caner Yildirim] Accessibility on Android

Presentation from GDG DevFest Ukraine 2016.
Learn more at: https://devfest.gdg.org.ua

Transcript

1. ACESSIBILITY ON ANDROID R. CANER YILDIRIM #dfua
2. Who am I? Resul Caner Yildirim UX Expert @InnovationBox
3. Outline PRODUCT DESIGN APP DEVELOPMENT MYTHS & WRONGS CHALLENGES DISABILITY TESTING STORIES PERSONAS DISABILITY DESIGN PROCESS DESIGN TIPS USER RESEARCH
4. What do 4 million apps and over 600 million websites have in common? Question
5. They suck!
7. “UX design is the value you deliver at every touchpoint” Emily Stewart
8. More than 1 billion persons in the world have some form of disability. This corresponds to about 15% of the world's population. World Health Organization
9. A typical male, age 35, nonsmoker, who works an office job, with some outdoor physical responsibilities, and who leads a healthy lifestyle has the following risks: http://www.disabilitycanhappen.org/docs/disability_stats.pdf
10. 21% chance of becoming disabled for 3 months or longer during his working career http://www.disabilitycanhappen.org/docs/disability_stats.pdf
11. With a 38% chance that the disability would last 5 years or longer and with the average disability for someone like him lasting 82 months. http://www.disabilitycanhappen.org/docs/disability_stats.pdf
12. Accessibility Myths Text only pages are the best Accessible sites look boring It takes to much time and money It’s hard to implement Accessibility is for disable users Its responsibility of
 developers If I can use everyone can do it Accessibility is 
 optional
13. When in a project do you think accessibility? Question
14. Research Design Development Test / Iterate
15. Research Design Development Accessibility Test
16. Test Development Design Accessibility Research
17. Accessible Design
18. Personas With Matt Murdock
19. Creating Personas for Your Design Ask yourself : • Who are the users? • What are the activities they wish to perform? • Why they might visit your websites? i.e. motivation • How does our website/services fit into their context of life?
20. John Fisher Matt Murdock’s Client
21. Background
 • Age: 70 • Occupation: retired • Disabilities: low-vision, hand tremor, short-term memory loss • Technical level: uses his mobile to call his relatives and look his grandchildren's photos.
22. Attributes • Uses screen magnifier • Uses his phone only for call and camera • Preferred large links, texts and icons • Finds scrolling stickers and flashing animations very distracting • Easy to get lost in the app
23. Goals • Able to use basic services on the mobile easily • Don’t get stuck on apps and able to save his data • Able to customize font-size, colors and content
24. Tips For Creating Personas • Empathy: Think about target users and their pain points. • Concrete: Create detailed personas and make them real. • Face to face interview with your persona • Include disability condition and AT information for accessibility personas
25. • Visual disability • Hearing disability • Mobility disabilities Focus of today
26. POUR Principle • Perceivable • Operable • Understandable • Robust
27. Vision Disability • Blindness • Low Vision • Color-blindness
28. Blindness
29. • cannot scan for content • primary interact with keyboard • hard to access visual information • limitations of screen readers
30. Perceivable: include detailed text description for graphics, video, animation Operable: fully operable with keyboard Understandable: make sure your page has a clear, and consistent structure, and avoid using complex tables Robust: be careful with new technologies that will raise incapability with AT
31. Low - Vision With Matt Murdock
38. Low-Vision: Challenges • Cannot see without magnifier • Text in graphics is hard to read • Cannot see contents with low contrast and resolution
39. Tips: Use real text as much as possible, rather than text in graphics. Use percentages, rather than absolute units (e.g. dp, pixel), in your layouts. Maximize the contrast of your pages, including graphics, fonts, and backgrounds
40. Color Blindness With Matt Murdock
41. Color-Blindness
42. Color-Blindness: Types • Protanopia and protanomaly (red deficiencies) • Deuteranopia and deuteranomaly (green deficiencies) • Tritanopia (blue deficiencies) • Rod monochromacy or achromacy (no color)
43. Color-Blindness: Challenges • Cannot see all colors • Color used as the only way to convey information •Cannot realize bad contrast
44. Hue Lightness & Saturation
45. Exaggerate lightness differences between foreground and background colors
46. Choose dark colors from the bottom half of the circle against light colors from the top half of the circle. Light Colors Dark Colors
47. Avoid contrasting hues from adjacent parts of the hue circle, especially if the colors do not contrast sharply in lightness.
48. Perceivable: Avoid colors or color pairs that cause problems for people who are colorblind. Provide sufficient contrast between foreground and background colors. Make sure that colors are not your only method of conveying important information.
49. Hearing With Jason Carmela
50. Hearing: Challenges • Auditory prompts without visual signposts • Lacking caption/transcript for video and audio content
51. Perceivable: Make sure they can perceive (hear) auditory content
 • Alternative text for animation • Synchronized captioning • Transcript • Text description (e.g. for audio instructions) Allow for user control of start/stop, animations, and other equivalent options.
52. Mobility With Matt Murdock
53. Mobility: Challenges • May not be able to control touchscreen • May become fatigue very easily when using AT •May need an extra button or keyboard (Switch Access)
54. Operable: Build a good navigation structure Give feedback to user actions Help users navigate efficiently through keyboard Implement BrailleBack
55. What Is Your Role in Accessibility?
56. • User Experience Designers • Recognize the accessibility implications of your designs. • Apply appropriate accessibility personas and scenarios to ensure your designs are accessible to all. • User Experience Researchers • Design usability tests to include users with disabilities and impairments. • Conduct usability tests on specific accessibility features.
57. Story Time!
59. Namba Taxi
60. Android Accessibility Features
61. TalkBack
62. BrailleBack
63. Switch Access
64. Voice Access
65. Other Features
66. • Large Texts • Magnification Gestures • Color Inversion • Color Correction • High Contrast Texts • Caption Support
67. Nano Tech Autonomous Cars Robotics Machine Learning Artificial Intelligence Genetics IoT Mobile AR/VR Wearable The world is changing and so are users
68. EMPATHIZE
69. DEFINE
70. IDEATE
71. PROTOTYPE
72. TEST
73. “If I had an hour to solve a problem I’d spend 55 min. thinking about the problem and 5 min. thinking about solutions.” Albert Einstein
74. Why understand our users? ?
75. To solve real problems • Don’t assume you know their problems • Don’t assume they will behave as you expect them to • Don’t assume you’ve thought of everything
76. • Research up-front can help you avoid designing or building things that don’t matter • Continual research can validate your ideas and save you time and money To save money
77. Researcher Designer Developer Product Manager Research aligns the team’s understanding of the problem. To align the team
78. #dfua @protechman THANK YOU! caner@innovationbox.com R. Caner Yildirim
79. meet@innovationbox.com InnovationBox QUESTIONS & IDEAS
80. Credits • http://www.who.int/mediacentre/factsheets/fs352/en/ • http://www.slideshare.net/qixingz/design-for-accessibility • https://www.google.com/accessibility/ • https://developer.android.com/guide/topics/ui/accessibility/ index.html • https://medium.com/salesforce-ux/7-things-every-designer- needs-to-know-about-accessibility-64f105f0881b