Priority 1 User Checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby A Approval requires that none of them apply to your page. Please review these 3 item(s):

1. If style sheets are ignored or unsupported, are pages still readable and usable?
   
   
2. Provide alternative content for each SCRIPT that conveys important information or functionality.
   
   
3. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (1 instance)
   Line 195
   

The following 3 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby A Approved status.

4. Identify any changes in the document's language.
   
   
5. If you can't make a page accessible, construct an alternate accessible version.
   
   
6. Use the simplest and most straightforward language that is possible.
   
   

This page does not meet the requirements for Bobby AA Approved status. Below is a list of 1 Priority 2 accessibility error(s) found:

1. Use a public text identifier in a DOCTYPE statement. (1 instance)
   Line 1
   

Priority 2 User Checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby AA Approval requires that none of them apply to your page. Please review these 5 item(s):

1. Use style sheets to control layout and presentation wherever possible.
   
   
2. Avoid use of obsolete language features if possible. (1 instance)
   Line 194
   
3. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. (6 instances)
   Lines 9, 97, 113, 115, 117, 119
   
4. Make sure header elements are not used only for bold text.
   
   
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 and are required for Bobby AA Approved status.

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

This page does not meet the requirements for Bobby AAA Approved status. Below is a list of 2 Priority 3 accessibility error(s) found:

1. Provide a summary for tables. (1 instance)
   Line 195
   
2. Identify the language of the text. (1 instance)
   Line 2
   

Priority 3 User Checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby AAA 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), provide a caption. (1 instance)
   Line 195
   
2. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
   
   
3. Where appropriate, use icons or graphics (with accessible alternatives) to facilitate comprehension of the page.
   
   
4. Consider adding keyboard shortcuts to frequently used links.
   
   

The following 5 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AAA Approved status.

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