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 an image conveys important information beyond what is its alternative text, provide an extended description. (3 instances)
   Line 63, Line 88, Line 120
   
2. If you use color to convey information, make sure the information is also represented another way.
   
   
3. Be sure pages are readable and usable if style sheets are ignored.
   
   
4. 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.

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

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

1. Separate adjacent links with more than whitespace. (13 instances)
   Line 61, Line 83, Line 90, Line 92, Line 93, Line 94, Line 95, Line 96, Line 99, Line 101, Line 108, Line 124
   
2. Use relative sizing and positioning (% values) rather than absolute (pixels). (24 instances)
   Line 57, Line 67, Line 68, Line 70, Line 74, Line 76, Line 79, Line 80, Line 83, Line 89, Line 90, Line 92, Line 94, Line 96, Line 99, Line 101, Line 105, Line 108, Line 111, Line 114, Line 115, Line 117, Line 120, Line 122
   
3. Avoid use of deprecated language features if possible. (37 instances)
   Line 56, Line 57, Line 67, Line 68, Line 69, Line 70, Line 72, Line 73, Line 74, Line 75, Line 76, Line 78, Line 79, Line 80, Line 81, Line 83, Line 89, Line 90, Line 92, Line 94, Line 96, Line 99, Line 101, Line 103, Line 105, Line 108, Line 111, Line 114, Line 115, Line 117, Line 120, Line 122
   

User Checks

6 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. Use header elements in the proper sequence and not for bold text.
   
   
5. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (1 instance)
   Line 7
   
6. 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.

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

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

1. Consider adding keyboard shortcuts to frequently used links.
   
   
2. Group related links.
   
   
3. Specify a logical tab order among form controls, links and objects.
   
   

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

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

The following section contains a list of 5 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 6
   
2. Required attribute TYPE is missing from tag SCRIPT for browser(s): HTML4.0 (1 instance)
   Line 7
   
3. Unknown element name DOCUMENT.MM_TIME.LENGTH; for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (1 instance)
   Lines 34-40
   
4. Unknown attribute TYPE in element STYLE. for browser(s): Lynx2.7 (1 instance)
   Line 42
   
5. Attribute SIZE in element FONT must be assigned an integer. for browser(s): Explorer4.01 (1 instance)
   Line 56
   

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://aces.nsstc.nasa.gov/partners.html	9.49 K	2.64
http://aces.nsstc.nasa.gov/images/side_nav1.jpg	5.85 K	1.62
http://aces.nsstc.nasa.gov/images/uav_flyingimage.jpg	5.42 K	1.51
http://aces.nsstc.nasa.gov/images/nasa_logo.jpg	3.74 K	1.04
Total	24.51 K	6.81
HTTP Request Delays	--	2.00
Total + Delays	--	8.81