Skip navigation | Go to content Hamilton & Bond
About Us Portfolio Services Client Access Resources

Back to Section 508 Compliance       Bobby WorldWide Approved 508

Section 1194.22
Web-based Internet information and applications – Detail
Criteria Supporting Features Remarks and Explanations
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). ALT tags and long description are provided on images as appropriate. Meets criteria by enabling audible descriptions.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. We will synchronize textual descriptions of motion which may be appearing on the screen. Meets criteria by providing audible description of motion and captions for sound depicted on the screen.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Avoid color which is tied to decision making. Use only appropriate high contrast color palettes. Meets criteria by removing perception of color from decision making.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. We avoid using frames or tables as the sole means of organizing document content. Meets criteria by reducing the possibility of disorderly content display.
(e) Redundant text links shall be provided for each active region of a server-side image map. We do not use server side image maps. Meets criteria by avoiding server side image maps.
(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. We do not use server side image maps. When client side image maps are used we provide alternative text links. Meets criteria by avoiding server side image maps.
(g) Row and column headers shall be identified for data tables. Row and column headers are identified with the attribute "ID" and "Headers" or "Scope". Meets criteria by allowing screen reader to logically match data with column headers in a table format.
(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. For complex tables, row and column headers are identified with the attribute "ID", "Axis" and "Headers". Meets criteria by allowing screen reader to logically match data with column headers in a table format.
(i) Frames shall be titled with text that facilitates frame identification and navigation. Framesets are avoided whenever possible. When use is essential, framesets are properly titled. Meets criteria by identifying frames and their intended navigation to provide logical screen interpretation.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. If motion is essential to the web page, we control motion frame rates to avoid screen flicker. Meets criteria by making web pages more friendly and safer for persons with photosensitive epilepsy.
(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. Our database content solutions automatically provide a "text only" equivalent for every page of your website which automatically reflects your graphical pages without additional design or content maintenance. In addition to meeting the criteria, "text only" pages offer many more advantages including XML technologies such as cell phone and PDA communication. They are also preferred by Search Engines.
(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. Because javascript can be disabled by the user and because javascript "standards" change often, we avoid it for presentation of essential content. Meets criteria by keeping content presentation simple and compatible with assistive technologies.
(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). HTML markup is adequate to present most information. When additional software is required, such as PDF files, we provide a link to authorized download sites. Meets the criteria and avoids requirements for web viewers to locate, install and configure additional software.
(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. Form elements are marked with "label" and "name" attributes. Organize forms in a manner that provides for logical interpretation by assistive screen readers. Meets criteria by allowing screen reader to logically match category data with input fields in a form.
(o) A method shall be provided that permits users to skip repetitive navigation links. We include skip links in every page which might contain repetitive navigation. Meets criteria by allowing assistive technologies to skip to the desired content of a web page by simple user command.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Alternative text is used to alert visitors whenever a timed response is necessary. Meets criteria by informing web visitors of a viewing requirement.
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.

Chicago Advertising and Search Engine Management Advertising and Search Engine Management Home Contact Us | Hosting | Design | Search Engine | Site Index | Search | Government
© 1984-2012 Hamilton & Bond, Inc. All rights reserved. Get Reliable Google Advice
Advertising, Search Engine, Marketing, Hosting