Gavilan Access Checklist

The questions below concern the accessibility of your distance learning course website to people with disabilities. Please answer by checking the yes or no box. If an explanation is necessary, please also check the box in the "Expl" column and attach the explanation. For more information on accessibility, see The Access Board provisions at (http://www.access-board.gov/sec508/guide/1194.22.htm#(a)%00) and the WebAIM Section 508 Checklist at (http://www.webaim.org/standards/508/checklist).

Yes

Expl

Requirement and Purpose

1. A text equivalent is provided for every non-text element, including both images and animated objects. This will enable a screen reader to read the text equivalent to a blind student.

2. Equivalent alternatives for any multimedia presentation are synchronized with the presentation.

3. Webpages are designed so that all information conveyed with color is also available without color. For example, so a blind or color-blind student could understand a color-coded representation of DNA.

4. Documents are organized so they are readable without requiring an associated style sheet.

5. Redundant text links are provided for each active region of a server-side image. This will enable a screen reader to read the links to a blind student.

6. Client-side image maps are provided instead of server-side images.

7. Row and column headers are identified for data tables.

8. Markup is used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. The identification will enable screen readers to discern the headers, which disclose the purpose of the data in the rows and columns.

9. Frames have titles with text that facilitates frame identification and navigation. This will help blind students understand the organizational purpose of the frame.

10. Pages are designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. The movement can be distracting for students with certain disabilities.

11. A text-only page, with equivalent information or functionality, is provided to make a website comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page will be updated whenever the primary page changes.

12. When pages use scripting languages to display content, or to create interface elements, the information provided by the script is identified with functional text that can be read by assistive technology.

13. When a webpage requires that an applet, plug-in or other application be present on the client system to interpret page content, the page provides a link to a plug-in or applet that complies.

14. When electronic forms are designed to be completed online, the form allows 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.

15. A method is provided that permits users to skip repetitive navigation links.

16. When a timed response is required, the user is alerted and given sufficient time to indicate more time is required.

17. Ensure that webpages meet 508 standards by testing through Cynthia Says (http://www.cynthiasays.com/), WebXACT (http://webxact.watchfire.com/), or through the AccVerify/AccRepair programs (available in the SRC).

You can download the Gavilan Accessibility checklist in PDF.
You can download the Gavilan Accessibility Checklist in Word.