Principles of accessible web desing (at #fronteers10)

2eb74cc5ebb96ea69807efa88c448aa2?s=47 Eric Eggert
September 27, 2011

Principles of accessible web desing (at #fronteers10)

2eb74cc5ebb96ea69807efa88c448aa2?s=128

Eric Eggert

September 27, 2011
Tweet

Transcript

  1. Principles of Accessible Web Design Eric Eggert aka. @yatil —

    Fronteers Jam Session — Amsterdam
  2. (Almost.) Everyone here is disabled. (Or will be at some

    time.)
  3. None
  4. “People need not be limited by physical handicaps as long

    as they are not disabled in spirit.”
  5. Different input mechanisms

  6. Different input mechanisms

  7. Different input mechanisms

  8. Different input mechanisms

  9. Different input mechanisms

  10. Different input mechanisms

  11. Different input mechanisms

  12. Different output mechanisms

  13. Different output mechanisms

  14. Different output mechanisms

  15. Different output mechanisms

  16. Different output mechanisms

  17. Different output mechanisms

  18. None
  19. We don’t need special websites for people with special requirements.

  20. Have you ever forgotten to buy new batteries for your

    mouse?
  21. None
  22. None
  23. None
  24. None
  25. Accessible websites help everyone.

  26. None
  27. We are designing the web for our future selves.

  28. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  29. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  30. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  31. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  32. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  33. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  34. 0 25 50 75 100 14-19 20-29 30-39 40-49 50-59

    60+ 1998 2008
  35. What can we do?

  36. 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.
  37. POSH5 & POUR

  38. POSH5 & POUR Plain Old Simple HTML5

  39. POSH5 & POUR Plain Old Simple HTML5 Perceivable, Operable, Understandable,

    Robust
  40. POSH5 Use the best HTML5 Element available for the task

    at hand.
  41. HTML5 Includes many accessibility features (although others claim otherwise). It

    is not the spec to look to when searching for web accessibility techniques.
  42. WCAG2 Is the spec for accessible web content. Provides an

    exhaustive list of techniques to make web content accessible.
  43. http://www.w3.org/WAI/WCAG20/quickref/ Perceivable Operable Understandable Robust

  44. And now: Sharky mail: mail@yatil.de twitter: @yatil

  45. And now: Sharky mail: mail@yatil.de twitter: @yatil