Bobby
URL tested: http://thunder.nsstc.nasa.gov/LISbrowse/nov97tnqc.html, January 7, 2002 10:06:43 AM CST
Bobby Core v3.2, WAI Guidelines 1999/05/05

About this report

The Bobby report presents an accessibility evaluation grouped by the three priority levels defined by the Web Access Initiative (WAI), as well as browser compatibility and download statistics. As an automated evaluation tool, Bobby is able to detect many accessibility problems and to highlight other possible problems that must be checked. A "Bobby" hat in the original page (if displayed) indicates that Bobby was able to detect a Priority 1 problem with accessibility. A question mark indicates a Priority 1 item that needs to be checked by the user. Follow the links provided in the report to get details about any problem reported, including how to repair it, if needed. For more information on the report, please access our online documentation.

To be Bobby Approved, a page must pass all of the Priority 1 accessibility checkpoints established by the WAI.




Click on the error messages below to find out more information.

Priority 1 Accessibility

This web page does not contain any Priority 1 accessibility errors that Bobby can detect. However, certain items require human judgment; these are listed below. Please review these items; if none of these apply to your page, it qualifies for Bobby Approved status.

User Checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby Approval requires that none of them apply to your page. Please review these 2 item(s):

  1. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (1 instance)
    Line 17
  2. If you use color to convey information, make sure the information is also represented another way.

The following 4 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby Approved status.

  1. Ensure that descriptions of dynamic content are updated with changes in content.

  2. Use the simplest and most straightforward language that is possible.

  3. Avoid ASCII art.

  4. If you can't make a page accessible, construct an alternate accessible version.

If the Priority 1 issues listed do not apply to your page, then it qualifies as Bobby Approved and you are entitled to use the Bobby Approved icon. To obtain the icon and learn how to place it in your page, visit the Icon Guidelines page on the CAST web site.


Priority 2 Accessibility

Bobby Approved status is assigned on the basis of Priority 1 items in the Web Content Guidelines. For a higher level of accessibility you may also want to examine Priority 2 and Priority 3 items. 3 Priority 2 issue(s) that Bobby has identified are presented below.

  1. Separate adjacent links with more than whitespace. (1 instance)
    Line 12
  2. Use relative sizing and positioning (% values) rather than absolute (pixels). (176 instances)
    Line 20, Line 22, Line 23, Line 26, Line 41, Line 42, Line 43, Line 44, Line 45, Line 46, Line 47, Line 49, Line 50, Line 51, Line 56, Line 58, Line 59, Line 60, Line 62, Line 64, Line 65, Line 66, Line 68, Line 70, Line 71, Line 72, Line 74, Line 76, Line 77, Line 78, Line 80, Line 82, Line 83, Line 84, Line 86, Line 88, Line 89, Line 90, Line 92, Line 94, Line 95, Line 96, Line 101, Line 103, Line 104, Line 105, Line 107, Line 109, Line 110, Line 111, Line 113, Line 115, Line 116, Line 117, Line 119, Line 121, Line 122, Line 123, Line 125, Line 127, Line 128, Line 129, Line 131, Line 133, Line 134, Line 135, Line 137, Line 139, Line 140, Line 141, Line 146, Line 148, Line 149, Line 150, Line 152, Line 154, Line 155, Line 156, Line 158, Line 160, Line 161, Line 162, Line 164, Line 166, Line 167, Line 168, Line 170, Line 172, Line 173, Line 174, Line 176, Line 178, Line 179, Line 180, Line 182, Line 184, Line 185, Line 186, Line 191, Line 193, Line 194, Line 195, Line 197, Line 199, Line 200, Line 201, Line 203, Line 205, Line 206, Line 207, Line 209, Line 211, Line 212, Line 213, Line 215, Line 217, Line 218, Line 219, Line 221, Line 223, Line 224, Line 225, Line 227, Line 230, Line 231, Line 236, Line 239, Line 240, Line 242, Line 243, Line 244, Line 245, Line 246, Line 247
  3. Avoid use of deprecated language features if possible. (94 instances)
    Line 8, Line 10, Line 16, Line 20, Line 23, Line 26, Line 49, Line 50, Line 51, Line 58, Line 59, Line 60, Line 64, Line 65, Line 66, Line 70, Line 71, Line 72, Line 76, Line 77, Line 78, Line 82, Line 83, Line 84, Line 88, Line 89, Line 90, Line 94, Line 95, Line 96, Line 103, Line 104, Line 105, Line 109, Line 110, Line 111, Line 115, Line 116, Line 117, Line 121, Line 122, Line 123, Line 127, Line 128, Line 129, Line 133, Line 134, Line 135, Line 139, Line 140, Line 141, Line 148, Line 149, Line 150, Line 154, Line 155, Line 156, Line 160, Line 161, Line 162, Line 166, Line 167, Line 168, Line 172, Line 173, Line 174, Line 178, Line 179, Line 180, Line 184, Line 185, Line 186, Line 193, Line 194, Line 195, Line 199, Line 200, Line 201, Line 205, Line 206, Line 207, Line 211, Line 212, Line 213, Line 217, Line 218, Line 219, Line 223, Line 224, Line 225, Line 230, Line 231, Line 239, Line 240

