Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Designing for accessibility

95b99419138620c939f1582fc0cd8b9b?s=47 Laura Kalbag
September 27, 2013

Designing for accessibility

From a talk at Shropgeek (R)evolution in September 2013

95b99419138620c939f1582fc0cd8b9b?s=128

Laura Kalbag

September 27, 2013
Tweet

More Decks by Laura Kalbag

Other Decks in Design

Transcript

  1. Designing for accessibility @laurakalbag laurakalbag.com AKA universal design AKA inclusive

    design
  2. Are you are developer or a designer?

  3. None
  4. = =

  5. designing for accessibility isn’t just for “designers”

  6. What is accessibility?

  7. Accessibility is the degree to which a website is available

    to as many people as possible.
  8. accessibility isn’t just about screen readers

  9. None
  10. None
  11. Shiny Shiny

  12. Is it because we don’t understand who we’re trying to

    help?
  13. Is it because we just don’t know what to do?

  14. Is it because it’s too hard, and there’s too much

    to think about?
  15. I’ve not got the answers

  16. It’s not fair if the web isn’t accessible

  17. None
  18. Design decisions made in the name of accessibility will largely

    benefit everyone.
  19. The four (main) types of disability that affect use of

    the web
  20. Visual

  21. Hearing

  22. Motor

  23. Cognitive

  24. None of these disabilities are completely black and white

  25. mild moderate moderately severe severe profound hearing

  26. astigmatism sensitivity colour blindness akinetopsia blindness eyesight

  27. Visual make it easy to read

  28. Hearing make it easy to hear

  29. Motor make it easy to interact

  30. make it easy to understand and focus Cognitive

  31. Good accessibility is good usability

  32. Examples

  33. Disclaimer

  34. Text

  35. None
  36. None
  37. None
  38. Squinting does not make an enjoyable reading experience

  39. 1. Make text content easy to read. 2. Ensure sensible

    font sizes. 3. Don’t prevent the user from resizing the fonts themselves in the browser.
  40. None
  41. None
  42. None
  43. What’s that supposed to mean?

  44. 1. Good copy is a part of good accessibility. Keep

    your text simple and your meaning clear.
  45. Colour

  46. None
  47. None
  48. Your screen isn’t the same as everybody else’s screens

  49. 1. Use colour contrast tools to ensure your text is

    high-contrast enough. 2. Beware of super-high contrast too.
  50. Content hierarchy

  51. This is a top-level heading This is a paragraph. It

    has some text in it. It’s a few sentences long. A lot of paragraphs look like this. This is a second level heading. This is a paragraph which has some links to other content and a button that allows you to take action.
  52. This is a top-level heading This is a paragraph. It

    has some text in it. It’s a few sentences long. A lot of paragraphs look like this. This is a second level heading. This is a paragraph which has some links to other content and a button that allows you to take action
  53. Randomly enlarging and colouring text does not make a hierarchy.

  54. 1. Make the content structure clear and consistent. 2. Use

    semantic headings, labels, lists and other relevant elements for your HTML or native controls.
  55. Links

  56. Why should I click there?

  57. Sometimes the links are the same colour and style as

    the rest of the text and you only find out it’s a link when you hover over it.
  58. Sometimes the links are the same colour and style as

    the rest of the text and you only find out it’s a link when you hover over it.
  59. Finding interactive elements should not be a game.

  60. 1. Make buttons and interactive elements easyily distinguishable from non-interactive

    elements. 2. Make links easy to recognise by using an underline.
  61. None
  62. None
  63. Why should I click there?

  64. 1. Use link text that makes sense out of context.

    Don’t use “click here”. 2. Remember that not all your users are clicking.
  65. Alt text

  66. None
  67. None
  68. Unhelpful alt text has its place on XKCD

  69. None
  70. 1. Provide text alternatives for images that helps a user

    understand the context of the image.
  71. Media

  72. No, I don’t want to listen to your podcast or

    watch your video tutorial. Give me text!
  73. 1. Provide text transcripts for audio. 2. Provide subtitles for

    video.
  74. JavaScript

  75. None
  76. None
  77. None
  78. 1. Use JavaScript with care and load it in a

    sensible place. 2. If your web site or app needs JavaScript, ensure you use WAI ARIA to guide assistive technologies.
  79. Navigation and way-finding

  80. None
  81. None
  82. The days of flash are over, stop punishing me with

    your artsy navigation.
  83. 1. Provide consistent ways to help users navigate, find content,

    and determine where they are.
  84. Forms

  85. First name Last name Email address Laura Kalbag email@laurakalbag.com

  86. None
  87. Don’t make me guess what and where the error is.

  88. Animations

  89. None
  90. Wait for me!

  91. 1. Give users enough time to read and use content

    2. Try not to distract users from their goals with unstoppable animations
  92. Resources

  93. None
  94. None
  95. None
  96. None
  97. None
  98. None
  99. None
  100. None
  101. None
  102. None
  103. None
  104. I need proof that accessible sites aren’t just ugly

  105. None
  106. None
  107. None
  108. None
  109. None
  110. None
  111. None
  112. None
  113. Consider accessibility at every point of planning. It is functionality,

    content hierarchy, copy, visual design and code.
  114. Accessibility as default

  115. Accessibility is easy to consider once you start caring about

    it.
  116. None
  117. Laura Kalbag @laurakalbag laurakalbag.com