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. 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.

2. Ensure that descriptions of dynamic content are updated with changes in content.
   
   
3. Use the simplest and most straightforward language that is possible.
   
   
4. Avoid ASCII art.
   
   
5. If you can't make a page accessible, construct an alternate accessible version.
   
   

For a higher level of accessibility you may also want to examine Priority 2 items. This web page does not contain any Priority 2 accessibility errors that Bobby can detect. However, certain items require human judgment; these are listed below.

User Checks

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

1. Group related form controls and label each group. (1 instance)
   Lines 6-7
   
2. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (1 instance)
   Line 14
   

The following 8 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

3. Use a clear, consistent navigation structure.
   
   
4. Make sure your document validates to formal published grammars.
   
   
5. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).
   
   
6. Use metadata to add computer-understandable information about the page.
   
   
7. Group related elements when possible.
   
   
8. Ensure that dynamic content is accessible or provide an alternate presentation or page.
   
   
9. 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.
   
   
10. Use the latest technology specification available whenever possible.
    
    

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

1. Identify the language of the text. (1 instance)
   Line 1
   

User Checks

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

1. Consider furnishing keyboard shortcuts for form elements.
   
   

The following 9 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

2. Create a consistent style of presentation between pages.
   
   
3. Provide a link at the beginning of a group of related links to bypass the group.
   
   
4. Use icons or graphics (with accessible alternatives) to facilitate comprehension of the page.
   
   
5. Allow users to customize their experience of the web page.
   
   
6. Use the ABBR and ACRONYM elements to denote and expand abbreviations and acronyms.
   
   
7. Offer navigation bars for easy access to the navigation structure.
   
   
8. Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
   
   
9. If ASCII art is present, provide a means to skip over it.
   
   
10. Offer different types of searches for different skill levels and preferences.
    
    

The following section contains a list of 2 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 NAME in element FORM. for browser(s): Lynx2.7, HTML4.0 (1 instance)
   Lines 6-7
   
2. Required attribute TYPE is missing from tag SCRIPT for browser(s): HTML4.0 (1 instance)
   Line 14
   

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/data/trmm_val2.html	0.36 K	0.10
Total	0.36 K	0.10
HTTP Request Delays	--	0.50
Total + Delays	--	0.60