This page does not meet the requirements for Bobby Approved status. Below is a list of 1 Priority 1 accessibility errors found:

1. Provide alternative text for all images. (1 instance)
   Line 261
   

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 6 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. (3 instances)
   Line 194, Line 279, Line 175
   
3. If an image conveys important information beyond what is in its alternative text, provide an extended description. (16 instances)
   Line 160, Line 181, Line 182, Line 183, Line 184, Line 185, Line 186, Line 197, Line 207, Line 217, Line 226, Line 236, Line 246, Line 261, Line 269, Line 286
   
4. If style sheets are ignored or unsupported, are pages still readable and usable?
   
   
5. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (5 instances)
   Line 158, Line 179, Line 194, Line 279, Line 175
   
6. 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.

7. Use the simplest and most straightforward language that is possible.
   
   
8. If ASCII art is present, consider substituting it with an accessible image.
   
   
9. Identify any changes in the document's language.
   
   
10. 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. Use relative sizing and positioning (% values) rather than absolute (pixels). (86 instances)
   Line 158, Line 177, Line 179, Line 181, Line 182, Line 183, Line 184, Line 185, Line 186, Line 193, Line 194, Line 196, Line 199, Line 200, Line 206, Line 209, Line 210, Line 216, Line 219, Line 220, Line 225, Line 228, Line 229, Line 235, Line 238, Line 239, Line 240, Line 245, Line 248, Line 249, Line 250, Line 256, Line 258, Line 265, Line 267, Line 269, Line 272, Line 273, Line 278, Line 279, Line 281, Line 285, Line 290, Line 293, Line 294, Line 298, Line 299, Line 303, Line 304, Line 308, Line 309, Line 313, Line 314, Line 318, Line 319, Line 323, Line 327, Line 328, Line 332, Line 333, Line 338, Line 339, Line 343, Line 344, Line 348, Line 349, Line 354, Line 355, Line 360, Line 361, Line 365, Line 368, Line 369, Line 372
   
2. Use a public text identifier in a DOCTYPE statement.
   
   
3. Make sure event handlers do not require use of a mouse. (6 instances)
   Line 181, Line 182, Line 183, Line 184, Line 185, Line 186
   

User Checks

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

1. Avoid use of obsolete language features if possible. (39 instances)
   Line 158, Line 199, Line 200, Line 209, Line 210, Line 219, Line 220, Line 228, Line 229, Line 238, Line 239, Line 240, Line 248, Line 249, Line 250, Line 258, Line 269, Line 273, Line 286, Line 290, Line 294, Line 299, Line 304, Line 309, Line 314, Line 319, Line 323, Line 328, Line 333, Line 339, Line 344, Line 349, Line 355, Line 361, Line 365, Line 369
   
2. Add a descriptive title to links when needed.
   
   
3. Check that the foreground and background colors contrast sufficiently with each other.
   
   
4. If this gif image is animated, make sure it does not contain fast or distracting motion. (16 instances)
   Line 160, Line 181, Line 182, Line 183, Line 184, Line 185, Line 186, Line 197, Line 207, Line 217, Line 226, Line 236, Line 246, Line 261, Line 269, Line 286
   
5. Mark up any quotations with the Q and BLOCKQUOTE elements.
   
   
6. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. (6 instances)
   Line 30, Line 44, Line 77, Line 84, Line 92, Line 99
   
7. 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.

8. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).
   
   
9. Make sure your document validates to formal published grammars.
   
   
10. Group related elements when possible.
    
    
11. 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?
    
    
12. Make sure that all link phrases make sense when read out of context.
    
    
13. Is there a clear, consistent navigation structure?
    
    
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. 3 Priority 3 issue(s) that Bobby has identified are presented below.

1. Identify the language of the text. (1 instance)
   Line 1
   
2. Client-side image map contains a link not presented elsewhere on the page. (5 instances)
   Line 166, Line 165, Line 167, Line 164, Line 163
   
3. Provide a summary for tables. (5 instances)
   Line 158, Line 179, Line 194, Line 279, Line 175
   

User Checks

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

1. If there are logical groups of links, have they been identified?
   
   
2. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
   
   
3. If this is a data table (not used for layout only), provide a caption. (5 instances)
   Line 158, Line 179, Line 194, Line 279, Line 175
   
4. If this document is part of a collection, provide metadata that identifies this document's location in the collection.
   
   
5. Consider adding keyboard shortcuts to frequently used links.
   
   
6. If you have grouped links, is there a link at the beginning to bypass the group?
   
   
7. 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.

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

The following section contains a list of 3 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 BGCOLOR in element TABLE needs a valid color. for browser(s): HTML4.0 (1 instance)
   Line 179
   
2. Required attribute ALT is missing from tag IMG for browser(s): HTML4.0 (1 instance)
   Line 261
   
3. Attribute BGCOLOR in element TR needs a valid color. for browser(s): HTML4.0 (1 instance)
   Line 180
   

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.dwd.state.wi.us/	16.45 K	4.57
http://www.dwd.state.wi.us/Images/header2.gif	14.51 K	4.03
http://www.dwd.state.wi.us/images/new_default/nav1_off.gif	0.68 K	0.19
http://www.dwd.state.wi.us/images/new_default/nav2_off.gif	0.69 K	0.19
http://www.dwd.state.wi.us/images/new_default/nav3_off.gif	0.78 K	0.22
http://www.dwd.state.wi.us/images/new_default/nav4_off.gif	0.93 K	0.26
http://www.dwd.state.wi.us/images/new_default/nav5_off.gif	0.79 K	0.22
http://www.dwd.state.wi.us/images/new_default/nav6_off.gif	0.81 K	0.23
http://www.dwd.state.wi.us/images/jobnet.gif	1.48 K	0.41
http://www.dwd.state.wi.us/images/jobcenter2.gif	1.69 K	0.47
http://www.dwd.state.wi.us/images/seasonal75-c.gif	2.71 K	0.75
http://www.dwd.state.wi.us/images/fedstar2.gif	1.11 K	0.31
http://www.dwd.state.wi.us/images/w-2_logo_59.gif	2.64 K	0.73
http://www.dwd.state.wi.us/images/dwdlogo75.gif	2.56 K	0.71
http://www.dwd.state.wi.us/images/shim2.gif	0.82 K	0.23
http://www.dwd.state.wi.us/images/wi-portal61.gif	2.97 K	0.83
http://www.dwd.state.wi.us/images/progrm_tab.gif	1.08 K	0.30
Total	52.71 K	14.64
HTTP Request Delays	--	8.50
Total + Delays	--	23.14