SF State - Accessible Technology Initiative (ATI)

Image: Photos of the SF State campus and students using a headset, a braille keyboard and a blind cane

SF State Web Accessibility Standards

Part1: Section 508 – 16 Checkpoints

  • (a) A text equivalent for every non-text element shall be provided (e.g., via alt, longdesc, or in element content).

  • (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

  • (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

  • (d) Documents shall be organized so they are readable without requiring an associated style sheet.

  • (e) Redundant text links shall be provided for each active region of a server-side image map.

  • (f) 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.

  • (g) Row and column headers shall be identified for data tables.

  • (h) 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.

  • (i) Frames shall be titled with text that facilitates frame identification and navigation.

  • (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

  • (k) 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.
  • (l) 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.

  • (m) 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).

  • (n) When electronic forms are designed to be completed online, 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.

  • (o) A method shall be provided that permits users to skip repetitive navigation links.
  • (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Additional SF State Accessibility 8 Checkpoints

  1. Validate your HTML

  2. Create meaningful page titles. Page titles should contain unique, short and meaningful descriptions of the content or purpose of the page.

  3. Use meaningful and unique text for links.

  4. Ensure there is adequate color contrast on the page

  5. Inform the user about pop-ups or new windows

  6. Create accessible PDF, Word and PowerPoint Files

  7. Create structured content

  8. Ensure logical reading order of layout tables
SF State Home