Dealing with (ir)responsibility for accessibility in UX
•Download as PPTX, PDF•
5 likes•27,391 views
The value of taking a role-based approach to managing accessibility, and what that might look like. Presented at UX in the City, Oxford, April 2016.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (6)
Similar to Dealing with (ir)responsibility for accessibility in UX
Similar to Dealing with (ir)responsibility for accessibility in UX (20)
More from David Sloan
More from David Sloan (20)
Recently uploaded
Recently uploaded (20)
Dealing with (ir)responsibility for accessibility in UX
- 1. Dealing with (ir)responsibility for accessibility in UX David Sloan @sloandr UX in the City, Oxford, April 1st 2016
- 2. What does irresponsibility for accessibility look like?
- 3. Example of accessibility audit spreadsheet
- 4. The project manager with a vague notion accessibility is really important
- 5. The Rumpelstiltskin developer Image credit: Flickr user Shardayyy https://www.flickr.com/photos/shardayyy/6060374429
- 6. The accessibility specialist who speaks, but does anyone listen?
- 7. So. How can we best distribute responsibility—and authority— for accessibility?
- 8. Responsibility as part of accessibility maturity
- 9. Accessible Design Maturity Continuum An Accessible Design Maturity Continuum, uxfor.us/mature-it
- 10. “By concentrating solely on the bulge at the center of the bell curve we are more likely to confirm what we already know than learn something new and surprising.” Tim Brown, Change by Design
- 12. User research
- 13. Visual design
- 14. Content strategy
- 15. Research and design: responsible for handing off an inclusive design that can be implemented accessibly
- 16. Development
- 17. QA testing
- 18. Development and QA: responsible for delivering a functional solution that is as accessible as possible
- 20. Project/product management: responsible for owning accessibility for the project or product
- 22. Senior management: responsible for organisational strategy and accountability for accessibility
- 23. Dealing with responsibility for accessibility that isn’t well distributed
- 24. Tactics • Use accessibility audits to find out reasons for existence of barriers • Communicate progress internally and externally • Standardise on solutions, and share them • Identify accessibility points of contact, and grow a network • Use pilot projects to demonstrate value of integrating accessibility
- 25. “When people feel successful taking baby steps they often find themselves want to make big changes, including their environment.” —BJ Fogg
- 26. “We have an organizational mandate that UX won’t hand anything to engineering that cannot be made accessible..” —UX lead at health information provider
- 28. Manifesto for Accessible User Experience When we examine accessibility through the lens of user experience, we see that accessibility is: • A core value, not an item on a checklist • A shared concern, not a delegated task • A creative challenge, not a challenge to creativity • An intrinsic quality, not a bolted-on fix • About people, not technology accessibleux.org
Editor's Notes
- Accessibility often looks like this
- Don’t panic!
- S— into gold
- Speaks for disabled people
- Avoid Inconsistency Incompleteness Inaccuracy
- Identify Auditing and repair (if possible), Focusing on conformance with standards Responsibility is QA/Dev Prioritise Still auditing and repairing, but focus is on key user journeys, task completion People over standards Responsibility moves to include UX/PM Inject Adding accessibility into design and development processes and practices Responsibility widened to include: visual design, content authors Integrate Accessibility influences innovation, service/product definition
- Disability as a trigger for innovation
- Ensuring accessibility considerations are the responsibility of the right person at the right time
- Understanding the problem space from a disabled person’s perspective Involving disabled people in early research activities Including disability in personas and scenarios
- Visual design: Colors, fonts, use of icons Selection of appropriate UI patterns for interactions Templating, consistency in layout A11y in wireframes, style guides Annotations/resources that advise on implementation
- Text: plain language Form labelling, error messages Icons/images and alternative text Media, including captioning and AD
- Inclusive because it’s been informed by a disabled person’s perspective
- Processes and practices for ensuring accessibility influences development decisions Tools for testing as you code Control over UI library selection and use Media player selection CMS support for a11y How a11y is integrated into sprints Test processes for accessibility
- Specific tests for accessibility, conducted at the right time Clear definition of success: Keyboard accessibility Name, role, state/value information exposed Semantic structure Labels
- also making clear where requirements cannot be met; starting the discussion on what to do as early as possible
- Authority and accountability for accessibility The higher the buy-in, the more visible accessibility is as a quality Signing-off on projects only when accessibility has been assessed as being achievable Ensuring teams have skills and awareness of their responsibilities Managing communication on accessibility progress Managing exception processes
- Encouraging a culture of accessibility Organizational accessibility strategy Including an internal accessibility standard as a measure of quality Identifying other owners of accessibility: Recruitment Staff Development Procurement
- Dave
- Persuasive design principles
- Draft matrix mapping WCAG SCs to roles
- Dave