Accessibility

All Strategic Information/Monitoring & Evaluation Field Officer Web sites must be accessible to users, as described in Section 508 of the Rehabilitation Act, and compatible with screen readers and other assistive technologies. Section 508 requires that Web sites (Internet and intranet) launched or revised after June 21, 2001, conform to certain accessibility standards. For more information about Section 508 and Web accessibility, see http://www.section508.gov/.

The following numbered standards are direct quotes excerpted from Section 508 of the Rehabilitation Act, §1194.22. The bulleted points below them are added here as helpful guidelines for compliance with Section 508.

1. A text equivalent for every non-text element [such as graphics and charts] shall be provided (e.g., via "alt", "longdesc", or in element content).
• Every image, Java applet, Flash file, video file, audio file, plug-in, etc., has an alt description.
• Complex graphics (graphs, charts, etc.) are accompanied by detailed text descriptions.
• The alt descriptions succinctly describe the purpose of the objects, without being too verbose (for simple objects) or too vague (for complex objects).
• Decorative graphics with no other function have empty alt descriptions (alt= ""), but they never have missing alt descriptions.
2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
• If color is used to convey important information, an alternative indicator is used, such as an asterisk (*) or other symbol.
• Contrast is good.
4. Documents shall be organized so they are readable without requiring an associated style sheet.
• Style sheets may be used for color, indentation, and other presentation effects, but the document is still understandable (even if less visually appealing) when the style sheet is turned off.
5. Redundant text links shall be provided for each active region of a server-side image map.
• Separate text links are provided outside of the server-side image map to access the same content that the image map hot spots access.
6. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
• Standard HTML client-side image maps are used, and appropriate alt tags are provided for the image as well as the hot spots.
7. Row and column headers shall be identified for data tables.
• Data tables have the column and row headers appropriately identified (using the tag).
• Tables used strictly for layout purposes do NOT have header rows or columns.
8. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
• Table cells are associated with the appropriate headers (e.g., with the id, headers, scope, and/or axis HTML attributes).
9. Frames shall be titled with text that facilitates frame identification and navigation.
• Each frame is given a title that helps the user understand the frame's purpose.
10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
11. A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
• A text-only version is created only when there is no other way to make the content accessible or when it offers significant advantages over the "main" version for certain disability types.
• The text-only version is up-to-date with the "main" version.
• The text-only version provides the functionality equivalent to that of the "main" version.
12. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
13. When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
• A link is provided to a disability-accessible page where the plug-in can be downloaded.
14. When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
• All form controls have text labels adjacent to them.
15. A method shall be provided that permits users to skip repetitive navigation links.
16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.