User Checks

3 Priority 2 issue(s) that Bobby has identified are presented below:

  1. If a table is used for layout only, do not use structural markup to achieve formatting effects. (1 instance)
    Line 17
  2. Check that the foreground and background colors contrast sufficiently with each other.

  3. Add a descriptive title to links when needed.

The following 8 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

  1. Use a clear, consistent navigation structure.

  2. Make sure your document validates to formal published grammars.

  3. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).

  4. Use metadata to add computer-understandable information about the page.

  5. Group related elements when possible.

  6. Ensure that dynamic content is accessible or provide an alternate presentation or page.

  7. Offer a site map or table of contents, and provide a description of the general layout of the site, the access features used, and how to use them.

  8. Use the latest technology specification available whenever possible.


Priority 3 Accessibility

Bobby Approved status is assigned on the basis of Priority 1 items in the Web Content Guidelines. For a higher level of accessibility you may also want to examine Priority 2 and Priority 3 items. 2 Priority 3 issue(s) that Bobby has identified are presented below.

  1. Identify the language of the text. (1 instance)
    Line 1
  2. Provide a summary and caption for tables. (1 instance)
    Line 17

User Checks

4 Priority 3 issue(s) that Bobby has identified are presented below:

  1. Provide abbreviations for long row or column labels. (1 instance)
    Line 17
  2. Specify a logical tab order among form controls, links and objects.

  3. Consider adding keyboard shortcuts to frequently used links.

  4. Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns. (1 instance)
    Line 17

The following 9 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

  1. Create a consistent style of presentation between pages.

  2. Provide a link at the beginning of a group of related links to bypass the group.

  3. Use icons or graphics (with accessible alternatives) to facilitate comprehension of the page.

  4. Allow users to customize their experience of the web page.

  5. Use the ABBR and ACRONYM elements to denote and expand abbreviations and acronyms.

  6. Offer navigation bars for easy access to the navigation structure.

  7. Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

  8. If ASCII art is present, provide a means to skip over it.

  9. Offer different types of searches for different skill levels and preferences.


Browser Compatibility Errors

The following section contains a list of 6 browser compatibility errors. Browser compatibility errors help to determine when HTML tags and their attributes are not compatible with certain web browsers or HTML specifications. Browser compatibility errors do not affect the accessibility rating of a page.
  1. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (42 instances)
    Line 41, Line 42, Line 43, Line 44, Line 45, Line 46, Line 47, Line 56, Line 62, Line 68, Line 74, Line 80, Line 86, Line 92, Line 101, Line 107, Line 113, Line 119, Line 125, Line 131, Line 137, Line 146, Line 152, Line 158, Line 164, Line 170, Line 176, Line 182, Line 191, Line 197, Line 203, Line 209, Line 215, Line 221, Line 227, Line 236, Line 242, Line 243, Line 244, Line 245, Line 246, Line 247
  2. Unknown attribute BORDERCOLOR in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Line 17
  3. Unknown attribute HEIGHT in element TH. for browser(s): Lynx2.7, Explorer4.01 (1 instance)
    Line 22
  4. Unknown attribute HEIGHT in element TD. for browser(s): Lynx2.7 (42 instances)
    Line 41, Line 42, Line 43, Line 44, Line 45, Line 46, Line 47, Line 56, Line 62, Line 68, Line 74, Line 80, Line 86, Line 92, Line 101, Line 107, Line 113, Line 119, Line 125, Line 131, Line 137, Line 146, Line 152, Line 158, Line 164, Line 170, Line 176, Line 182, Line 191, Line 197, Line 203, Line 209, Line 215, Line 221, Line 227, Line 236, Line 242, Line 243, Line 244, Line 245, Line 246, Line 247
  5. Unknown attribute BORDERCOLORDARK in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Line 17
  6. Unknown attribute BORDERCOLORLIGHT in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Line 17

Download Time

The following three-column table gives download time statistics for the images, applets, and objects on this page. The first column contains the URL of each item, the second column the item size in kilobytes, and the third column the approximate download time for each item when using a 28,800 baud modem. At the end of the report, an arbitrary delay of 0.5 seconds is added for each file to account for slow-downs caused by HTTP connection times.

URL
Size
Time (secs)
http://thunder.nsstc.nasa.gov/LISbrowse/nov97tnqc.html 5.86 K 1.63
Total
5.86 K
1.63
HTTP Request Delays
--
0.50
Total + Delays
--
2.13