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).
Tutorials and resources on checkpoint a
- (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
Tutorials and resources on checkpoint b
- (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
Tutorials and resources on checkpoint c
- (d) Documents shall be organized so they are readable without requiring an associated style sheet.
Tutorials and resources on checkpoint d
- (e) Redundant text links shall be provided for each active region of a server-side image map.
Tutorials and resources on checkpoint e
- (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.
Tutorials and resources on checkpoint f
- (g) Row and column headers shall be identified for data tables.
Tutorials and resources on checkpoint g
- (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.
Tutorials and resources on checkpoint h
- (i) Frames shall be titled with text that facilitates frame identification and navigation.
- Tutorials and resources on checkpoint i
- (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
Tutorials and resources on checkpoint j
- (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.
Tutorials and resources on checkpoint l
- (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).
Tutorials and resources on checkpoint m
- (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.
Tutorials and resources on checkpoint n
- (o) A method shall be provided that permits users to skip repetitive navigation links. Tutorials and resources on checkpoint o
- (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Tutorials and resources on checkpoint p
Additional SF State Accessibility 8 Checkpoints
- Validate your HTML
Tutorials and resources on checkpoint 1
Create meaningful page titles. Page titles should contain unique, short and meaningful descriptions of the content or purpose of the page.
Tutorials and resources on checkpoint 2
- Use meaningful and unique text for links.
Tutorials and resources on checkpoint 3
- Ensure there is adequate color contrast on the page
Tutorials and resources on checkpoint 4
Inform the user about pop-ups or new windows
Tutorials and resources on checkpoint 5
Create accessible PDF, Word and PowerPoint Files
Tutorials and resources on checkpoint 6
Create structured content
Tutorials and resources on checkpoint 7
Ensure logical reading order of layout tables
Tutorials and resources on checkpoint 8