Web Development
Overview
Micro Sites
Conversion Optimization
The XCO Process
Section 508 Development
Benefits of Section 508
Section 508 Standards
XHTML and CSS

Contact Info

USWeb, LLC.
23844 South Power Rd.
Ste. 102-618
Queen Creek, AZ, 85242
1-800-585-7782

Proud members of...

Interactive Advertising Bureau SEMPO Contributor

Section 508 Standards For Web Page Design and Development


  • A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  • Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  • Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  • Documents shall be organized so they are readable without requiring an associated style sheet.
  • Redundant text links shall be provided for each active region of a server-side image map.
  • 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.
  • Row and column headers shall be identified for data tables.
  • 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.
  • Frames shall be titled with text that facilitates frame identification and navigation.
  • Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  • 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.
  • 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.
  • 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).
  • 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.
  • A method shall be provided that permits users to skip repetitive navigation links.
  • When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Summary of the WCAG 1.0 of the WAI of the W3C

  • Provide equivalent alternatives to auditory and visual content
  • Ensure that text and graphics are understandable when viewed without color.
  • Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.
  • Clarify natural language usage.
  • Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents.
  • Ensure that pages are accessible even when newer technologies are not supported or are turned off.
  • Ensure user control of time-sensitive content changes.
  • Ensure direct accessibility of embedded user interfaces.
  • User features that enable activation of page elements via a variety of input devices.
  • Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly.
  • Use W3C technologies and guidelines.
  • Provide context and orientation information.
  • Provide clear navigation mechanisms.
  • Ensure that documents are clear and simple.