Enabling your disabled market through UX
- 1. Enabling your disabled market by Mark Flint
- 2. Who am I? Degree in multimedia design technologies. Worked in education and disability sectors.
- 3. Who are Purple? Not for profit. Disability Confident. Changing the conversation between business and disabled consumers.
- 4. What? Why accessibility? User research and testing methods. How we can make our designs accessible?
- 5. Why?
- 6. 12 million 19% of population
- 7. Purple pound £249 billion per year. Disabled consumer spending power.
- 8. Conditions Blindness Impaired vision Colour blindness Deafness Impaired hearing Inability to use a mouse Slow response time Limited fine motor control Learning disabilities ADHD Inability to retain or concentrate on information Autism Asperges Alzheimer's Chronic illness Physical disabilities Intellectual disabilities Dyslexia
- 9. Myth of average. Design to edges. Adapt to each users requirements.
- 10. UX process
- 11. Involve the experts Disabled people know their needs better than anyone.
- 12. Recruiting Local services, charities, schools/colleges.
- 13. User categories Visual, auditory, physical, cognitive. Novice and advanced.
- 14. Inclusive personas Vision, hearing, speech, manual dexterity, mobility, cognitive.
- 15. Craig, age 27 “I’ve got to take a pic of that…and tweet it, Instagram it, and…” About him: • Thinks texting is an art • Blogs about food • Takes lots of pictures • Impulsive and will go almost anywhere on the spur of the moment Accessibility consideration: Has deuteranopia (Colour blind with green deficiencies Technology use: iPhone 6 Plus, HP Slate 10 Tablet Needs for a good experience: • Content that doesn't rely on color to provide meaning or content • Buttons and controls that have clearly indicated states (active or inactive) • Uses maps a lot and finds them difficult to understand when they're color coded without further explanation of color meanings Accommodations or assistive technologies used: The HueVue app helps Glen to identify colors when he needs them. It's not always convenient to use.
- 16. ? Contrast settings. Colour filters.
- 17. Jane, age 16 “I love looking at vintage maps and stamps.” About her: • Average kid, loves games, hates homework • Was in an accident at age 7; injuries resulted in brain damage • Wants to be a veterinarian • Collects maps and stamps Accessibility consideration: Has a mild cognitive (intellectual) disability; short-term memory loss Technology use: Galaxy Note 4 phone (Android), MacBook Pro Needs for a good experience: • Simple, clear layout; consistent navigation • Headings and bullets • Content written in plain language without slang • Inline definitions for abbreviations, acronyms, and jargon • Iconography, drawings, animations • Captions and transcripts for videos Accommodations or assistive technologies used: Occasionally uses a screen reader, particularly when she's researching online for homework assignments or when she has a hard time understanding things (narration is easier to understand than reading)
- 18. ? Visual presentation. Readable fonts.
- 19. How do we run the sessions?
- 21. Setting up the room Make sure the room is clear.
- 22. Interpreter? Is there space for a PA? Record interpreter.
- 23. Tasks in easy read format All documentation. Schedule for the day.
- 24. Simplified text with an icon.
- 25. Record screen reader audio output Record screen reader and participant separately.
- 26. Watch the keyboard Navigating via the tab key or arrow keys, consider recording keystrokes.
- 27. Time Allow twice the time, due to assistive technologies. Varies dependent on disability.
- 28. Assistive technologies Screen reader, eye gaze etc. What can you offer?
- 29. Debrief after each task Do not wait until the end.
- 30. What do they like/dislike? Websites, apps etc.
- 31. Then you can ask them about their answers.
- 32. Homework Get more results by asking them to do the like/dislike task before they arrive.
- 33. Icons Found that users were confused by the hundreds of different icons with the same meaning.
- 34. Autistic individual did not recognise the house with windows as being an icon.
- 35. Common mistakes
- 36. Involve them from the beginning
- 37. ‘one of us tested it with a screen reader’ Assistive technologies should be used in real-life scenarios. You can not test for accessibility without involving disabled people.
- 38. Test against WCAG While people with disabilities are good at finding accessibility issues, if something is inaccessible, they might not be able to identify it because it’s inaccessible.
- 39. Automated testing ‘my site is accessible it passed the online test’. No tool exists that will test. Does not mean it is usable.
- 40. ‘my site is accessible it passed the online test’ Alt = Dog
- 41. Do not assume that feedback from one person with a disability applies to all A person with a disability doesn't necessarily know how other people with different disabilities interact with products, nor know enough about other disabilities to provide valid guidance on other accessibility issues.
- 42. Use same tasks So results are comparable.
- 43. How do we make our designs accessible?
- 45. Tips
- 46. Don’t use colour as the only visual means of conveying information Use colour to highlight or complement what is already visible.
- 47. How many error messages can you see?
- 48. Only 1 error message is clear in greyscale.
- 49. Provide visual focus indication for keyboard focus
- 50. Most websites do not create their own focus styles.
- 51. Don’t make people hover to find things This effects keyboard-only user and speech recognition.
- 54. Visual impairments Underlining links, alt tags, contrast, fonts.
- 55. Dyslexia Friendly fonts such as arial, verdana, Tahoma / text to speech.
- 57. Motor disabilities Keyboard shortcuts, switch control, large tap targets.
- 58. So remember… Purple pound, involve disabled users, design to the edges.
- 59. End
Editor's Notes
- #3: Degree in Multimedia Design Last 7 years working on UX and Research projects in either the education or disability sector Head of digital transformation at Purple
- #9: Talk about the myth of average
- #10: Cut at 0 Mention if there is no average you have literally designed it for nobody We need to design to the edges