Bobby
URL tested: http://thunder.nsstc.nasa.gov/nldn/nldn-0202.html, January 7, 2002 10:10:19 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 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 137
  3. Be sure pages are readable and usable if style sheets are ignored.

  4. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (7 instances)
    Line 118, Line 145, Line 167, Line 253, Line 311, Line 339, Line 137
  5. If an image conveys important information beyond what is its alternative text, provide an extended description. (1 instance)
    Line 121

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

  1. Make sure event handlers do not require use of a mouse. (1 instance)
    Line 373
  2. Avoid use of deprecated language features if possible. (22 instances)
    Line 124, Line 139, Line 140, Line 150, Line 155, Line 163, Line 164, Line 247, Line 248, Line 269, Line 296, Line 306, Line 307, Line 316, Line 325, Line 334, Line 335, Line 344, Line 353, Line 362, Line 377, Line 386
  3. Use relative sizing and positioning (% values) rather than absolute (pixels). (16 instances)
    Line 140, Line 150, Line 155, Line 164, Line 248, Line 269, Line 296, Line 307, Line 316, Line 325, Line 335, Line 344, Line 353, Line 362, Line 377, Line 386
  4. Group long lists of selections into a hierarchy. (3 instances)
    Line 171, Line 190, Line 207
  5. Explicitly associate form controls and their labels with the LABEL element. (16 instances)
    Line 149, Line 154, Line 171, Line 190, Line 207, Line 257, Line 258, Line 273, Line 274, Line 284, Line 285, Line 315, Line 324, Line 343, Line 352, Line 361

User Checks

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

  1. Add a descriptive title to links when needed.

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

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

  4. Ensure that labels of all form controls are placed immediately before the control. (17 instances)
    Line 149, Line 154, Line 171, Line 190, Line 207, Line 257, Line 258, Line 273, Line 274, Line 284, Line 285, Line 315, Line 324, Line 343, Line 352, Line 361, Line 373
  5. Group related form controls and label each group. (1 instance)
    Line 135
  6. Avoid using tables to format text documents in columns unless the table can be linearized. (7 instances)
    Line 118, Line 145, Line 167, Line 253, Line 311, Line 339, Line 137
  7. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (1 instance)
    Line 11
  8. 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. (7 instances)
    Line 118, Line 145, Line 167, Line 253, Line 311, Line 339, Line 137

User Checks

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

  1. Provide abbreviations for long row or column labels. (7 instances)
    Line 118, Line 145, Line 167, Line 253, Line 311, Line 339, Line 137
  2. Consider furnishing keyboard shortcuts for form elements.

  3. Specify a logical tab order among form controls, links and objects.

  4. Consider adding keyboard shortcuts to frequently used links.

  5. Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns. (7 instances)
    Line 118, Line 137, Line 145, Line 167, Line 253, Line 311, Line 339

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. Attribute ALINK in element BODY needs a valid color. for browser(s): Explorer4.01, Navigator4.0 (1 instance)
    Lines 116-117
  2. Attribute COLOR in element FONT needs a valid color. for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (6 instances)
    Line 124, Line 139, Line 163, Line 247, Line 306, Line 334
  3. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (1 instance)
    Line 139
  4. Attribute NOSHADE in element HR is assigned an incorrect value. for browser(s): Lynx2.7 (1 instance)
    Line 385
  5. Unknown element name NOSCRIPT for browser(s): Lynx2.7 (2 instances)
    Line 293, Line 299
  6. Attribute SIZE in element FONT must be assigned an integer. for browser(s): Explorer4.01 (1 instance)
    Line 124
  7. Unknown attribute TYPE in element STYLE. for browser(s): Lynx2.7 (1 instance)
    Line 5
  8. Attribute LINK in element BODY needs a valid color. for browser(s): Explorer4.01, Navigator4.0 (1 instance)
    Lines 116-117
  9. Required attribute TYPE is missing from tag SCRIPT for browser(s): HTML4.0 (1 instance)
    Line 11
  10. Attribute SELECTED in element OPTION is assigned an incorrect value. for browser(s): Lynx2.7 (6 instances)
    Line 172, Line 191, Line 208, Line 259, Line 275, Line 286
  11. Unknown attribute BGCOLOR in element TD. for browser(s): Lynx2.7 (6 instances)
    Line 144, Line 152, Line 166, Line 252, Line 310, Line 338
  12. Unknown attribute NAME in element FORM. for browser(s): Lynx2.7, HTML4.0 (1 instance)
    Line 135

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/nldn/nldn-0202.html 10.42 K 2.89
http://thunder.nsstc.nasa.gov/nldn/lightning1.jpg 3.94 K 1.10
Total
14.36 K
3.99
HTTP Request Delays
--
1.00
Total + Delays
--
4.99