Designing Documentation for Visually-Impaired Users  

Preparing 'large-print' texts requires more than changing type size; it involves writing and structuring materials to meet the needs of an audience with varied physical challenges. For large print documents, format considerations include: using appropriate type, line length, and other design elements; setting all material flush left; and using lay-flat bindings. For braille documents, text may also need to eliminate or explain unusual symbols. Content considerations for both may include: replacement of graphics with descriptive text: brief orientation to the physical location and dimensions of objects; and reminders of help services. Cassette tapes offer one alternative to print or braille texts, plus serve other audiences.

Barthel, Brea. STC Proceedings (1994). Articles>Documentation>Accessibility

Making Documentation Accessible to Users With Disabilities  

Good documentation takes into account the needs of people with disabilities. Such documentation is termed 'accessible' and provides support for the assistive technologies used by people with disabilities. For example, accessible documentation provides a text equivalent for each graphic element, such as a picture, flow diagram, or icon. This provision is necessary for users who rely on screen readers to read the documentation.

Chappell, Gail B. STC Proceedings (2003). Articles>Documentation>Accessibility>Technical Writing

Making Web-Based Online Help Accessible: A Case Study  

Accessibility is about providing successful access to information, and the use of information technology by people who have disabilities. The IBM® WebSphere® Commerce development team adopted IBM’s mandate to make its software accessible, and achieved a high level of accessibility in its release of the IBM WebSphere Commerce, Version 5.4, suite of products. Continuing with the next release, the WebSphere Commerce development team strove for an even higher level of accessibility. This paper discusses some of the experiences and lessons learned from making WebSphere Commerce online help and software accessible. It examines some of the most common issues from the User Experience, Information Development, and Test perspectives.

Bot-Roche, Diba, Frances Mullally, Vijay Sivashankar and Donna Sutarno. STC Proceedings (2003). Articles>Documentation>Accessibility>Help

Section 508, Documentation and the US Software Market

This article outlines how you can ensure that your software documentation conforms to the new accessibility legislation in the US.

Unwalla, Mike. TechScribe (2003). Articles>Documentation>Accessibility>Section 508