Clerc Center Logo   Laurent Clerc National Deaf Education Center
Gallaudet University
Gallaudet > Clerc Center > TecEds > TecEds Reviews > Suggestions for Developers search | site index
TecEds Reviews
intro search submit accessible media other resources home
 

Suggestions for Developers

Want to make software accessible to deaf and hard of hearing individuals? Here are some suggestions gleaned from comments by teachers in the field.

  1. Provide visual clues as to what the computer and program is doing when changing screens
  2. Simple and straightfoward to operate, yet challenging for the mind
  3. Game-like format
  4. Abundant and varied activities
  5. Relevant supplemental materials and teacher guides
  6. Pace and level of difficulty can be set by teacher or parent
  7. Allows modification by teacher or parent such as adding words or problems
  8. Requires minimal, if any, adult involvement--can be used independently
  9. Minimal amount of text and/or reading required for young children.
  10. Very positive reinforcement for correct answers. Gentle correction for wrong answers.
  11. Foolproof keying, i.e. hitting the wrong sequence of keys does not re-bot the program.
  12. Multiple uses, i.e. writing, language arts, social studies.
  13. As for audio... Don't rely on any sound as the sole means of providing information. If it is just background sound that has no bearing on the intended lesson, fine. If valuable information is provided via sound/voice, there must be some complementary visual that expresses the same thing. A simple example, if a child completes a task the program should not simply voice-over, "Continue by clicking on the frog," but must include a visual cue such as having the frog jump up and down with a sign that says, "Click on me" or some such thing.

For general information about developing accessible software, visit Microsoft's Windows Guidelines for Accessible Software Design