AccMonitor Report for http://www.contentquality.com/tutorial/a11.htm

**Verification Checklist**
Checkpoints	Passed
508 Standards, Section 1194.22	Yes	No	Other
A. 508 Standards, Section 1194.22, (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Rule: 1.1.1 - All IMG elements are required to contain either the alt or the longdesc attribute. Failure - IMG Element at Line: 124, Column: 33 Failure - IMG Element at Line: 186, Column: 33		No
B. 508 Standards, Section 1194.22, (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.			N/A
C. 508 Standards, Section 1194.22, (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. 508 Standards, Section 1194.22, (d) Documents shall be organized so they are readable without requiring an associated style sheet. Note: Document uses external stylesheets, inline style information, or header style information.
E. 508 Standards, Section 1194.22, (e) Redundant text links shall be provided for each active region of a server-side image map.			N/A
F. 508 Standards, Section 1194.22, (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.			N/A
G. 508 Standards, Section 1194.22, (g) Row and column headers shall be identified for data tables.			N/A
H. 508 Standards, Section 1194.22, (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.			N/A
I. 508 Standards, Section 1194.22, (i) Frames shall be titled with text that facilitates frame identification and navigation.			N/A
J. 508 Standards, Section 1194.22, (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Note: SCRIPT element(s) found in document body, a visual verification must be done to ensure the script does not cause the screen to flicker.
K. 508 Standards, Section 1194.22, (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.
(k) Option A - Check for the string 'Text Version' within the document.			N/V
(k) Option B - Check for a Global Text Version Link within the document.			N/V
(k) Option C - Check for an Accessibility Policy Link within the document.			N/V
L. 508 Standards, Section 1194.22, (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. Rule: 6.3.3 - Locate elements that use HTML event handlers. Note: This rule has not been selected to be verified for this checkpoint. Rule: 6.3.4 - When SCRIPT Elements are used, the NOSCRIPT element is required in the document. Warning - SCRIPT Element(s) are found in document and the NOSCRIPT element is not.
M. 508 Standards, Section 1194.22, (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). Rule: 6.3.8 - All pages that have links to files that require a special reader or plug-in are required to contain the specified text indicating a link to the reader or plug-in. Note: This rule has not been selected to be verified for this checkpoint.	Yes
N. 508 Standards, Section 1194.22, (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.			N/A
O. 508 Standards, Section 1194.22, (o) A method shall be provided that permits users to skip repetitive navigation links. Rule: (o).1 - All pages are required to contain a bookmark link to skip navigation that has the specified text in either the link text or the 'title' attribute value. Skip Navigation Text: Note: This rule has not been selected to be verified for this checkpoint.
P. 508 Standards, Section 1194.22, (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Checkpoint Result Legend: Yes = Passed Automated Verification, No = Failed Automated Verification, Warning = Failed Automated Verification, however, configured not to cause page to fail (Priority 2 or 3 only), N/V = Not selected for verification, N/A = No related elements were found in document (Visual only), No Value = Visual Checkpoint

Source Listing

1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2: <html lang="en-US"> 3: 4: <head> 5: <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.weburbia.com/safe/ratings.htm" l r (s 0))'> 6: <meta http-equiv="Content-Language" content="en-us"> 7: <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> 8: <LINK rel="stylesheet" href="http://www.cynthiasays.com/css/cynthia.css" type="text/css"> 9: <meta name="keywords" content="Accessibility, Section 508, ICDRI, Internet Society Disability and Special Needs , HiSoftware, Online Accessibility Test"> 10: <meta name="description" content="Cynthia, The Accessibility Agent"> 11: <meta name="language" content="en-US"> 12: <meta name="robots" content="ALL"> 13: <meta name="rating" content="GENERAL"> 14: <meta name="distribution" content="GLOBAL"> 15: <meta name="classification" content="Online Resource"> 16: <meta name="copyright" content="2003 - HiSoftware Inc"> 17: <meta name="author" content="HiSoftware Inc - Unless otherwise noted"> 18: <title>Tutorial - Section 508 A - WCAG 1.0/1.1</title> 19: <style> 20:  29: </style> 30: <meta name="subject" content="Computers:Internet:WWW"> 31: </head> 32: 33: <body> 34: 35:  36: <a href="#Content">skip 37: navigation</a> | <a href="../Default.asp">home</a> | 38: <a href="../help/Help.htm">help</a> 39: | <a href="../cynthia/cynthia.htm">about this site</a> 40: | 41: <a title="Contact and Feedback" href="http://www.hisoftware.com/co/contacting_us.htm">contact us</a> 42: | <a href="http://www.hisoftware.com/press/index.html">news</a> | <a href="../search/hisearch.asp">search</a> 43: | <a href="http://www.hisoftware.com/">HiSoftware</a><hr class="rule1"> 44: <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" width="100%" class="dottedwhite" id="AutoNumber2"> 45: <tr> 46: <td width="100%"> 47: <table border="0" style="border-collapse: collapse" width="100%" id="AutoNumber1" cellpadding="7" class="greyshade"> 48: <tr> 49: <td width="100%"> 50: <a href="http://www.hisoftware.com/index.html"> 51: <img alt="HiSoftware Logo and Link to main page of Web Site" hspace="7" src="../hi-logo.gif" vspace="4" border="0" longDesc="http://www.hisoftware.com/co/hisoftwarelogo.htm" align="right" width="220" height="84"></a>Welcome 52: to the HiSoftware® Cynthia Says™ Portal 53: The HiSoftware CynthiaSays portal is a 54: joint Education and Outreach project of HiSoftware, ICDRI, and the Internet 55: Society Disability and Special Needs Chapter.  56: 57: Read 58: <a title="Book Information - Opens new Window" target="_blank" href="http://www.hisoftware.com/uaccess/Index.html"> 59: Understanding Accessibility</a> today!  60: <a href="http://www.hisoftware.com/subscribe.htm">Download 61: Now </a> </td> 62: <td width="100%"></td> 63: </tr> 64: </table> 65: </td> 66: </tr> 67: </table> 68: <table style="BORDER-COLLAPSE: collapse" cellSpacing="0" cellPadding="0" width="100%" border="0"> 69: <tr> 70: <td vAlign="top"> 71: <table id="AutoNumber3" style="BORDER-COLLAPSE: collapse" cellSpacing="0" cellPadding="7" width="100%" border="0"> 72: <tr> 73: <td width="100%"><a name="Content"></a>Section 508 74: Standard (a) & W3C WCAG 1.0 Guidelines 1.1 75: Note some Images on the page will be missing 76: alternative text, this is for demonstration purposes and the text below 77: clearly defines the problem and what the alternative text would be if 78: the item was correct. 79: This guide is derived from the book 80: <a target="_blank" href="http://www.hisoftware.com/uaen/WebHelp/uaen.htm"> 81: Understanding Accessibility, Published by HiSoftware Publishing..</a>. 82: The Entire book can be viewed online in accessible HTML Help format. 83: A text equivalent for every non-text element 84: shall be provided (e.g., via "alt", "longdesc", or in element content). 85: <ul> 86: <li>All IMG elements are required to contain 87: either the 'alt' or the 'longdesc' attribute. </li> 88: <li>All INPUT elements are required to contain 89: the 'alt' attribute or use a LABEL. </li> 90: <li>All OBJECT elements are required to contain 91: element content. </li> 92: <li>All APPLET elements are required to contain 93: both element content and the alt attribute. </li> 94: <li>All IFRAME elements are required to contain 95: element content. </li> 96: <li>All Anchor elements found within MAP elements 97: are required to contain the 'alt' attribute. </li> 98: <li>All AREA elements are required to contain the 99: 'alt' attribute.  </li> 100: </ul> 101: The Examples 102: <ol> 103: <li><a href="#one">Simple image requiring alt 104: text</a></li> 105: <li><a href="#two">Same Image also servers as 106: navigation link</a></li> 107: <li><a href="#three">An image requiring a long 108: description</a></li> 109: <li><a href="#four">Object MS Office Spread Sheet</a></li> 110: <li><a href="#five">Applet</a></li> 111: <li><a href="#six">Input Elements</a></li> 112: <li><a href="#seven">Inline Frame</a></li> 113: <li><a href="#eight">Image Maps</a></li> 114: <li><a href="#nine">Image as bullet</a></li> 115: </ol> 116: 117: <a name="one">1.  Simple Image Requiring 118: Alternative Text</a> 119: The first Image represents “conserve”. The 120: images purpose is simply to add the meaning of conserve. The rule states 121: all IMG elements are required to contain either the 'alt' or the 122: 'longdesc' attribute. 123:   124: <img src="images/image009.gif" border="0" width="165" height="122"> 125:   126: <blockquote> 127: This image requires alternative text. 128: Current HTML – EXAMPLE 1 129: In the current HTML the alt attribute is 130: missing. 131: <blockquote> 132: <img src="images/image009.gif" border="0" 133: width="165" height="122"> 134: </blockquote> 135: Corrected HTML – EXAMPLE 1 136: In the corrected HTML the alt attribute is 137: used. 138: <blockquote> 139: <IMG border="0" src="images/image009.gif" 140: border="0" width="165" height="122" alt=”Conserve Icon”> 141: </blockquote> 142: </blockquote> 143: <a href="#Content">top</a> 144: <a name="two">2. Same image: also serves as a 145: navigation link</a> 146: This example demonstrates an image with a 147: navigation purpose. The purpose is to provide a navigation link to the 148: HiSoftware home page. The rule states all IMG elements are required to 149: contain either the 'alt' or the 'longdesc' attribute. 150: <blockquote> 151: Current HTML – EXAMPLE 2 152: In the current HTML the alt attribute is 153: missing. 154: <blockquote> 155: <IMG border="0" src="images/image009.gif" 156: width="165" height="122"> 157: </blockquote> 158: Corrected HTML – EXAMPLE 2 159: In the corrected HTML the alt attribute is 160: used and the alt text also shows the purpose of the image. 161: <a href="http://www.hisoftware.com/"> 162: <blockquote> 163: <IMG border="0" src="images/image009.gif" 164: 165: </blockquote> 166: alt="Conservation Symbol and link to 167: HiSoftware Home Page" width="165" height="122"></a> 168: </blockquote> 169: <blockquote> 170: Note: To create effective alternative 171: text for your non-text elements makes sure you: 172: <ul> 173: <li>Follow the <a href="imagealttext.htm"> 174: guide on this site</a> for developing alternative text</li> 175: <li>Use a spell checker</li> 176: </ul> 177: </blockquote> 178: <a href="#Content">top</a> 179: <a name="three">3. An image requiring a long 180: description</a> 181: This example demonstrates the use of “longdesc.” 182: It would be difficult to describe this image with alternative text only. 183: In this case a long description should be used. The rule states that all 184: IMG elements are required to contain either the 'alt' or the 'longdesc' 185: attribute. 186: <img src="images/image010.gif" border="0" width="192" height="192"> 187: <blockquote> 188: Current HTML – EXAMPLE 3 189: In the current HTML the alt attribute is 190: missing and there is no longdesc attribute. 191: <blockquote> 192: <Img border="0" src="images/image010.gif" 193: width="192" height="192"> 194: </blockquote> 195: Corrected HTML – EXAMPLE 3 196: In the corrected HTML the alt attribute and 197: longdesc attribute are used. In addition to this a d-Link was used. 198: <blockquote> 199: <Img border="0" src="images/image010.gif" 200: alt="Space Related Objects - See Long Description" width="192" 201: height="192" longdesc="AboutSpace.html"> 202: <A  href="AboutSpace.html">[D]</A> 203: </blockquote> 204: </blockquote> 205: <a href="#Content">top</a> 206: <a name="four">4. Object MS Office Spreadsheet</a> 207: Example four demonstrates the proper 208: accessibility coding for an ActiveX object. The object is of a Microsoft 209: Office Web component. The rule states All OBJECT elements are required 210: to contain element content. 211: Current HTML – EXAMPLE 4 212: The element content is missing from the current 213: HTML. 214: <blockquote> 215: <object classid="clsid:0002E551-0000-0000-C000-000000000046" 216: id="Spreadsheet1" width="319" height="249"> 217: <param name="DataType" value="XMLDATA"> 218: </object> 219: </blockquote> 220: Corrected HTML – EXAMPLE 4 221: In the corrected HTML the element content is 222: present. 223: <blockquote> 224: <object classid="clsid:0002E551-0000-0000-C000-000000000046" 225: id="Spreadsheet1" width="319" height="249"> 226: <param name="DataType" value="XMLDATA"> 227: Your browser does not support this object. 228: This is an object and it represents data that 229: is also available at 230: http://www.hisoftware.com/uaccess/demo1.htm 231: </object> 232: </blockquote> 233: <a href="#Content">top</a> 234: <a name="five">5. Applet</a> 235: Example five demonstrates the proper 236: accessibility coding for a Java applet. The rule states that all APPLET 237: elements are required to contain both element content and the alt 238: attribute. 239: Current HTML – EXAMPLE 5 240: In the current HTML the element content and alt 241: attribute are missing. 242: <blockquote> 243: <applet width="128" height="128" 244: code="" 245: codebase="http://Example.js.class/"> 246: </applet> 247: </blockquote> 248: Corrected HTML – EXAMPLE 5 249: In the corrected HTML the element content and 250: the alt attribute are present. 251: <blockquote> 252: <applet width="128" height="128" 253: code=""  alt=”My Applet Description” 254: codebase="http://Example.js.class/"> 255: This is a navigation applet. Alternative 256: navigation can be found at: 257: http://www.hisoftware.com/uaccess/navigate.html 258: </applet> 259: </blockquote> 260: <a href="#Content">top</a> 261: <a name="six">6. Input Elements (also 508 (n))</a> 262: Example six demonstrates the proper 263: accessibility coding for a standard HTML form. The rule states that all 264: INPUT elements are required to contain the 'alt' attribute or use a 265: LABEL. 266: Current HTML – EXAMPLE 6 267: In the current HTML the alternative text for the 268: input element is not present. 269: <blockquote> 270:  <Form method="POST" action="-WEBBOT-"> 271: <Input type="text" name="T1" size="20"> 272: 273: </form> 274: </blockquote> 275: Corrected HTML – EXAMPLE 6 276: <blockquote> 277: <Form method="POST" action="-WEBBOT-"> 278: <Label for="T1"> User Name: </label> 279: 280: <Input type="text" name="T1" size="20" 281: alt=”First Name”> </form> 282: </blockquote> 283: <a href="#Content">top</a> 284: <a name="seven">7. Inline Frame (IFRAME)</a> 285: Example seven demonstrates the proper 286: accessibility coding for Inline frames. Inline frames prove an excellent 287: TABLE or FRAME alternative. The rule states that all IFRAME elements are 288: required to contain element content. 289: Current HTML – EXAMPLE 7 290: In the current HTML the element content for the 291: IFRAME element is not present. 292: <blockquote> 293: <Iframe name="I1" SRC="sample.htm"> 294: </iframe> 295: </blockquote> 296: Corrected HTML– EXAMPLE 7 297: In the corrected HTML the element content is 298: present. 299: <blockquote> 300: <Iframe name="I1" SRC="sample.htm"> 301: Your browser does not support inline frames or 302: is currently configured not to display inline frames. Content can be 303: viewed at actual source page: 304: http://www.hisoftware.com/sample.htm 305: </iframe> 306: </blockquote> 307: <a href="#Content">top</a> 308: <a name="eight">8. Image Map Example (Section 309: 508 (f))</a> 310: Example eight demonstrates the proper 311: accessibility coding for an Image Map. The rule states that all AREA 312: elements are required to contain the 'alt' attribute.   313: Current HTML – EXAMPLE 8 314: In the current HTML the alternative text for the 315: area elements and alternative text for the image are not present. 316: <blockquote> 317: <map name="FPMap0"> 318: <area href="#Go Here for Links!!!" shape="rect" 319: coords="13, 5, 172, 75"> 320: <area href="#Go Here for Links!!!" shape="rect" 321: coords="8, 92, 119, 187"> 322: <area href="#Go Here for Links!!!" shape="rect" 323: coords="125, 91, 191, 180"> 324: </map> 325: <img border="0" 326: src="../../images/j0301076.gif" usemap="#FPMap0" width="192" 327: height="192"> 328: </blockquote> 329: Corrected HTML – EXAMPLE 8 330: In the corrected HTML the alternative text for 331: the area elements and alternative text for the image are present. 332: <blockquote> 333: <map name="FPMap0"> 334: <area href="#Go Here for Links!!!" shape="rect" 335: coords="13, 5, 172, 75" alt=”My Alternative Text”> 336: <area href="#Go Here for Links!!!" shape="rect" 337: coords="8, 92, 119, 187" alt=”My Alternative Text” 338: <area href="#Go Here for Links!!!" shape="rect" 339: coords="125, 91, 191, 180" alt=”My Alternative Text”> 340: </map> 341: <img border="0" 342: src="../../images/j0301076.gif" usemap="#FPMap0" width="192" 343: height="192" alt=”Space Image”> 344: </blockquote> 345: <a href="#Content">top</a> 346: <a name="nine">9. Images As Bullets Example</a> 347: Example nine demonstrates the proper 348: accessibility coding for a bullet list, where the bullets are actually 349: images. The rule states All IMG elements are required to contain either 350: the 'alt' or the 'longdesc' attribute. 351: Current HTML – EXAMPLE 9 352: In the current HTML there are five products 353: listed, these products have an image before the product name to create a 354: fashionable bulleted list. 355: <blockquote> 356: HiSoftware Accessibility Products 357: <img border="0" src="BD10263_.GIF"> 358: Understanding Accessibility Book 359: <img border="0" src="BD10263_.GIF"> 360: AccVerify 361: <img border="0" src="BD10263_.GIF"> 362: AccRepair 363: <img border="0" src="BD10263_.GIF"> 364: AccMonitor 365: <img border="0" src="BD10263_.GIF"> 366: AccessibilityWATCH 367: </blockquote> 368: Corrected HTML – EXAMPLE 9 369: The guidelines state that the purpose of the 370: image is very important, the purpose in this case has nothing to do with 371: the visual representation, and it is merely a bullet. This is definitely 372: an exception to previously stated rules. The exception is: describing 373: the image in the alternative text would not be effective instead we will 374: describe the purpose. 375: <blockquote> 376: HiSoftware Accessibility Products 377: <img border="0" src="BD10263_.GIF" alt=”*”> 378: Understanding Accessibility Book 379:   380: <img border="0" src="BD10263_.GIF" alt=”*”> 381: AccVerify 382:   383: <img border="0" src="BD10263_.GIF" alt=”*”> 384: AccRepair 385:   386: <img border="0" src="BD10263_.GIF" alt=”*”> 387: AccMonitor 388:   389: <img border="0" src="BD10263_.GIF" alt=”*”> 390: AccessibilityWATCH 391: </blockquote> 392: In this case the asterisks clearly describe the 393: value and purpose of the images as bullets.  394: <a href="#Content">top</a> 395:   396:  397: 398: <a target="_self" href="http://www.cynthiasays.com/pfv/gpfv.exe?pfurl=http://www.cynthiasays.com/tutorial/a11.htm"> 399: <img alt="Printer" src="../images/prf.gif" border="0" width="18" height="15"></a> 400: Printer Friendly Version... 401: </td> 402: </tr> 403: </table> 404: </td> 405: </tr> 406: </table> 407:  408: 409: <hr noshade class="rule1" size="1"> 410: (c) Copyright 2003-2007 HiSoftware Inc. HiSoftware and CynthiaSays are trademarks of 411: HiSoftware Inc. All other 412: individual names and trademarks 413: are the property of their respective owners. Privacy Statement: HiSoftware's CynthiaSays.Com is currently running on the HiSoftware family of Web Servers 414: and conforms to its privacy policy, for more information click on the privacy 415: policy link at the bottom of this page. 416: 417: 418: The HiSoftware Cynthia Says Portal 419: complies with WCAG 1.0 Priority 1 Guidelines and Section 508 Standards, 420: <a href="../org/accessibility.htm">view our site accessibility statement</a>  421: 422: 423: <a href="../org/termsofuse.htm">HiSoftware CYNTHIASAYS.COM SERVICE TERMS OF USE</a> | 424: <a target="_blank" href="http://www.hisoftware.com/co/privacy.htm">PRIVACY POLICY...</a> | <a href="../cynthia/Sitehelp.htm">SITE HELP</a> | <a href="../cynthia/SiteMap.htm">SITE 425: MAP</a> | <a href="../resources/addcynthia.htm">ADD Cynthia 426: TO YOUR SITE</a> 427: 428: 429: 430: 431: <a href="../org/cynthiatested.htm"> 432: <img border="0" src="../images/Ctested.gif" alt="Cynthia Tested!" width="88" height="32"></a> 433: <a href="http://jigsaw.w3.org/css-validator/"> 434: <img alt="Valid CSS!" src="http://jigsaw.w3.org/css-validator/images/vcss" border="0" width="88" height="31"></a> 435: <script language='javascript' src='http://server.iad.liveperson.net/hc/18692324/x.js?cmd=file&file=chatScript3&site=18692324&&category=en;woman;5'> </script> 436: 437: </body></html>