Browse files

Delete deaf.pdf

  • Loading branch information...
karypun committed Jun 26, 2016
1 parent ecdaa67 commit 821bef25d1a7585d416247af645a423afe02fb6f
Showing with 0 additions and 0 deletions.
  1. BIN accessibility/deaf.pdf
BIN -94.7 KB accessibility/deaf.pdf
Binary file not shown.

2 comments on commit 821bef2


This comment has been minimized.

Copy link

sanjaypoyzer replied Jun 28, 2016

Just wondering why this was deleted?


This comment has been minimized.

Copy link

ei8fdb replied Jun 29, 2016

Hea @karypun, as an experiment, I thought I'd publish my thoughts on the poster here, in the open.

I think what was there originally was a good place to start. I've gone back through some articles, and best practices on inclusive design for users who are hard of hearing, or deaf.

The most accessible source was a nice article on A List Apart, which you've probably already read. It made the distinction between subtitles and captions - it reminded me of the argument for localisation, not translation.

So based on those, here are some thoughts:

  • Firstly we should get a content designers input on the content

Under the "do" heading

  • when using videos provide sign language interpretation if possible
  • if not combine captions with subtitles

(the message here is that using subtitles, instead of captions for videos where the audio uses confusing figures of speech will be equally confusing as if written)

Under the "don't" heading

  • use complicated words or figures of speech
    (to communicate the figure of speech message, maybe try some iconography showing confusion?)
  • put content in audio of video only
  • transcribe audio/video word for word - translate the meaning
  • provide verbal only feedback channels
  • make users read long blocks of content

If you haven't seen it here is the ALA article:
and a nice introduction from Webaim:

Please sign in to comment.