1. Practical Tips For Designing Inclusive User Experiences Kath Moonan

2. Hello! Vodafone Accessibility Lead (Contractor) Accessibility Chair, Usability Professionals Assoc. UK Worked in accessibility over 10 years AbilityNet Senior Consultant 2006-2009 Accessibility 2.0 conference organiser Strong interest in: Inclusive design Working with UX and visual designers I like working with developers too!

3. Contents Accessibility for UX? Persuasion – Increasing engagement Users first Find positives Align accessibility with business project goals Include users in research (as well as testing) Practicalities Interaction design principles Work in progress Involving diverse users in research and testing iPhone apps

4. ≠ Contents (Almost) no screen readers Wot no code!

5. A note on language:Why diverse and not disabled? Many users with diverse needs do not classify themselves as disabled: Dyslexic users Deaf users Mild impairments – mild vision, motor impairment Temporary disability Older users

6. Low take up of accessibility in UX? Top reasons from Lisa Herrod’ssurvey No budget? I don’t know how to http://www.webdirections.org/resources/lisa-herrod/ Clients won’t pay Recruitment Lacking specialist skills Stops creativity “We’re not ready yet”

7. Cost of diverse user testing at beta or live Cost No. of changes Accessibility testing Requirements Deployment Development

8. Where to start?

9. WCAG 2.0 has little UX guidance

10. http://www.uiaccess.com/accessucd

12. http://wiki.fluidproject.org/

13. Guerilla Diverse User Research

14. Meet the users Involving users in research is an exciting, persuasive way to include accessibility in a project User requirements shouldn’t be exclusive to mainstream non-disabled users Diverse users have requirements too Learn from the people then apply the guidelines not Learn from the guidelines – never meet the people

15. Involve users with mild impairments Involving users with milder impairments is a great way to start Many users may already be involved in standard user testing but not screened for their impairment No specialist equipment needed Adapt skills you already have Be sensitive to the user

16. Don’t ask What’s wrong with you?

17. Do ask - Are you comfortable talking about your condition? Your insights are incredibly helpful to us and will help us improve the accessibility of our product You don’t have to answer all of my questions If I’ve missed anything please tell me Permission to show video educationally

18. The user is expert & collaborator Value their experience and opinion (don’t ask for it for free) Don’t make assumptions Gaining individual insight – everyone is different Users with impairments could be a target or new market

19. Dealing with accessibility barriers Be sensitive to the impact poor accessibility has on the participant Participants may think they have done something wrong despite re-assurances Take a break or stop if the participant gets stressed Be open - discuss accessibility issues at the end of each task or the session Round the session up with a reminder of the value of the user’s feedback Send a thankyou email!

20. Involve users with mild impairments Involving users with milder impairments is a great way to start Lots of these users involved in standard user testing but not screened for their impairment No specialist equipment needed Dyslexia Colour blindness Mild vision impairments (i.e. age related sight loss)

21. Involve users with mild impairments Dyslexia Colour blindness Mild vision impairments (i.e. age related sight loss) RSI Hard of hearing (especially for projects with video / audio content)

22. What about other impairment types? Use web resources Use WCAG 2.0 BS8878 Expert reviews and cognitive walkthroughs Fluid UX accessibility review Keyboard only Functionality test: NVDA or Voiceover Screen reader Zoom magnifier on the mac / browser zoom Collaborate with an expert

23. WAI – user stories http://www.w3.org/WAI/intro/people-use-web/stories#onlinestudent

24. Youtube http://www.youtube.com/watch?v=SafNTEHJ0DM

25. Yahoo – Victor Tsaran http://www.yuiblog.com/blog/2007/05/14/video-intro-to-screenreaders/

26. Persuasion

27. Persuasion Users + business case = persuasion Listen to users Business benefits Design principles User requirements + problem solving = engagement Quick wins Creative solutions

28. Assets User requirements Resources based on interview Fact sheets Design principles

31. User centred design Avoid design decisions purely based on your vision* or the equipment you’re using Gain insight into the experience of people with low vision, colour blindness or dyslexia Use simulations and heuristics in our toolkit to help you evaluate your design Involve people with low vision, colour blindness or dyslexia in your design processes *Unless you have a vision impairment! Using colour to enhance accessibility 31 April 21, 2011

32. Visual impairment - statistics About 2,000,000 people in the UK have significant sight loss 364,615 people in the UK who were registered as severely sight impaired (blind) or sight impaired (partially sighted) The vast majority of people with sight problems are older people, aged 65 and over Seventy percent of blind and partially sighted adults have other disabilities or long term health problems in addition to their sight loss Using colour to enhance accessibility 32 April 21, 2011

33. Partial sight simulations Using colour to enhance accessibility 33 April 21, 2011 Age-related macular degeneration (AMD) http://www.lighthouse.org/about-low-vision-blindness/vision-disorders/age-related-macular-degeneration-amd/

34. Partial sight simulations Using colour to enhance accessibility 34 April 21, 2011 Cataracts http://www.lighthouse.org/about-low-vision-blindness/vision-disorders/cataract/

35. Partial sight simulations Using colour to enhance accessibility 35 April 21, 2011 Diabetic Retinopathy http://www.lighthouse.org/about-low-vision-blindness/vision-disorders/diabetic-retinopathy/

36. Stargardt’s Syndrome simulation Using colour to enhance accessibility 36 April 21, 2011

37. Walkthroughs How would the participant navigate through your product? Identify issues at prototype stage Exciting and engaging for the team

38. Publicise what works Accessibility is often presented as what’s going wrong: Checkpoint violations Errors Missing / broken Snag list is not compelling Report what works first What users like Why What lessons can be learnt

39. Align accessibility with business goals SEO* - headers, page titles – will increase search engine ranking Quality coding – across a large organisation procedures are complex: Third party agencies Off shore development Multi-agency project lifecycle Accessibility helps alignment / leverage to fix poor coding Accessibility used to iterate design http://bunnyfoot.com/blog/author/veronika-jermolina/

40. Vodafone research Colour contrast Text size Icons Diverse users Mainstream users

41. Developing an iPhone app iPhone is a revolutionary device for many disabled users Great positive news story Perfect example of inclusive design Team are excited by project Showcases positivity What I can do with my iPhone I love my iPhone “If I can do it on the iPhone I will”

42. User research Involved diverse users from the beginning Find out how users use their phones Blind and partially sighted expert users

43. Diverse user testing – phase one Users who don’t require assistive technology Severe motor impairment Multiple sclerosis Dyslexia Findings – overlapped significantly with mainstream users Diverse users experience usability issue as a barrier Gained buy-in from team – positive results

44. Summary Meet your users Users first – guidelines second Align accessibility with business goals Introduce problems that require solutions Re-purpose WCAG for increased engagement Thanks Stay in touch @ladymoonan! Thanks to Vodafone