Bobby
URL tested: http://thunder.nsstc.nasa.gov/validation/validation.html, January 7, 2002 10:13:38 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 4 item(s):

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

  2. For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns. (1 instance)
    Line 239
  3. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (4 instances)
    Lines 13-15, Line 11, Line 239, Line 25
  4. If an image conveys important information beyond what is its alternative text, provide an extended description. (7 instances)
    Line 258, Line 289, Line 319, Line 348, Line 375, Line 403, Line 426

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

  1. Separate adjacent links with more than whitespace. (1 instance)
    Line 316
  2. Use relative sizing and positioning (% values) rather than absolute (pixels). (2 instances)
    Line 11, Line 25
  3. Make sure that headings are nested properly. (2 instances)
    Line 216, Line 433
  4. Avoid use of deprecated language features if possible. (122 instances)
    Line 10, Line 24, Line 27, Line 33, Line 46, Line 49, Line 51, Line 53, Line 57, Line 58, Line 59, Line 61, Line 62, Line 63, Line 64, Line 66, Line 68, Line 69, Line 70, Line 71, Line 73, Line 77, Line 78, Line 80, Line 90, Line 91, Line 93, Line 106, Line 107, Line 109, Line 119, Line 120, Line 122, Line 132, Line 133, Line 135, Line 145, Line 146, Line 148, Line 160, Line 161, Line 163, Line 174, Line 175, Line 177, Line 184, Line 185, Line 188, Line 199, Line 200, Line 203, Line 215, Line 216, Line 218, Line 220, Line 222, Line 224, Line 226, Line 228, Line 230, Line 232, Line 241, Line 243, Line 249, Line 258, Line 267, Line 269, Line 275, Line 286, Line 289, Line 298, Line 300, Line 306, Line 314, Line 319, Line 328, Line 330, Line 336, Line 348, Line 357, Line 359, Line 365, Line 375, Line 384, Line 386, Line 392, Line 403, Line 412, Line 414, Line 419, Line 426, Line 433, Line 435, Line 440, Line 443, Line 445, Line 449, Line 450, Line 454, Line 456, Line 457, Line 458, Line 459, Line 461, Line 462, Line 473, Line 488, Line 489, Line 492, Line 494, Line 495, Line 496, Line 499, Line 500, Line 520, Line 536, Line 537, Line 540, Line 542, Line 544, Line 546

User Checks

6 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. (6 instances)
    Line 258, Line 289, Line 319, Line 375, Line 403, Line 426
  5. Avoid using tables to format text documents in columns unless the table can be linearized. (4 instances)
    Lines 13-15, Line 11, Line 239, Line 25
  6. 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. (4 instances)
    Lines 13-15, Line 11, Line 239, Line 25

User Checks

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

  1. Provide abbreviations for long row or column labels. (4 instances)
    Lines 13-15, Line 11, Line 239, Line 25
  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. (4 instances)
    Line 11, Lines 13-15, Line 25, Line 239

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.




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/validation/validation.html 36.12 K 10.03
http://thunder.nsstc.nasa.gov/validation/images/aldf_sm.gif 22.47 K 6.24
http://thunder.nsstc.nasa.gov/validation/images/ksc_ldar_sm.gif 18.38 K 5.10
http://thunder.nsstc.nasa.gov/validation/images/ksc_fm_sm.gif 26.67 K 7.41
http://thunder.nsstc.nasa.gov/validation/images/airborne_mill_sm.jpg 8.01 K 2.23
http://thunder.nsstc.nasa.gov/validation/images/cond_probe_sm.gif 22.95 K 6.37
http://thunder.nsstc.nasa.gov/validation/images/ops_sensor_sm.gif 11.33 K 3.15
http://thunder.nsstc.nasa.gov/validation/images/spectrometer_sm.gif 25.28 K 7.02
Total
171.20 K
47.56
HTTP Request Delays
--
4.00
Total + Delays
--
51.56