Bobby
URL tested: http://thunder.nsstc.nasa.gov/lis/index.html, January 7, 2002 10:05:15 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 5 item(s):

  1. If an image conveys important information beyond what is its alternative text, provide an extended description. (28 instances)
    Lines 132-133, Lines 134-136, Lines 137-138, Lines 139-141, Lines 142-143, Lines 144-145, Lines 146-147, Lines 148-149, Lines 150-151, Lines 152-153, Lines 154-155, Lines 156-157, Lines 158-159, Lines 164-165, Lines 166-167, Lines 168-169, Lines 173-174, Line 231, Lines 265-267, Lines 285-287, Lines 407-409, Lines 411-413, Lines 419-421, Lines 423-425, Lines 427-429, Lines 435-437, Line 465, Line 641
  2. If you use color to convey information, make sure the information is also represented another way.

  3. For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns. (6 instances)
    Line 130, Line 311, Line 403, Line 469, Line 541, Line 618
  4. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (16 instances)
    Line 162, Line 130, Lines 189-193, Line 185, Line 317, Line 337, Line 311, Line 403, Line 475, Line 493, Line 469, Line 547, Line 567, Line 541, Line 213, Line 618
  5. 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. (42 instances)
    Line 129, Line 181, Line 197, Line 219, Line 231, Line 253, Line 265, Line 275, Line 285, Line 297, Line 321, Line 345, Line 347, Line 351, Line 353, Line 357, Line 381, Line 385, Line 395, Line 445, Line 453, Line 463, Line 465, Line 479, Line 499, Line 501, Line 515, Line 551, Line 553, Line 575, Line 579, Line 583, Line 587, Line 591, Line 617, Line 625, Line 635, Line 636
  2. Use relative sizing and positioning (% values) rather than absolute (pixels). (5 instances)
    Line 130, Line 185, Line 213, Line 403, Line 618
  3. Make sure event handlers do not require use of a mouse. (6 instances)
    Line 134, Line 139, Line 144, Line 148, Line 152, Line 156

User Checks

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

  1. Mark up quotations with the Q and BLOCKQUOTE elements.

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

  3. Use header elements in the proper sequence and not for bold text.

  4. Avoid using movement in images where possible. (22 instances)
    Lines 132-133, Lines 134-136, Lines 137-138, Lines 139-141, Lines 142-143, Lines 144-145, Lines 146-147, Lines 148-149, Lines 150-151, Lines 152-153, Lines 154-155, Lines 156-157, Lines 158-159, Lines 164-165, Lines 166-167, Lines 168-169, Lines 265-267, Lines 285-287, Lines 407-409, Lines 423-425, Line 465, Line 641
  5. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (10 instances)
    Line 21, Line 47, Line 53, Line 83, Line 93, Line 99, Line 105, Line 111, Line 117, Line 123
  6. Avoid using tables to format text documents in columns unless the table can be linearized. (16 instances)
    Line 162, Line 130, Lines 189-193, Line 185, Line 317, Line 337, Line 311, Line 403, Line 475, Line 493, Line 469, Line 547, Line 567, Line 541, Line 213, Line 618
  7. 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. (16 instances)
    Line 162, Line 130, Lines 189-193, Line 185, Line 317, Line 337, Line 311, Line 403, Line 475, Line 493, Line 469, Line 547, Line 567, Line 541, Line 213, Line 618

User Checks

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

  1. Provide abbreviations for long row or column labels. (16 instances)
    Line 162, Line 130, Lines 189-193, Line 185, Line 317, Line 337, Line 311, Line 403, Line 475, Line 493, Line 469, Line 547, Line 567, Line 541, Line 213, Line 618
  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. (16 instances)
    Line 130, Line 162, Line 185, Lines 189-193, Line 213, Line 311, Line 317, Line 337, Line 403, Line 469, Line 475, Line 493, Line 541, Line 547, Line 567, Line 618

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 14 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 15
  2. Unknown attribute VSPACE in element IMG. for browser(s): Lynx2.7 (3 instances)
    Line 231, Lines 265-267, Lines 285-287
  3. Unknown attribute BORDERCOLOR in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Lines 189-193
  4. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (4 instances)
    Line 321, Line 479, Line 551, Line 635
  5. Unknown attribute NAME in element IMG. for browser(s): Lynx2.7 (1 instance)
    Lines 166-167
  6. Attribute NOSHADE in element HR is assigned an incorrect value. for browser(s): Lynx2.7 (3 instances)
    Line 379, Line 621, Line 631
  7. Unknown attribute BGCOLOR in element TABLE. for browser(s): Lynx2.7 (8 instances)
    Line 185, Lines 189-193, Line 311, Line 337, Line 469, Line 493, Line 541, Line 567
  8. Required attribute TYPE is missing from tag SCRIPT for browser(s): HTML4.0 (10 instances)
    Line 21, Line 47, Line 53, Line 83, Line 93, Line 99, Line 105, Line 111, Line 117, Line 123
  9. Unknown attribute BORDERCOLORLIGHT in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Lines 189-193
  10. Unknown attribute BORDERCOLORDARK in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (1 instance)
    Lines 189-193
  11. Unknown attribute COLS in element TABLE. for browser(s): HTML4.0 (1 instance)
    Lines 189-193
  12. Unknown attribute HSPACE in element IMG. for browser(s): Lynx2.7 (3 instances)
    Line 231, Lines 265-267, Lines 285-287
  13. Unknown attribute BGCOLOR in element TD. for browser(s): Lynx2.7 (1 instance)
    Line 197
  14. Unknown attribute ALIGH in element DIV. for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (2 instances)
    Line 129, Line 181

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/lis/index.html 21.36 K 5.93
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_left.gif 0.36 K 0.10
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_home.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_primer.gif 0.44 K 0.12
http://thunder.nsstc.nasa.gov/images/tabs/listab_back_dataset.gif 0.64 K 0.18
http://thunder.nsstc.nasa.gov/images/tabs/listab_front_middle1.gif 0.38 K 0.11
http://thunder.nsstc.nasa.gov/images/tabs/listab_front_research.gif 1.12 K 0.31
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_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_lis.jpg 9.56 K 2.66
http://thunder.nsstc.nasa.gov/lis/images/lis_sensor.jpg 6.13 K 1.70
http://thunder.nsstc.nasa.gov/lis/images/trmm_earth_sm2.gif 18.66 K 5.18
http://thunder.nsstc.nasa.gov/lis/images/trmm_teardrop.gif 4.49 K 1.25
http://thunder.nsstc.nasa.gov/lis/images/first_storms_left.gif 6.08 K 1.69
http://thunder.nsstc.nasa.gov/lis/images/first_storms_top.jpg 5.10 K 1.42
http://thunder.nsstc.nasa.gov/lis/images/first_storms_cloud_left.jpg 3.35 K 0.93
http://thunder.nsstc.nasa.gov/lis/images/first_storms_anim.gif 7.38 K 2.05
http://thunder.nsstc.nasa.gov/lis/images/first_storms_cloud_right.jpg 1.41 K 0.39
http://thunder.nsstc.nasa.gov/lis/images/first_storms_bottom.jpg 7.94 K 2.21
http://thunder.nsstc.nasa.gov/lis/images/lis_season_djf98.gif 76.59 K 21.28
http://thunder.nsstc.nasa.gov/images/fullwhite.gif 3.34 K 0.93
Total
177.56 K
49.32
HTTP Request Delays
--
13.50
Total + Delays
--
62.82