Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Promoting mobile accessibility at work

Tiphaine
October 05, 2022

Promoting mobile accessibility at work

Tiphaine

October 05, 2022
Tweet

More Decks by Tiphaine

Other Decks in Technology

Transcript

  1. ◉ 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 to have more tasks 4 Challenges Ref:Deque Systems
  2. “ If you know your enemy and know yourself, in

    a hundred battles you will never be defeated. 5
  3. ◉ Troubles clicking small buttons ◉ Difficulties with some gestures

    ◉ Can’t use the touch screen 9 Motor Problems
  4. ◉ Troubles reading long text ◉ Difficulties comprehending words ◉

    Can’t understand the UI 10 Cognitive Problems
  5. ◉ Difficulties hearing properly ◉ Can’t perceive sound ◉ Can’t

    understand without subtitles 11 Auditory Problems
  6. ◉ Font size change ◉ Color correction ◉ TalkBack 12

    Braille Display Assistive Technology Ref:Emerald Coast
  7. Assistive Technology 13 ◉ Display size change ◉ Voice input

    / control ◉ Switch Access Ref:Google
  8. WCAG 2.0 ◉ Web Content Accessibility Guidelines 2.0 ◉ Recommended

    by W3C ◉ A list of requirements to follow 16
  9. Levels of Conformance 18 A Single A 25 items Minimum

    AA Double A 13 items Better AAA Triple A 23 items Best
  10. JIS X 8341-3:2016 ◉ Web accessibility standard in Japan ◉

    Also used for mobile phones 19 “JIS X 8341-3:2016 Level AA Compliant” Aim for the certification! ✊
  11. ◉ 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 to have more tasks 21 Challenges Ref:Deque Systems
  12. Marketing Boost ◉ Improve your company’s image✨ ◉ Keep up

    with industry trends ◉ Differentiate yourself from your competition 23
  13. ◉ Having a guideline helps write cleaner code ◉ Reusing

    components increases productivity ◉ Implementing UI tests eases maintenance Improve developers’ life 25
  14. Your user base is changing ◉ Japanese population is shrinking

    ◉ Your current users are aging ◉ Aging troubles start before 65 years old 29
  15. 31 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 / 内閣府
  16. The invisible population ◉ People can’t talk due to social

    pressure ◉ You might be the reason you don’t see them ◉ The target is different from government stats 32
  17. It helps everyone ◉ It’s not “Disabled vs Normal People”

    ◉ You can be temporarily/situationally disabled ◉ “Don’t assume anything” 33
  18. Create a better product ◉ Constraints drive creativity ◉ Better

    skills ensure higher product quality 34 BAD DESIGNS DISABLE PEOPLE Ref:btrax
  19. It is required by law 36 Ref:内閣府 The Act for

    Eliminating Discrimination against Persons with Disabilities was revised in 2021, Now mandatory for private-sector too
  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 to have more tasks 37 Challenges Ref:Deque Systems
  21. 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? 41
  22. Research ◉ Basics (targets, problems, assistive technologies) ◉ Why you

    need accessibility ◉ WCAG ◉ Inclusive Design 43
  23. 45 Plan ◉ Set achievable, incremental goals ◉ Identify problems,

    create tickets ◉ Prioritize tickets, complete them Ref:W3C, Web担当者Forum / 弁護士ドットコム
  24. ◉ Start with small & easy changes ◉ Go gradually

    (ex: one ticket per sprint) ◉ Integrate checks into existing processes 47 Think on the long term
  25. 49 WCAG Perceivable level A items Just screen reader support

    Finally released 😭✨ WCAG Perceivable level A items kakari for Clinic
  26. Track Progress Don’t track the use of assistive technology 52

    Ref:AdrianRoselli, W3C, Mightybytes, StackExchange
  27. ◉ Number of WCAG criterions met ◉ Goals previously set

    ◉ Number of tickets done ◉ Number of inquiries 53 Track Progress
  28. ◉ People are not rejecting you ◉ Build a welcoming

    culture ◉ Stay humble ◉ Get support from people with influence 54 Workplace Relationships
  29. Small acts in your daily life ◉ Just sharing info

    on SNS is enough 👍 ◉ Be considerate when posting 57
  30. 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