Sample HTML Form Using JavaScript

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 2 item(s):

1. Be sure pages are readable and usable if style sheets are ignored.
   
   
2. If you use color to convey information, make sure the information is also represented another way.
   
   

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 Approved status.

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

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. Explicitly associate form controls and their labels with the LABEL element. (9 instances)
   Line 57, Line 61, Line 65, Line 69, Line 73, Line 77, Line 81, Line 85, Line 89
   

User Checks

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

1. Avoid use of deprecated language features if possible. (1 instance)
   Line 94
   
2. If a table is used for layout only, do not use structural markup to achieve formatting effects. (1 instance)
   Line 43
   
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. Ensure that labels of all form controls are placed immediately before the control. (18 instances)
   Line 56, Line 57, Line 60, Line 61, Line 64, Line 65, Line 68, Line 69, Line 72, Line 73, Line 76, Line 77, Line 80, Line 81, Line 84, Line 85, Line 88, Line 89
   
6. Group related form controls and label each group. (1 instance)
   Line 44
   
7. If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening. (1 instance)
   Line 98
   
8. 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.

9. Use a clear, consistent navigation structure.
   
   
10. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).
    
    
11. Make sure your document validates to formal published grammars.
    
    
12. Use metadata to add computer-understandable information about the page.
    
    
13. Group related elements when possible.
    
    
14. Ensure that dynamic content is accessible or provide an alternate presentation or page.
    
    
15. 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.
    
    
16. 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. Include default, place-holding characters in edit boxes and text areas. (9 instances)
   Line 57, Line 61, Line 65, Line 69, Line 73, Line 77, Line 81, Line 85, Line 89
   

User Checks

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

1. Provide abbreviations for long row or column labels. (1 instance)
   Line 43
   
2. Consider furnishing keyboard shortcuts for form elements.
   
   
3. Specify a logical tab order among form controls, links and objects.
   
   
4. Provide a linear text alternative for tables that lay out content in parallel, word-wrapped columns. (1 instance)
   Line 43
   

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

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

1. Unknown attribute NAME in element FORM. for browser(s): HTML4.0 (1 instance)
   Line 44
   
2. Required attribute ACTION is missing from tag FORM for browser(s): HTML4.0 (1 instance)
   Line 44