Raise accessibility awareness at work as an Android developer

Android Worldwide - 26/10/2022
An edited version of the talk I gave at DroidKaigi (which focused on Japan market).

Video:
https://www.youtube.com/watch?v=mdsoyGhi4WM

Original:
https://docs.google.com/presentation/d/14ogtarX2Cc4RjDPco8WQePuROgINvuQfAWbbBznHxIo/edit?usp=sharing

Transcript

1. Raise accessibility　 awareness at work as an Android developer Android Worldwide Tiphaine | Oct 2022
2. ◉ Android Engineer in Japan ◉ MedPeer Inc (Kakari) @tahia910 2 Tiphaine
3. “ Why is accessibility not considered at work? 3 ?
4. ◉ Started on the wrong foot due to complaints ◉ Don’t know how to deal with the problem ◉ The risk of doing nothing is not clear ◉ Don’t want more work 4 Challenges Ref：Deque Systems
5. “ If you know your enemy and know yourself, in a hundred battles you will never be defeated. 5
6. The problem and how to deal with it What? 6 1
7. Types of Disabilities 7 Visual Motor Cognitive Auditory
8. ◉ Difficulties distinguishing colors ◉ Can’t read the text ◉ Can’t see the screen 8 Visual Problems
9. ◉ Troubles clicking small buttons ◉ Difficulties with some gestures ◉ Can’t use the touch screen 9 Motor Problems
10. ◉ Troubles reading long text ◉ Difficulties comprehending words ◉ Can’t understand the UI 10 Cognitive Problems
11. ◉ Difficulties hearing properly ◉ Can’t perceive sound ◉ Can’t understand without subtitles 11 Auditory Problems
12. ◉ Font size change ◉ Color correction ◉ TalkBack 12 Braille Display Assistive Technology Ref：Emerald Coast
13. Assistive Technology 13 ◉ Display size change ◉ Voice input / control ◉ Switch Access Ref：Google
14. 14 And many more! Definitely can’t remember them all 😱
15. “ 15 Just follow the guideline to solve everything!
16. WCAG 2.0 ◉ Web Content Accessibility Guidelines 2.0 ◉ Recommended by W3C ◉ Also used for mobile apps ◉ A list of requirements to follow 16
17. Four Principles 1. Perceivable 2. Operable 3. Understandable 4. Robust 17
18. Levels of Conformance 18 A Single A 25 items Minimum AA Double A 13 items Better AAA Triple A 23 items Best
19. You are not alone ◉ BBC ◉ Orange ◉ MDN ◉ And many more! 19
20. ◉ Started on the wrong foot due to complaints ◉ Don’t know how to deal with the problem ◉ The risk of doing nothing is not clear ◉ Don’t want more work 20 Challenges Ref：Deque Systems
21. Why？ Merits and risks for business 2 21
22. Marketing Boost ◉ Improve your company’s image✨ ◉ Keep up with industry trends ◉ Differentiate yourself from your competition 22
23. Respond to expectations ◉ Attract loyal customers ◉ Broaden your reach ◉ Avoid negative publicity 23
24. ◉ Having a guideline helps write cleaner code ◉ Reusing components increases productivity ◉ Implementing UI tests eases maintenance Improve developers’ life 24
25. 25 Usability Accessibility Ref：BAsixs Satisfactory Safe Usable Accessible
26. 26 Ref：Our World In Data, UN (1, 2) In 2050, one in 6 people will be over 65 Median age projection worldwide AGE
27. Future 2050 seniors are currently in their 30s All heavy smartphone users 27
28. Your user base is changing ◉ Your current users are aging ◉ Your country’s population might be shrinking ◉ Aging troubles start before 65 years old 28
29. “ Survivor bias： Logical error of focusing on who made it past a selection process, overlooking those who did not. 29
30. 30 Don’t improve accessibility Disabled people unable to use the product “So there’s no need to consider them” Disabled people seen as a minority Don’t appear in user stats (+ Low awareness in society) Ref：pacingpixie / HubSpot
31. The invisible population ◉ You might be the reason you don’t see them ◉ People can’t talk due to social pressure ◉ The target is different from government stats 31
32. It helps everyone ◉ It’s not “Disabled vs Normal People” ◉ You can be temporarily/situationally disabled ◉ “Don’t assume anything” 32
33. Create a better product ◉ Constraints drive creativity ◉ Better skills ensure higher product quality 33 BAD DESIGNS DISABLE PEOPLE Ref：btrax
34. 34 (󰑔) Digital accessibility related lawsuits Ref：UsableNet (report)
35. It is required by law 35 Ref：W3C, Disability:IN, eSSENTIAL Accessibility ◉ Mandatory for private sector: Australia, Canada, China, EU, India, Israel, Japan, New Zealand, South Korea, Switzerland, UK... ◉ Mobile apps are also targeted
36. ◉ Started on the wrong foot due to complaints ◉ Don’t know how to deal with the problem ◉ The risk of doing nothing is not clear ◉ Don’t want more work 36 Challenges Ref：Deque Systems
37. Integration process How? 37 3
38. 38 Planning & Analysis Design Implementation Testing Maintenance You want to check at each stage Ref：TPGi
39. Roadmap 39 1 Observe
40. Observe ◉ How much attention is paid to the problem? ◉ What is the current state of your app? ◉ Who is the decision maker? ◉ Who are your allies? 40
41. Roadmap 41 1 Observe 2 Research
42. Research ◉ Basics (targets, problems, assistive technologies) ◉ Why you need accessibility ◉ WCAG ◉ Inclusive Design 42
43. Roadmap 43 2 3 Plan Research 1 Observe
44. 44 Plan ◉ Set achievable, incremental goals ◉ Identify problems, create tickets ◉ Prioritize tickets, complete them Ref：W3C, Web担当者Forum / 弁護士ドットコム
45. “ 45 Do what you can within your reach, little by little, continuously
46. ◉ Start with small & easy changes ◉ Go gradually (ex: one ticket per sprint) ◉ Integrate checks into existing processes 46 Think on the long term
47. Roadmap 47 3 Plan 1 Observe 2 Research 4 Implement
48. 48 WCAG Perceivable level A items Just screen reader support All screens & released on time 🎉 WCAG Perceivable level A items kakari for Clinic
49. Roadmap 49 4 5 Maintain Implement 2 Research 1 Observe 3 Plan
50. Document & Educate ◉ Checklist ◉ Training ◉ Internal Guideline ◉ Policy 50
51. Accessibility Statement ◉ Explain your current situation ◉ Provide a way of contact for feedback ◉ Display your accessibility certification ◉ Reference the local legislation 51 Ref：W3C, NDA, GOV.UK, Essential Accessibility
52. Track Progress Don’t track the use of assistive technology 52 Ref：AdrianRoselli, W3C, Mightybytes, StackExchange
53. ◉ Number of WCAG criterions met ◉ Goals previously set ◉ Number of tickets done ◉ Number of inquiries 53 Track Progress
54. ◉ People are not rejecting you ◉ Build a welcoming culture ◉ Don’t put unnecessary pressure on yourself ◉ Get support from people with influence 54 Workplace Relationships
55. Roadmap 55 6 Share 2 Research 4 Implement 1 Observe 3 Plan 5 Maintain
56. Spread the word ◉ Communicate internally on progress ◉ Inform your customers ◉ Get feedbacks 56
57. Small acts in your daily life ◉ Just sharing info on SNS is enough 👍 ◉ Be considerate when posting 57
58. References ◉ Pragmatic Accessibility: A How-To Guide for Teams (Google I/O '17) - Google Developers ◉ Android Accessibility by Tutorials - Victoria Gonda ◉ noteアクセシビリティ施策 - note ◉ Ameba Pickのアクセシビリティ向上への取り込みに ついて - CyberAgent 58
59. Thanks! 59 Theme：SlidesCarnival Special thanks: @purunkaoru @y2kit_1127 @Gabrielle_Lng