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
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
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