This page provides examples of the most common ways that the Section 508 guidelines are followed. There are more solutions out there. < Back to Accessibility Resources
This page is still under development. Though incomplete, it is provided as a working copy. We welcome comments and suggestions.
For a more thorough analysis of Section 508 web guidelines, please see Jim Thatcher's web site.
This applies to images <IMG> and image maps <MAP>/<AREA>, as well as objects <OBJECT> and embedded content <EMBED>. Also, if multimedia content and/or plug-ins are used, an alternative text version should be available (e.g. transcript for audio/video presentations, non-Flash version, etc.).

<img src="../portfolio/joel/images/i0gallery_landscape.jpg"
width="100" height="66" alt="Artistic rendering of
a lake">
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=4,0,2,0"
width="231" height="29">
<param name=movie value="text1.swf">
<param name=quality value=high>
<param name="BGCOLOR" value="">
<param name="SCALE" value="exactfit">
<embed src="text1.swf" quality=high pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"
type="application/x-shockwave-flash" scale="exactfit"
width="231" height="29" bgcolor="">
<noembed>
This will show up if both the object and embed tags are not
functional. <a href="alternate.html">Link to alternate text
content.</a>
</noembed>
</embed>
</object>
For video presentations, make sure captions are synchronized with the video. Also, if audio cues are provided, make sure they are inserted at the appropriate points in the audio track.
(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 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.
(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.