Fronteers Jam Session: Principles of Accessible Web Design

3,880 views
3,768 views

Published on

Published in: Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,880
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
20
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Fronteers Jam Session: Principles of Accessible Web Design

  1. 1. Principles of Accessible Web Design Eric Eggert aka. @yatil — Fronteers Jam Session — Amsterdam
  2. 2. (Almost.) Everyone here is disabled. (Or will be at some time.)
  3. 3. “People need not be limited by physical handicaps as long as they are not disabled in spirit.”
  4. 4. Different input mechanisms
  5. 5. Different input mechanisms
  6. 6. Different input mechanisms
  7. 7. Different input mechanisms
  8. 8. Different input mechanisms
  9. 9. Different input mechanisms
  10. 10. Different input mechanisms
  11. 11. Different output mechanisms
  12. 12. Different output mechanisms
  13. 13. Different output mechanisms
  14. 14. Different output mechanisms
  15. 15. Different output mechanisms
  16. 16. Different output mechanisms
  17. 17. We don’t need special websites for people with special requirements.
  18. 18. Have you ever forgotten to buy new batteries for your mouse?
  19. 19. Accessible websites help everyone.
  20. 20. We are designing the web for our future selves.
  21. 21. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  22. 22. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  23. 23. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  24. 24. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  25. 25. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  26. 26. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  27. 27. 1998 2008 14-19 20-29 30-39 40-49 50-59 60+ 0 25 50 75 100
  28. 28. What can we do?
  29. 29. Don’t use Flash. It isn’t working on most mobiles. It isn’t „working“ on most PCs either. It can be made accessible on Windows and IE only.
  30. 30. POSH5 & POUR
  31. 31. Plain Old Simple HTML5 POSH5 & POUR
  32. 32. Plain Old Simple HTML5 POSH5 & POUR Perceivable, Operable, Understandable, Robust
  33. 33. POSH5 Use the best HTML5 Element available for the task at hand.
  34. 34. HTML5 Includes many accessibility features (although others claim otherwise). It is not the spec to look to when searching for web accessibility techniques.
  35. 35. WCAG2 Is the spec for accessible web content. Provides an exhaustive list of techniques to make web content accessible.
  36. 36. Perceivable Operable Understandable Robust http://www.w3.org/WAI/WCAG20/quickref/
  37. 37. And now: Sharky mail: mail@yatil.de twitter: @yatil
  38. 38. And now: Sharky mail: mail@yatil.de twitter: @yatil

×