Bobby
URL tested: http://thunder.nsstc.nasa.gov/LISbrowse/oct99.html, January 7, 2002 10:06:39 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 page does not meet the requirements for Bobby Approved status. Below is a list of 1 Priority 1 accessibility errors found:

  1. Provide alternative text for all images. (31 instances)
    Lines 59-60, Lines 65-66, Lines 74-75, Lines 80-81, Lines 86-87, Lines 92-93, Lines 98-99, Lines 104-105, Lines 110-111, Lines 119-120, Lines 125-126, Lines 131-132, Lines 137-138, Lines 143-144, Lines 149-150, Lines 155-156, Lines 164-165, Lines 170-171, Lines 176-177, Lines 182-183, Lines 188-189, Lines 194-195, Lines 200-201, Lines 209-210, Lines 215-216, Lines 221-222, Lines 227-228, Lines 233-234, Lines 239-240, Lines 245-246, Lines 254-255

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 3 item(s):

  1. If you use color to convey information, make sure the information is also represented another way.

  2. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (3 instances)
    Lines 14-16, Line 12, Line 28
  3. If an image conveys important information beyond what is its alternative text, provide an extended description. (31 instances)
    Lines 59-60, Lines 65-66, Lines 74-75, Lines 80-81, Lines 86-87, Lines 92-93, Lines 98-99, Lines 104-105, Lines 110-111, Lines 119-120, Lines 125-126, Lines 131-132, Lines 137-138, Lines 143-144, Lines 149-150, Lines 155-156, Lines 164-165, Lines 170-171, Lines 176-177, Lines 182-183, Lines 188-189, Lines 194-195, Lines 200-201, Lines 209-210, Lines 215-216, Lines 221-222, Lines 227-228, Lines 233-234, Lines 239-240, Lines 245-246, Lines 254-255

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.

Not Bobby ApprovedThis page does not yet meet the requirements for Bobby Approved status.


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. 2 Priority 2 issue(s) that Bobby has identified are presented below.

  1. Use relative sizing and positioning (% values) rather than absolute (pixels). (151 instances)
    Line 12, Line 31, Line 33, Line 34, Line 37, Line 52, Line 53, Line 54, Line 55, Line 56, Line 57, Line 60, Line 61, Line 63, Line 66, Line 67, Line 72, Line 75, Line 76, Line 78, Line 81, Line 82, Line 84, Line 87, Line 88, Line 90, Line 93, Line 94, Line 96, Line 99, Line 100, Line 102, Line 105, Line 106, Line 108, Line 111, Line 112, Line 117, Line 120, Line 121, Line 123, Line 126, Line 127, Line 129, Line 132, Line 133, Line 135, Line 138, Line 139, Line 141, Line 144, Line 145, Line 147, Line 150, Line 151, Line 153, Line 156, Line 157, Line 162, Line 165, Line 166, Line 168, Line 171, Line 172, Line 174, Line 177, Line 178, Line 180, Line 183, Line 184, Line 186, Line 189, Line 190, Line 192, Line 195, Line 196, Line 198, Line 201, Line 202, Line 207, Line 210, Line 211, Line 213, Line 216, Line 217, Line 219, Line 222, Line 223, Line 225, Line 228, Line 229, Line 231, Line 234, Line 235, Line 237, Line 240, Line 241, Line 243, Line 246, Line 247, Line 252, Line 255, Line 256, Line 258, Line 259, Line 260, Line 261, Line 262, Line 263
  2. Avoid use of deprecated language features if possible. (68 instances)
    Line 10, Line 27, Line 31, Line 34, Line 37, Line 60, Line 61, Line 66, Line 67, Line 75, Line 76, Line 81, Line 82, Line 87, Line 88, Line 93, Line 94, Line 99, Line 100, Line 105, Line 106, Line 111, Line 112, Line 120, Line 121, Line 126, Line 127, Line 132, Line 133, Line 138, Line 139, Line 144, Line 145, Line 150, Line 151, Line 156, Line 157, Line 165, Line 166, Line 171, Line 172, Line 177, Line 178, Line 183, Line 184, Line 189, Line 190, Line 195, Line 196, Line 201, Line 202, Line 210, Line 211, Line 216, Line 217, Line 222, Line 223, Line 228, Line 229, Line 234, Line 235, Line 240, Line 241, Line 246, Line 247, Line 255, Line 256, Line 270

User Checks

4 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 28
  2. Check that the foreground and background colors contrast sufficiently with each other.

  3. Avoid using tables to format text documents in columns unless the table can be linearized. (2 instances)
    Lines 14-16, Line 12
  4. 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. (3 instances)
    Lines 14-16, Line 12, Line 28

