Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Getting Started With Web Accessibility

4,258 views

Published on

Published in: Design, Technology
  • Be the first to comment

Getting Started With Web Accessibility

  1. 1. Getting Started with Web Accessibility<br />@seanyo<br />SeanYo.ca<br />sean.yo@uoguelph.ca<br />
  2. 2. What is Web Accessibility?<br />Web accessibility refers to the practice of making websites usable by people of all abilities and disabilities. When sites are correctly designed developed and edited all users can haveequal access to information and functionality.<br />http://en.wikipedia.org/wiki/Web_accessibility<br />
  3. 3. Diversity of Abilities<br />Web Accessibility Barriers<br />Auditory<br />1<br />Cognitive and Neurological<br />2<br />Physical/Motor<br />3<br />Speech<br />4<br />Visual<br />5<br />
  4. 4. Why Be Accessible?<br />
  5. 5. Why Web Accessibility Makes Sense<br />
  6. 6. Why Be Accessible?<br />
  7. 7. Why Have a Website?<br />
  8. 8. To Connect With People<br />
  9. 9. User Experience<br />
  10. 10. Accessibility Experience<br />
  11. 11. People Have Experiences Checklists Don’t<br />
  12. 12. Web Accessibility Principles<br />
  13. 13. The Only One That Matters<br />People First<br />
  14. 14. AODA <br />Principles of Accessibility<br /><ul><li> Independence
  15. 15. Dignity
  16. 16. Integration
  17. 17. Equality of opportunity</li></li></ul><li>W3C<br />Principles of Accessibility<br /><ul><li> Perceivable
  18. 18. Operable
  19. 19. Understandable
  20. 20. Robust</li></li></ul><li>Understading Web Accessibility<br />For Managers & Developers<br />
  21. 21. Accessibility is Simple<br />Automated Tools and Best Practices<br /><ul><li> Lots of great, free tools to measure accessibility
  22. 22. Lots of great, free info & recommendations
  23. 23. Using web standards is good for accessibility
  24. 24. Tools: WAVE, FAE, TAW, FANGS, NVDA
  25. 25. Info: WAI, WCAG, WebAIM, WaSP
  26. 26. Use valid, semantic code - Even better, use a CMS</li></li></ul><li>Accessibility is Complicated<br />No Single Path<br /><ul><li> How to measure accessibility?
  27. 27. Automated testing needs user testing
  28. 28. Websites are not fire &forget – they are a process
  29. 29. Which Standard? WCAG, 508, AODA
  30. 30. Lots of platforms: IE, Gecko, Webkit + Mobile
  31. 31. Content will change & break accessibility</li></li></ul><li>Accessibility is Cheap<br />The Best Stuff is Open & Free<br /><ul><li> Being accessible improves search rankings
  32. 32. Google is a Screen Reader
  33. 33. CMS tools are a strong investment – Open & free
  34. 34. The best tools are Open & free
  35. 35. Development best practices are Open & free
  36. 36. CMS tools can automated compliance : alt tags</li></li></ul><li>Accessibility is Expensive<br />You’re only as Accessible as your last a11y bug… <br /><ul><li> Passing a checklist doesn’t make a site accessible
  37. 37. Accessibility is challenging and doesn’t end
  38. 38. Leaving it to the end is costly – in time and money
  39. 39. Web development is a mature profession
  40. 40. Accessibility is a critical dimension of webdev
  41. 41. A11y is expensive to retrofit, like schemas & security</li></li></ul><li>Accessibility is Cheap & Simple…<br />
  42. 42. …When Finding Problems<br />
  43. 43. Accessibility is Complicated and Expensive…<br />
  44. 44. …When Fixing Accessibility Problems<br />
  45. 45. Accessibility for Management<br />
  46. 46. Plan for Accessibility From the Beginning<br />
  47. 47. Most errors are introduced during requirements analysis and design. The later they are removed, the most expensive it is to take them out.<br />Boehm et al (1975): “Some Experience with Automated Aids to the Design of Large-Scale Reliable Software.”<br />Diagram Source: http://blogs.windriver.com/vxworks/device-management/<br />
  48. 48. Accessibility is not an option.An inaccessible website is incomplete.<br />
  49. 49. A vendor claiming a product is accessible does not make it accessible.<br />
  50. 50. Avoid Assumptions About Your Audience<br />
  51. 51. Count on Text Provide Alternatives in Text<br />
  52. 52. Don’t take control of your visitor’s experience<br />
  53. 53. Use Clear Language<br />
  54. 54. Testing Is Hard<br />Real People<br />Different Needs<br />Assistive Technology<br />
  55. 55. Accessibility for Developers<br />
  56. 56. Be Usable, Searchable and Navigable<br />
  57. 57. Be Semantic <br />
  58. 58. Separate Content & Presentation<br />
  59. 59. Progressive Enhancement is the new graceful degredation<br />
  60. 60. Do Periodic A11y Sanity Testing<br />Turn off CSS<br />All Alt Text in Place<br />Test with FANGS/Screen Reader<br />
  61. 61. Testing Is Fun<br />Real People<br />Different Needs<br />Assistive Technology<br />
  62. 62.  <br />5:00 PM<br />The Bullring<br />Wednesday, June 1st<br />

×