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

Not an afterthought: accessibility from start to finish

Not an afterthought: accessibility from start to finish

Building a new feature, fixing a bug, or adding support for a new operating system version.

None of these things are only engineering effort, or design effort, or product management effort, or quality assurance effort. They are a team effort.

Making an app accessible is a team effort, too. And something that is to be considered whether you're building that new feature, fixing that bug, or adding that support for a new operating system version.

We'll look at accessibility being something in the list of expectations, like your bug being fixed, or your feature working as it was intended.

And with that, making the difference between someone being unable to use your app at all, to being as delighted by it as anyone else.

Let's take a look at what we all can do to make our apps accessible, increase awareness, and build beautiful products for everyone — from start to finish.

Bas Broek

August 10, 2022
Tweet

More Decks by Bas Broek

Other Decks in Programming

Transcript

  1. NOT AN AFTERTHOUGHT: ACCESSIBILITY FROM START TO FINISH @BASTHOMAS 1

    — @basthomas, GitHub, August 10, 2022
  2. PLEASE ASK ME ANYTHING! LET THIS BE INTERACTIVE 2 —

    @basthomas, GitHub, August 10, 2022
  3. WHO AM I? ▸ XING ▸ Apple, macOS VoiceOver ▸

    WeTransfer ▸ Moya ▸ Swift Weekly Brief 3 — @basthomas, GitHub, August 10, 2022
  4. HISTORY WITH GITHUB MOBILE ▸ try! Swift NYC 2016 ▸

    GitHawk ▸ Accessibility in GitHawk 4 — @basthomas, GitHub, August 10, 2022
  5. 5 — @basthomas, GitHub, August 10, 2022

  6. FROM START 6 — @basthomas, GitHub, August 10, 2022

  7. TO FINISH 7 — @basthomas, GitHub, August 10, 2022

  8. WHY ACCESSIBILITY 8 — @basthomas, GitHub, August 10, 2022

  9. SHIFTING TO THE LEFT INTEGRATING INTO YOUR PROCESS ▸ Beyond

    developers ▸ Getting support teams in the loop ▸ Refinements ▸ QA mindset ▸ Definition of done ▸ Design for accessibility 9 — @basthomas, GitHub, August 10, 2022
  10. 10 — @basthomas, GitHub, August 10, 2022

  11. 11 — @basthomas, GitHub, August 10, 2022

  12. TACKLING ISSUES IS A TEAM EFFORT 12 — @basthomas, GitHub,

    August 10, 2022
  13. A DIVERSE TEAM 13 — @basthomas, GitHub, August 10, 2022

  14. THEY DON'T TEACH YOU THIS IN SCHOOL 14 — @basthomas,

    GitHub, August 10, 2022
  15. PLANTING SEEDS IT TAKES TIME. 15 — @basthomas, GitHub, August

    10, 2022
  16. UPKEEP VS BACKLOG 16 — @basthomas, GitHub, August 10, 2022

  17. SHARING KNOWLEDGE ▸ What do users expect? ▸ User testing

    ▸ Assistive Technologies vs Accessibility ▸ Understanding Assistive Technologies 17 — @basthomas, GitHub, August 10, 2022
  18. WHAT DO USERS EXPECT? 18 — @basthomas, GitHub, August 10,

    2022
  19. USER TESTING 19 — @basthomas, GitHub, August 10, 2022

  20. ASSISTIVE TECHNOLOGIES VS ACCESSIBILITY ▸ Screen reader ▸ Dark mode

    / theming ▸ Haptics ▸ Voice input ▸ ... (much) more 20 — @basthomas, GitHub, August 10, 2022
  21. ASSISTIVE TECHNOLOGIES: ONION LAYERS ▸ Screen reader ▸ Switch access

    ▸ Voice input ▸ Keyboard navigation 21 — @basthomas, GitHub, August 10, 2022
  22. UNDERSTANDING ASSISTIVE TECHNOLOGIES ▸ Usage ▸ (Power) user's usage 22

    — @basthomas, GitHub, August 10, 2022
  23. DEMOS? USE ASSISTIVE TECHNOLOGIES! 23 — @basthomas, GitHub, August 10,

    2022
  24. 24 — @basthomas, GitHub, August 10, 2022

  25. 25 — @basthomas, GitHub, August 10, 2022

  26. (AUTOMATED) TESTING IS HARD 26 — @basthomas, GitHub, August 10,

    2022
  27. QUICK WINS(DAY) CHIPPING AWAY 27 — @basthomas, GitHub, August 10,

    2022
  28. ALL OF THIS IS EASIER SAID THAN DONE WHICH CHALLENGES

    ARE YOU FACING? 28 — @basthomas, GitHub, August 10, 2022
  29. TRYING OUT THE GITHUB APP 29 — @basthomas, GitHub, August

    10, 2022
  30. THANK YOU! @BASTHOMAS 30 — @basthomas, GitHub, August 10, 2022