Bobby
URL tested: http://thunder.nsstc.nasa.gov/bookshelf/pubs/sprites.html, January 7, 2002 9:56:01 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 1 item(s):

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

  1. Use relative sizing and positioning (% values) rather than absolute (pixels). (102 instances)
    Line 9, Line 13, Line 15, Line 17, Line 20, Line 23, Line 25, Line 28, Line 30, Line 33, Line 74, Line 76, Line 89, Line 106, Line 109, Line 127, Line 150, Line 153, Line 181, Line 184, Line 212, Line 248, Line 262, Line 279, Line 295, Line 318, Line 319, Line 325, Line 334, Line 340, Line 342, Line 353, Line 372, Line 398, Line 416, Line 430, Line 433, Line 449, Line 455, Line 457, Line 481, Line 483, Line 496, Line 498, Line 520, Line 526, Line 528, Line 540, Line 542, Line 555, Line 570, Line 581, Line 588, Line 590, Line 593, Line 597, Line 600, Line 604, Line 609, Line 616, Line 621, Line 626, Line 629, Line 634, Line 639, Line 642, Line 646, Line 650, Line 655, Line 659, Line 664, Line 668, Line 672, Line 675, Line 679, Line 682, Line 685, Line 689, Line 693, Line 697, Line 702, Line 707, Line 712, Line 715, Line 719, Line 724, Line 728, Line 732, Line 737, Line 742, Line 745, Line 749, Line 752, Line 756, Line 760, Line 765, Line 770, Line 775
  2. Avoid use of deprecated language features if possible. (102 instances)
    Line 9, Line 13, Line 15, Line 17, Line 20, Line 23, Line 25, Line 28, Line 30, Line 33, Line 74, Line 76, Line 89, Line 106, Line 109, Line 127, Line 150, Line 153, Line 181, Line 184, Line 212, Line 248, Line 262, Line 279, Line 295, Line 318, Line 319, Line 325, Line 334, Line 340, Line 342, Line 353, Line 372, Line 398, Line 416, Line 430, Line 433, Line 449, Line 455, Line 457, Line 481, Line 483, Line 496, Line 498, Line 520, Line 526, Line 528, Line 540, Line 542, Line 555, Line 570, Line 581, Line 588, Line 590, Line 593, Line 597, Line 600, Line 604, Line 609, Line 616, Line 621, Line 626, Line 629, Line 634, Line 639, Line 642, Line 646, Line 650, Line 655, Line 659, Line 664, Line 668, Line 672, Line 675, Line 679, Line 682, Line 685, Line 689, Line 693, Line 697, Line 702, Line 707, Line 712, Line 715, Line 719, Line 724, Line 728, Line 732, Line 737, Line 742, Line 745, Line 749, Line 752, Line 756, Line 760, Line 765, Line 770, Line 775

User Checks

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

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

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

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

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.



Browser Compatibility Errors

The following section contains a list of 1 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 HTTP-EQUIV in element META. for browser(s): Lynx2.7 (1 instance)
    Line 3

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/bookshelf/pubs/sprites.html 42.92 K 11.92
Total
42.92 K
11.92
HTTP Request Delays
--
0.50
Total + Delays
--
12.42