When creating content for consumption by a wide variety of users, you must plan to provide support for users with various disabilities. Such support is a legal requirement in many locations throughout the world.
You can follow several general guidelines when designing content for consumption by a variety of people with differing abilities. These guidelines apply to any content that you create for Publisher or other applications. You must also be aware of features that are specific to Publisher that ensure that the content that you provide supports accessibility requirements.
This section contains the following topics on designing for accessibility:
Obtain General Information
You can locate information about accessibility across the Information Technology industry in numerous published books.
This guide doesn't intend to duplicate those works. Various standards and legislation are documented, especially as part of the World Wide Web Consortium (W3C) and Section 508 of the United States Rehabilitation Act.
Avoid Common Misconceptions
Many designers make assumptions about technology and accessibility. Some of the more common misconceptions are listed in this section.
HTML content automatically equals accessible content.
Accessible tools automatically create accessible content.
Automated testing tools can reliably determine accessibility.
None of these assumptions is correct. Developers can create non-accessible content using HTML. A tool that can produce accessible content might not do so by default, or might allow a developer to select options that turn off the accessible features within existing accessible content. Automated testing tools do not always interact with content the same way that end users do. As a result, the tools can erroneously report accessible elements as non-accessible. Therefore, accessibility is ultimately the responsibility of the content designer. When creating content, designers must be aware of certain common practices to ensure the content is accessible to all users.
Follow General Guidelines for Accessible Content
Always consider the fact that multiple disabilities exist and that multiple disabilities might manifest in the same individual. You must also remember that there're varying degrees of certain disabilities (such as the various types of color vision deficiency). Your designs must take all these possibilities into account.
This section contains guidelines on the following general areas of design:
Many different types of color vision deficiency exist, from an inability to see the difference between one common color pair such as red-green (the most common deficiency), all the way to full color blindness where a person can see only varying shades of gray and black. Using only color to convey critical information means that certain users are not fully aware of all the pertinent information about a subject. And, of course, a blind user needs any information conveyed by color to also be present in an alternate textual format.
As a developer, you must not create any content that provides key information by color alone. One example of a non-accessible design is to denote negative numbers solely by coloring the text red. Another example is a typical "stoplight" indicator where the only context information comes from its color — green for good and red for bad.
Use Color with Text
You can use color in designs if you also include another indication of the same information.
For example, you can include a minus sign or parentheses to denote negative numbers in tables and pivots. For stoplight displays, you can add descriptive text or different shaped icons in addition to the color. You can include text such as "Status: good." You can include green circles for "good," yellow triangles for "warning," and red octagons for "bad."
Because color vision deficiency can also manifest as an inability to distinguish between subtle shades of similar colors, overall color design of all screen elements must provide a large amount of contrast. You should strive to achieve a minimum of a 4.5:1 color luminosity contrast ratio. For example, use black text on a white background instead of dark gray text on a light gray background.
You can check the following web sites for assistance:
This site offers a tool that can test for the proper level of contrast:
This site offers a tool for viewing how a web site is displayed for individuals with various types of color vision deficiency:
Users with low visual acuity often use screen magnification software to make the screen easier to read. The fonts that you use should be readable even when magnified by accessibility tools by as much as 20 times.
Some fonts do not display well when magnified, while others do. For example, the Tahoma font magnifies well.
Use the Template Builder to Verify Report Accessibility
You use the Template Builder for Word to create RTF templates that can generate reports with accessibility features.
The Template Builder also provides an accessibility checker to review the template for features that enhance the accessibility of the report for report consumers who may need assistive technologies to view the report.
For more information, see Check Accessibility.