User Checks

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

  1. Provide abbreviations for long row or column labels. (3 instances)
    Lines 14-16, Line 12, Line 28
  2. Specify a logical tab order among form controls, links and objects.

  3. Consider adding keyboard shortcuts to frequently used links.

  4. Group related links.

  5. Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns. (3 instances)
    Line 12, Lines 14-16, Line 28

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 12 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 HEIGHT in element TD. for browser(s): Lynx2.7 (42 instances)
    Line 52, Line 53, Line 54, Line 55, Line 56, Line 57, Line 63, Line 72, Line 78, Line 84, Line 90, Line 96, Line 102, Line 108, Line 117, Line 123, Line 129, Line 135, Line 141, Line 147, Line 153, Line 162, Line 168, Line 174, Line 180, Line 186, Line 192, Line 198, Line 207, Line 213, Line 219, Line 225, Line 231, Line 237, Line 243, Line 252, Line 258, Line 259, Line 260, Line 261, Line 262, Line 263
  2. Unknown attribute ALIGH in element DIV. for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (1 instance)
    Line 10
  3. Unknown attribute BORDERCOLOR in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (2 instances)
    Lines 14-16, Line 28
  4. Attribute ALINK in element BODY needs a valid color. for browser(s): Explorer4.01, Navigator4.0 (1 instance)
    Line 8
  5. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (45 instances)
    Line 18, Line 19, Line 20, Line 52, Line 53, Line 54, Line 55, Line 56, Line 57, Line 63, Line 72, Line 78, Line 84, Line 90, Line 96, Line 102, Line 108, Line 117, Line 123, Line 129, Line 135, Line 141, Line 147, Line 153, Line 162, Line 168, Line 174, Line 180, Line 186, Line 192, Line 198, Line 207, Line 213, Line 219, Line 225, Line 231, Line 237, Line 243, Line 252, Line 258, Line 259, Line 260, Line 261, Line 262, Line 263
  6. Unknown attribute BGCOLOR in element TABLE. for browser(s): Lynx2.7 (2 instances)
    Line 12, Lines 14-16
  7. Unknown attribute BORDERCOLORLIGHT in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (2 instances)
    Lines 14-16, Line 28
  8. Unknown attribute BORDERCOLORDARK in element TABLE. for browser(s): Lynx2.7, Navigator4.0, HTML4.0 (2 instances)
    Lines 14-16, Line 28
  9. Unknown attribute HEIGHT in element TH. for browser(s): Lynx2.7, Explorer4.01 (1 instance)
    Line 33
  10. Unknown attribute COLS in element TABLE. for browser(s): HTML4.0 (1 instance)
    Lines 14-16
  11. Unknown attribute BGCOLOR in element TD. for browser(s): Lynx2.7 (3 instances)
    Line 18, Line 19, Line 20
  12. Required attribute ALT is missing from tag IMG for browser(s): HTML4.0 (31 instances)
    Lines 59-60, Lines 65-66, Lines 74-75, Lines 80-81, Lines 86-87, Lines 92-93, Lines 98-99, Lines 104-105, Lines 110-111, Lines 119-120, Lines 125-126, Lines 131-132, Lines 137-138, Lines 143-144, Lines 149-150, Lines 155-156, Lines 164-165, Lines 170-171, Lines 176-177, Lines 182-183, Lines 188-189, Lines 194-195, Lines 200-201, Lines 209-210, Lines 215-216, Lines 221-222, Lines 227-228, Lines 233-234, Lines 239-240, Lines 245-246, Lines 254-255

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/oct99.html 9.53 K 2.65
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.274_T.jpg 6.00 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.275_T.jpg 6.06 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.276_T.jpg 6.00 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.277_T.jpg 5.99 K 1.66
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.278_T.jpg 6.03 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.279_T.jpg 6.06 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.280_T.jpg 5.96 K 1.66
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.281_T.jpg 6.00 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.282_T.jpg 6.04 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.283_T.jpg 6.03 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.284_T.jpg 6.07 K 1.69
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.285_T.jpg 6.05 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.286_T.jpg 6.06 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.287_T.jpg 6.06 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.288_T.jpg 6.04 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.289_T.jpg 6.05 K 1.68
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.290_T.jpg 6.01 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.291_T.jpg 6.02 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.292_T.jpg 6.00 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.293_T.jpg 5.93 K 1.65
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.294_T.jpg 5.97 K 1.66
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.295_T.jpg 6.01 K 1.67
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.296_T.jpg 5.97 K 1.66
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.297_T.jpg 5.93 K 1.65
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.298_T.jpg 5.90 K 1.64
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.299_T.jpg 5.88 K 1.63
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.300_T.jpg 5.89 K 1.64
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.301_T.jpg 5.94 K 1.65
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.302_T.jpg 5.91 K 1.64
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.303_T.jpg 5.90 K 1.64
http://thunder.nsstc.nasa.gov/LISbrowse/1999/jpg/TRMM_LIS_BR.04.0_1999.304_T.jpg 5.89 K 1.64
Total
195.17 K
54.21
HTTP Request Delays
--
16.00
Total + Delays
--
70.21