1 / 47

Where Accessibility Lives: Incorporating A11y into your Process and Team

Where Accessibility Lives: Incorporating A11y into your Process and Team. Presented By: Derek Featherstone. CSUN 2019 Assistive Technology Conference March 15, 2019. Where accessibility lives: a story of inclusion. Characters in our story. Claire VP Engineering. Jake Team Lead. Sanjay

bhoey
Download Presentation

Where Accessibility Lives: Incorporating A11y into your Process and Team

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Where Accessibility Lives: Incorporating A11y into your Process and Team Presented By: Derek Featherstone CSUN 2019 AssistiveTechnology Conference March 15, 2019

  2. Where accessibility lives: a story of inclusion

  3. Characters in our story Claire VP Engineering Jake Team Lead Sanjay Design Director

  4. incrediWeb Company incrediWeb Company

  5. User feedback quote “I’m really struggling toselect a colour for the shirt I want; the buttons are too close together for me."

  6. User feedback quote 2 “I can’t seem to change the size of the text"

  7. User feedback quote 3 “I’m trying to buy this but I can’t do it with the keyboard"

  8. User feedback quote 4 “I can’t quite understand this video... there’s too much background noise, and no captions."

  9. User feedback quote 5 “I’m having a tough time remembering what went wrong and how to fix it."

  10. The leadership team

  11. Jake talks with his team

  12. Jake calls for help Help.

  13. Jakes mindset

  14. Jake’s first question Who’s job is this?

  15. Jake’s second question How do we start?

  16. Jake’s third question What are we missing?

  17. Accessibility lives in people. Accessibility lives in process. Accessibility lives in tools.

  18. Accessibility lives in people.

  19. Step 1: set a goal Step 1: Set a goal.

  20. Perfect.

  21. Feelings that perfect creates absolute finished done no changes needed nothing left to do • unachievable • overwhelming • don’t know where to start

  22. Better.

  23. Feelings that better creates relative improvement over any previous state shows progress room to grow never “done” • first steps • “we can do this” • starting somewhere is better than doing nothing

  24. Step 2: Start and learn quickly Step 2: Start and learn quickly.

  25. How to start and learn quickly Step 2: Start and learn quickly. • Look to the standards (WCAG 2.0) • Get started, try to fix 20 things next week. • Use that week to figure out how long the other 217 issues will take.

  26. Step 3: Research and plan Step 3: Research and plan.

  27. Engaging a research panel

  28. How we test? 100% test coverage!

  29. User feedback in context I’m trying to buy this,but I can’t do it with the keyboard.

  30. User feedback in context 2 I’m really struggling to select a colour for the shirt I want; the buttons are too close together for me.

  31. How to research and plan Step 3: Research and plan. • Talk with people, and get help. • Create a prioritized remediation plan. • Keyboard issues • Image/media issues • Forms issues

  32. What are priorities? What kind of priorities? • Highest business value • High impact, low complexity • Highest risk • Can we solve other problems too?

  33. Accessibility lives in process.

  34. Step 4: Create your standard Step 4: Create your standard.

  35. How to create your standard Step 4: Create your standard. • Evolves to always get better. • “Here’s how we are going to do things” • Document those standards in your pattern libraries, style guides, and design systems. • Use this for hiring and onboarding

  36. Accidentally accessible “I mean accessibility is nice and all but you know that wasn’t the thinking behind this product. It wasn’t designed for disabled people.” Accidentally Accessible

  37. Design systems in the wild

  38. Design systems in the wild 2

  39. Documenting source order 1 2 3 Documenting source order: micro level

  40. Interaction tables

  41. ? Documenting our designs 4 7 6 5 2 3 1 44px “User name” (label) “Password” (label) “Show password” / “Hide password” (toggle button) “Secret key” (label) “Secret key help” (link) “Sign in” (button) “Help me sign in” (link) Notes: 3. When showing/hiding password, leave focus on button. 5. When showing help from link, move focus to help content. 100% container width

  42. Accessibility lives in tools.

  43. Step 5: Commit to the future Step 5: Commit to the future.

  44. How to commit to the future Step 5: Commit to the future. • Continue to evolve patterns, guides, and systems. • Study things we don’t know about • One dedicated accessibility sprint every quarter. • Include people with disabilities in the process: ideation, design, usability testing

  45. The team, together again. Claire VP Engineering Jake Team Lead Sanjay Design Director

  46. Te power of the web. The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect. Sir Tim Berners-Lee

  47. Thank You! Follow Us Speaker Contact Information: Derek Featherstonederek.featherstone@levelaccess.com Level Access Contact Information:​ info@levelaccess.com (800) 889-9659 www.levelaccess.com @LevelAccessA11y linkedin.com/company/level-access​ facebook.com/LevelAccessA11y/ levelaccess.com/blog/ Slides available for download March 15th at: www.levelaccess.com/csun2019 47

More Related