Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/ Many associate making a digital product accessible with the guidelines and specifications that address themselves at the code-level. In short, the developers/engineers will take care of it. While the thoughtful implementation of accessible code during the development phase is unquestionable, the truth is accessibility depends heavily on choices made by designers and others involved in determining the user experience, and typically before development begins. Join Jennison as he illustrates this by identifying some of the user interactions and design-related decisions that can pose accessibility challenges. He will also share practical advice for those seeking to scale accessibility and make it a shared responsibility.

1. Accessibility Is More Than What Lies In The Code
Jennison Asuncion
Sr Staff Technical PROG MGR, LinkedIn
Organizer, Bay Area Accessibility and Inclusive Design Meetup
Co-Founder, Global Accessibility Awareness Day
Keynote at Future of Web Design San Francisco, October 29, 2015

2. Agenda
Where To Begin
Accessibility Defined
User Testing
Conclusion
Some Design And Accessibility Specifics

3. 3
Accessibility refers to designing and developing user
experiences that everyone, including people with disabilities
can independently consume and interact with.
Achieved by conforming to the World Wide Web
consortium Web Content Accessibility Guidelines.
Accessibility Defined
Question: how many people’s UX can we positively impact?

4. 4
Raise awareness through conversation, presentation, and other
activities
Create a task force/committee
Secure leadership buy-in
Dedicate resource/create a program
Where To Begin

5. 5
Create/adopt a definition and guidelines
Patternize accessibility
Take the plunge with an audit or identify
one new-build to focus on
Where To Begin (cont’d)

6. 6
Assume and confirm accessibility as a core project requirement
with all stakeholders
Raise accessibility in initial conversations/track progress
Document in UI specs/wireframes
Definition of done
Post launch/maintenance/redesign
Actively solicit feedback
Where To Begin (cont’d)

7. 7
Locate participants
Test before you test
Assure your venue/getting there is accessible
Train your test team
Running the user test accessibly
User Testing

8. 8
Keyboard interactivity, including visible keyboard focus
Sufficient color contrast
Conveying meaning accessibly
Separate accessible version
Some Design And Accessibility Specifics

9. 9
Naming uniquely and meaningfully
Error messaging
Carousels
Pinch-zoom (don't disable)
Custom mobile web gestures
Some Design And Accessibility Specifics

10. 10
​Questions?
​jennison.asuncion@gmail.com (eMail)
​@Jennison (Twitter)
Conclusion

11. 11
​WebAIM www.webaim.org
​#a11y Twitter hashtag
​A11y on Slack http://web-a11y.herokuapp.com/
​W3C's Web Accessibility Initiative Resources
www.w3.org/WAI/Resources/Overview
​ARIA Design Patterns
www.w3.org/TR/wai-aria-practices/#aria_ex
​Accessibility Wins http://a11ywins.tumblr.com/
Resources