Bobby
URL tested: http://thunder.nsstc.nasa.gov/LISbrowse/oct01tnqc.html, January 7, 2002 10:06:41 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 6 item(s):

  1. If an image conveys important information beyond what is its alternative text, provide an extended description. (19 instances)
    Lines 133-134, Lines 135-137, Lines 138-139, Lines 140-142, Lines 143-144, Lines 145-146, Lines 147-148, Lines 149-150, Lines 151-152, Lines 153-154, Lines 155-156, Lines 157-158, Lines 159-160, Lines 165-166, Lines 167-168, Lines 169-170, Lines 175-176, Lines 176-178, Line 299
  2. For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns. (3 instances)
    Line 131, Line 200, Line 276
  3. If you use color to convey information, make sure the information is also represented another way.

  4. Be sure pages are readable and usable if style sheets are ignored.

  5. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (10 instances)
    Line 163, Line 131, Line 186, Line 184, Line 203, Line 214, Line 253, Line 200, Line 195, Line 276
  6. Provide alternative content for each SCRIPT that conveys important information or functionality.

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. Avoid use of deprecated language features if possible. (17 instances)
    Line 130, Line 188, Line 199, Line 205, Line 218, Line 223, Line 228, Line 235, Line 241, Line 255, Line 275, Line 283, Line 293, Line 294
  2. Use relative sizing and positioning (% values) rather than absolute (pixels). (5 instances)
    Line 131, Line 184, Line 195, Line 199, Line 276
  3. Make sure event handlers do not require use of a mouse. (6 instances)
    Line 135, Line 140, Line 145, Line 149, Line 153, Line 157

User Checks

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

  1. Add a descriptive title to links when needed.

  2. Check that the foreground and background colors contrast sufficiently with each other.

  3. Avoid using movement in images where possible. (18 instances)
    Lines 133-134, Lines 135-137, Lines 138-139, Lines 140-142, Lines 143-144, Lines 145-146, Lines 147-148, Lines 149-150, Lines 151-152, Lines 153-154, Lines 155-156, Lines 157-158, Lines 159-160, Lines 165-166, Lines 167-168, Lines 169-170, Lines 176-178, Line 299
  4. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (10 instances)
    Line 12, Line 42, Line 54, Line 84, Line 94, Line 100, Line 106, Line 112, Line 118, Line 124
  5. Avoid using tables to format text documents in columns unless the table can be linearized. (10 instances)
    Line 163, Line 131, Line 186, Line 184, Line 203, Line 214, Line 253, Line 200, Line 195, Line 276
  6. Style sheets should be used to control layout and presentation wherever possible.

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. (10 instances)
    Line 163, Line 131, Line 186, Line 184, Line 203, Line 214, Line 253, Line 200, Line 195, Line 276

User Checks

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

  1. Provide abbreviations for long row or column labels. (10 instances)
    Line 163, Line 131, Line 186, Line 184, Line 203, Line 214, Line 253, Line 200, Line 195, Line 276
  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. (10 instances)
    Line 131, Line 163, Line 184, Line 186, Line 195, Line 200, Line 203, Line 214, Line 253, Line 276

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 9 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. Attribute ALINK in element BODY needs a valid color. for browser(s): Explorer4.01, Navigator4.0 (1 instance)
    Line 53
  2. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (1 instance)
    Line 293
  3. Unknown attribute NAME in element IMG. for browser(s): Lynx2.7 (1 instance)
    Lines 167-168
  4. Attribute NOSHADE in element HR is assigned an incorrect value. for browser(s): Lynx2.7 (2 instances)
    Line 279, Line 289
  5. Unknown attribute TYPE in element STYLE. for browser(s): Lynx2.7 (1 instance)
    Line 6
  6. Unknown attribute BGCOLOR in element TABLE. for browser(s): Lynx2.7 (5 instances)
    Line 184, Line 186, Line 200, Line 214, Line 253
  7. Required attribute TYPE is missing from tag SCRIPT for browser(s): HTML4.0 (10 instances)
    Line 12, Line 42, Line 54, Line 84, Line 94, Line 100, Line 106, Line 112, Line 118, Line 124
  8. Unknown attribute BGCOLOR in element TD. for browser(s): Lynx2.7 (1 instance)
    Line 188
  9. Unknown attribute ALIGH in element DIV. for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (1 instance)
    Line 130

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/oct01tnqc.html 13.84 K 3.85
http://thunder.nsstc.nasa.gov/images/tabs/listab_front_left.gif 0.37 K 0.10
http://thunder.nsstc.nasa.gov/images/tabs/listab_front_home.gif 0.50 K 0.14
http://thunder.nsstc.nasa.gov/images/tabs/listab_front_middle2.gif 0.39 K 0.11
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_primer.gif 0.44 K 0.12
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_middle2.gif 0.38 K 0.10
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_dataset.gif 0.64 K 0.18
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_research.gif 0.96 K 0.27
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_validation.gif 0.57 K 0.16
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_bookshelf.gif 0.58 K 0.16
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_right.gif 0.36 K 0.10
http://thunder.nsstc.nasa.gov/images/desc/desc_spacer_left.gif 0.16 K 0.04
http://thunder.nsstc.nasa.gov/images/desc/desc_spacer_middle.gif 0.18 K 0.05
http://thunder.nsstc.nasa.gov/images/desc/desc_spacer_right.gif 0.16 K 0.04
http://thunder.nsstc.nasa.gov/images/titles/titles_thunder_home_left.jpg 11.34 K 3.15
http://thunder.nsstc.nasa.gov/images/titles/titles_thunder_home_right.gif 6.59 K 1.83
http://thunder.nsstc.nasa.gov/images/fullwhite.gif 3.34 K 0.93
Total
40.80 K
11.33
HTTP Request Delays
--
8.50
Total + Delays
--
19.83