UX Camp Ottawa: Accessibility as a Design Tool

5,550 views

Published on

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,550
On SlideShare
0
From Embeds
0
Number of Embeds
64
Actions
Shares
0
Downloads
57
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

UX Camp Ottawa: Accessibility as a Design Tool

  1. 1. Accessibility as a Design Tool
  2. 2. simplyaccessible.comAll contents © Simply Accessible Inc., unless otherwise noted.Expressed permission is required to use these slides.Contact info@simplyaccessible.com if you have any questions.
  3. 3. bacontoday.com/turbaconducken-turducken-wrapped-in-bacon/
  4. 4. I think some of why people don’t do Webaccessibility is a lack of awareness, but a lotof it is because people think it’s too hard.What would help is if you can start teachingpeople HOW to integrate it into typicalworkflows for specific audiences—devs.project managers, Scrum Masters, designers
  5. 5. I think they just genuinely struggled tounderstand the benefits. Many fail to realizethat it’s not just about people who are blindor deaf—many people could benefit from amore accessible site.
  6. 6. Derek, all this stuff that you’ve taught us...yes, it makes this more accessible, but really,fundamentally, this is just a better design,period.
  7. 7. Accessibility as a Design Tool
  8. 8. Derek Featherstonefeather@simplyaccessible.com @feather
  9. 9. Accessibility is not binary, all-or-nothing,black and white. We have every shade of greyin between. How you view this point frameseverything that you learn and do aboutaccessibility.
  10. 10. extremes extremes
  11. 11. IDEO: The Deep Divehttp://www.youtube.com/watch?v=M66ZU2PCIcM
  12. 12. ‘‘ By examining the extreme ends of a set of phenomena in depth, the entire universe ofrelationships can be illuminated since otherinstances will fall somewhere on the map of relations and links.
  13. 13. Tools to get the job done.
  14. 14. Tools to get the job done.
  15. 15. So, how do we useAccessibility as a Design Tool?
  16. 16. Always start at the beginning of the design process
  17. 17. Project User Design Develop & Validate &Definition Research Iteration Implement Launch
  18. 18. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny specialcontent needs?What support/customer serviceneeds will thisbring?Has this beendone before?What newtechnology &challenges arethere?
  19. 19. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include peoplecontent needs? with disabilities in more thanWhat support/ interviews andcustomer service focus groups; useneeds will this observation andbring? walk-throughs.Has this been Includedone before? functional needs in personas, userWhat new stories and othertechnology & artifactschallenges arethere? Find people both in and outside your org to get subject matter expertise and perspective.
  20. 20. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colourscontent needs? with disabilities in more than Test conceptsWhat support/ interviews andcustomer service focus groups; use Test iconographyneeds will this observation and and visualbring? walk-throughs. language assets (particularly forHas this been Include low vision user)done before? functional needs in personas, user Tend to focus onWhat new stories and other visual design, buttechnology & artifacts we must examinechallenges are process design.there? Find people both in and outside your org to get subject matter expertise and perspective.
  21. 21. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colours Test templatescontent needs? with disabilities in more than Test concepts Test functionalWhat support/ interviews and prototypes andcustomer service focus groups; use Test iconography demosneeds will this observation and and visualbring? walk-throughs. language assets Don’t test with (particularly for people withHas this been Include low vision user) disabilities toodone before? functional needs early (it can be in personas, user Tend to focus on very frustratingWhat new stories and other visual design, but and nottechnology & artifacts we must examine productive)challenges are process design.there? Find people both Fix technical in and outside accessibility your org to get issues THEN test subject matter with people with expertise and disabilities for perspective. ease of use
  22. 22. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colours Test templates Engage andcontent needs? with disabilities respond to user in more than Test concepts Test functional feedbackWhat support/ interviews and prototypes andcustomer service focus groups; use Test iconography demos Ensure that asneeds will this observation and and visual part of roll-outbring? walk-throughs. language assets Don’t test with appropriate (particularly for people with training is givenHas this been Include low vision user) disabilities too to CSRs so theydone before? functional needs early (it can be can act. in personas, user Tend to focus on very frustratingWhat new stories and other visual design, but and not On-going planstechnology & artifacts we must examine productive) for organizedchallenges are process design. learning fromthere? Find people both Fix technical project, and in and outside accessibility documentation/ your org to get issues THEN test resolution of subject matter with people with issues that are expertise and disabilities for raised perspective. ease of use
  23. 23. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colours Test templates Engage andcontent needs? with disabilities respond to user in more than Test concepts Test functional feedbackWhat support/ interviews and prototypes andcustomer service focus groups; use Test iconography demos Ensure that asneeds will this observation and and visual part of roll-outbring? walk-throughs. language assets Don’t test with appropriate (particularly for people with training is givenHas this been Include low vision user) disabilities too to CSRs so theydone before? functional needs early (it can be can act. in personas, user Tend to focus on very frustratingWhat new stories and other visual design, but and not On-going planstechnology & artifacts we must examine productive) for organizedchallenges are process design. learning fromthere? Find people both Fix technical project, and in and outside accessibility documentation/ your org to get issues THEN test resolution of subject matter with people with issues that are expertise and disabilities for raised perspective. ease of use
  24. 24. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colours Test templates Engage andcontent needs? with disabilities respond to user in more than Test concepts Test functional feedbackWhat support/ interviews and prototypes andcustomer service focus groups; use Test iconography demos Ensure that asneeds will this observation and and visual part of roll-outbring? walk-throughs. language assets Don’t test with appropriate (particularly for people with training is givenHas this been Include low vision user) disabilities too to CSRs so theydone before? functional needs early (it can be can act. in personas, user Tend to focus on very frustratingWhat new stories and other visual design, but and not On-going planstechnology & artifacts we must examine productive) for organizedchallenges are process design. learning fromthere? Find people both Fix technical project, and in and outside accessibility documentation/ your org to get issues THEN test resolution of subject matter with people with issues that are expertise and disabilities for raised perspective. ease of use
  25. 25. Project User Design Develop & Validate & Definition Research Iteration Implement LaunchAny special Include people Test colours Test templates Engage andcontent needs? with disabilities respond to user in more than Test concepts Test functional feedbackWhat support/ interviews and prototypes andcustomer service focus groups; use Test iconography demos Ensure that asneeds will this observation and and visual part of roll-outbring? walk-throughs. language assets Don’t test with appropriate (particularly for people with training is givenHas this been Include low vision user) disabilities too to CSRs so theydone before? functional needs early (it can be can act. in personas, user Tend to focus on very frustratingWhat new stories and other visual design, but and not On-going planstechnology & artifacts we must examine productive) for organizedchallenges are process design. learning fromthere? Find people both Fix technical project, and in and outside accessibility documentation/ your org to get issues THEN test resolution of subject matter with people with issues that are expertise and disabilities for raised perspective. ease of use
  26. 26. Overlapping Map Polygons: Non-visual access
  27. 27. Overlapping Map Polygons: Non-visual access
  28. 28. Auto-suggest: Keyboard Access
  29. 29. Error Messaging: Low-vision Access
  30. 30. SVG Maps: Keyboard Access
  31. 31. Table of Contents: Skip Links on Steroids
  32. 32. simplyaccessible.com/newsletter
  33. 33. Derek Featherstonefeather@simplyaccessible.com @feather
  34. 34. simplyaccessible.comAccessibility consulting, strategy and assessmentsAccessible development and remediation servicesTraining courses, workshops and conferences Derek Featherstone feather@simplyaccessible.com @feather on twitter (613) 599-9784

×