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. If this is a data table (not used for layout only), identify headers for the table rows and columns. (2 instances)
   Lines 262-263, Lines 376-377
   
3. If an image conveys important information beyond what is in its alternative text, provide an extended description. (15 instances)
   Lines 174-177, Lines 211-214, Lines 220-223, Lines 229-232, Lines 238-240, Lines 246-249, Lines 254-256, Lines 267-268, Lines 279-281, Lines 295-296, Lines 308-310, Line 321, Lines 333-335, Lines 367-369, Lines 386-387
   
4. If style sheets are ignored or unsupported, are pages still readable and usable?
   
   
5. 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.

6. Use the simplest and most straightforward language that is possible.
   
   
7. If ASCII art is present, consider substituting it with an accessible image.
   
   
8. Identify any changes in the document's language.
   
   
9. 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. 2 Priority 2 issue(s) that Bobby has identified are presented below.

1. Use relative sizing and positioning (% values) rather than absolute (pixels). (26 instances)
   Lines 169-170, Lines 203-204, Line 207, Line 216, Line 225, Line 234, Line 242, Line 251, Line 384, Line 392, Line 399, Line 406, Line 411, Line 418, Line 424, Line 429, Line 436, Line 442, Line 448, Line 455, Line 462, Line 468, Line 474, Line 481, Line 487, Line 493
   
2. Make sure event handlers do not require use of a mouse. (6 instances)
   Lines 208-211, Lines 217-220, Lines 226-229, Lines 235-238, Lines 243-246, Lines 252-254
   

User Checks

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

1. Add a descriptive title to links when needed.
   
   
2. Check that the foreground and background colors contrast sufficiently with each other.
   
   
3. If this gif image is animated, make sure it does not contain fast or distracting motion. (15 instances)
   Lines 174-177, Lines 211-214, Lines 220-223, Lines 229-232, Lines 238-240, Lines 246-249, Lines 254-256, Lines 267-268, Lines 279-281, Lines 295-296, Lines 308-310, Line 321, Lines 333-335, Lines 367-369, Lines 386-387
   
4. Mark up any quotations with the Q and BLOCKQUOTE elements.
   
   
5. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. (6 instances)
   Line 47, Line 61, Line 94, Line 101, Line 108, Line 115
   
6. Use style sheets to control layout and presentation wherever possible.
   
   

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

7. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).
   
   
8. Make sure your document validates to formal published grammars.
   
   
9. Group related elements when possible.
   
   
10. Is there a site map or table of contents, a description of the general layout of the site, the access features used, and how to use them?
    
    
11. Make sure that all link phrases make sense when read out of context.
    
    
12. Is there a clear, consistent navigation structure?
    
    
13. Use the latest technology specification available whenever possible.
    
    

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

User Checks

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

1. If there are logical groups of links, have they been identified?
   
   
2. If this is a data table (not used for layout only), provide a caption. (4 instances)
   Lines 169-170, Lines 203-204, Lines 262-263, Lines 376-377
   
3. If this document is part of a collection, provide metadata that identifies this document's location in the collection.
   
   
4. Consider adding keyboard shortcuts to frequently used links.
   
   
5. If you have grouped links, is there a link at the beginning to bypass the group?
   
   
6. Consider specifying a logical tab order among form controls, links and objects.
   
   

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

7. Are there navigation bars for easy access to the navigation structure?
   
   
8. Is there a consistent style of presentation between pages?
   
   
9. Is there distinguishing information at the beginning of headings, paragraphs, lists, etc.?
   
   
10. If ASCII art is present, provide a means to skip over it.
    
    
11. If there is a search feature, are there different types of searches for different skill levels and preferences?
    
    
12. Do you allow users to customize their experience of the web page?
    
    

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 REF in element A. for browser(s): HTML4.0 (1 instance)
   Line 338
   

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://www.scriptkitty.ws/accessibility/dwdHome.htm	20.38 K	5.66
http://www.scriptkitty.ws/accessibility/dwdHome_files/header2.gif	14.51 K	4.03
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav1_off.gif	0.68 K	0.19
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav2_off.gif	0.69 K	0.19
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav3_off.gif	0.78 K	0.22
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav4_off.gif	0.93 K	0.26
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav5_off.gif	0.79 K	0.22
http://www.scriptkitty.ws/accessibility/dwdHome_files/nav6_off.gif	0.81 K	0.23
http://www.scriptkitty.ws/accessibility/dwdHome_files/jobnet.gif	1.48 K	0.41
http://www.scriptkitty.ws/accessibility/dwdHome_files/jobcenter2.gif	1.69 K	0.47
http://www.scriptkitty.ws/accessibility/dwdHome_files/seasonal75-c.gif	2.71 K	0.75
http://www.scriptkitty.ws/accessibility/dwdHome_files/fedstar2.gif	1.11 K	0.31
http://www.scriptkitty.ws/accessibility/dwdHome_files/w-2_logo_59.gif	2.64 K	0.73
http://www.scriptkitty.ws/accessibility/dwdHome_files/dwdlogo75.gif	2.56 K	0.71
http://www.scriptkitty.ws/accessibility/dwdHome_files/wi-portal61.gif	2.97 K	0.83
http://www.scriptkitty.ws/accessibility/dwdHome_files/progrm_tab.gif	1.08 K	0.30
Total	55.82 K	15.51
HTTP Request Delays	--	8.00
Total + Delays	--	23.51