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 this is a data table (not used for layout only), identify headers for the table rows and columns. (2 instances)
   Line 8, Line 20
   
2. If an image conveys important information beyond what is in its alternative text, provide an extended description. (8 instances)
   Line 10, Line 13, Line 14, Line 15, Line 16, Line 17, Line 22, Line 32
   
3. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (2 instances)
   Line 8, Line 20
   
4. If you use color to convey information, make sure the information is also represented another way.
   
   

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

1. Use a public text identifier in a DOCTYPE statement.
   
   

User Checks

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

1. Check that the foreground and background colors contrast sufficiently with each other.
   
   
2. If this gif image is animated, make sure it does not contain fast or distracting motion. (6 instances)
   Line 10, Line 13, Line 14, Line 15, Line 16, Line 17
   
3. As appropriate, use metadata to add computer-understandable information about the page.
   
   
4. Mark up any quotations with the Q and BLOCKQUOTE elements.
   
   
5. Add a descriptive title to links when needed.
   
   

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

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

User Checks

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

1. If this is a data table (not used for layout only), provide a caption. (2 instances)
   Line 8, Line 20
   
2. Consider adding keyboard shortcuts to frequently used links.
   
   
3. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
   
   

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

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

No browser compatibility errors found.

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://vision.unco.edu/edtech/primer/tutorial/HearSample/good.html	2.86 K	0.80
http://vision.unco.edu/edtech/primer/tutorial/HearSample/BlueSuitTitle.gif	1.06 K	0.29
http://vision.unco.edu/edtech/primer/tutorial/HearSample/HomeBtn.gif	0.77 K	0.22
http://vision.unco.edu/edtech/primer/tutorial/HearSample/AboutBtn.gif	0.84 K	0.23
http://vision.unco.edu/edtech/primer/tutorial/HearSample/SamplesBtn.gif	0.84 K	0.23
http://vision.unco.edu/edtech/primer/tutorial/HearSample/ClientsBtn.gif	0.81 K	0.22
http://vision.unco.edu/edtech/primer/tutorial/HearSample/ContactBtn.gif	0.81 K	0.22
http://vision.unco.edu/edtech/primer/tutorial/HearSample/BlueSuitPic.jpg	4.84 K	1.35
http://vision.unco.edu/edtech/primer/tutorial/HearSample/SamplePic.jpg	3.63 K	1.01
Total	16.48 K	4.58
HTTP Request Delays	--	4.50
Total + Delays	--	9.08