Show Advanced / Accessibility Options Terms of use

Results for View in new window

Page last checked on Thu 28/12/2006 at 5:50pm.

  General Quality



Expand All|Collapse All

ErrorThis page does not comply with all of the automatic and manual checkpoints of the W3C Web Content Accessibility Guidelines, and requires repairs and manual verification.

Automatic CheckpointsManual Checkpoints
Priority 1Acceptable00Warning1120
Priority 2Error337Warning2032
Priority 3Error316Warning1010

11 tests, 20 instances on page
GuidelineInstancesLine Numbers
1.1If the submit button is used as an image map, use separate buttons for each active region.1112
1.1If an image conveys important information beyond what is in its alternative text, provide an extended description. 343, 95, 99
2.1If you use color to convey information, make sure the information is also represented another way. 343, 95, 99
4.1 Identify any changes in the document's language.   
5.2If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. 249, 433
6.1If style sheets are ignored or unsupported, ensure that pages are still readable and usable.   
6.3 Provide alternative content for each SCRIPT that conveys information or functionality.   
6.3 Make sure pages are still usable if programmatic objects do not function.327, 29, 31
7.1 Make sure that the page does not cause the screen to flicker rapidly.   
8.1 Provide accessible alternatives to the information in scripts, applets, or objects.327, 29, 31
14.1 Use the simplest and most straightforward language that is possible.  

3 tests, 37 instances on page
GuidelineInstancesLine Numbers
9.3 Make sure event handlers do not require use of a mouse. 439, 60, 95, 99
12.4Explicitly associate form controls and their labels with the LABEL element.1114
13.1 Do not use the same link phrase more than once when the links point to different URLs.3286, 90, 166, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 218, 246, 249, 259, 358, 364, 398, 404, 420
20 tests, 32 instances on page
GuidelineInstancesLine Numbers
2.2 Check that the foreground and background colors contrast sufficiently with each other. 343, 95, 99
3.1Where it's possible to mark up content instead of using images, use a markup language.   
3.2 Make sure your document validates to formal published grammars.   
3.5 Make sure header elements are not used only for bold text.   
3.7 Mark up any quotations with the Q and BLOCKQUOTE elements.   
5.3 Avoid using tables to format text documents in columns unless the table can be linearized.  
5.5If this is a data table (not used for layout only), provide a caption. 249, 433
6.4If objects use event handlers, make sure they do not require use of a mouse.   
7.2If this .gif image is animated, make sure it does not contain fast or distracting motion. 443, 95, 99, 112
9.2 Make sure that all elements that have their own interface are operable without a mouse. 327, 29, 31
10.1 Inform the user that clicking on certain links or areas of a window will open pop-up windows or change the active window.2270, 275
10.1If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. 327, 29, 31
10.2 Make sure that labels of all form controls are properly placed.   
11.1 Use the latest technology specification available whenever possible.  
11.2 Avoid use of obsolete language features if possible.259, 110
12.3If there are logical groupings of form controls, use FIELDSET with LEGEND on each group. 1109
12.3 Group related elements when possible.  
13.1 Make sure that all link phrases make sense when read out of context.  
13.3 Provide the user with a site map or table of contents , a description of the general layout of the site, the access features used, and instructions on how to use them.  
13.4 Provide a clear, consistent navigation structure.   

3 tests, 16 instances on page
GuidelineInstancesLine Numbers
5.5 Provide a summary for tables. 241, 149
10.4 Include default, place-holding characters in edit boxes and text areas.1111
10.5 Separate adjacent links with more than whitespace. 1351, 52, 53, 55, 56, 57, 98, 127, 129, 131, 139, 142, 145
10 tests, 10 instances on page
GuidelineInstancesLine Numbers
4.2 Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.  
9.4Consider specifying a logical tab order among form controls, links, and objects.  
11.3 Allow users to customize their experience of the web page.  
13.5 Provide navigation bars for easy access to the navigation structure.  
13.6If there are logical groups of links, make sure they are clearly identified.   
13.6If you have grouped links, make sure there is a link at the beginning that allows the user to bypass the group.  
13.7If there is a search feature, provide different types of searches for different skill levels and preferences.  
13.8 Provide distinguishing information at the beginning of headings, paragraphs, lists, etc.  
13.9If this document is part of a collection, provide metadata that identifies this document's location in the collection.  
14.3 Use a consistent style of presentation between pages.  

Custom Accessibility Standards

[Information available when using Watchfire products]Watchfire WebXM and WebQA can identify pages that do not meet custom accessibility standards (learn more)

 Links in:
[Information available when using Watchfire products]To help in site maintenance, Watchfire WebXM and WebQA can identify all of the pages that link to this page (learn more)

Details for this item are hidden (click to show) Links out: 134

 Link path from a starting URL:
[Information available when using Watchfire products]To help in site maintenance, Watchfire WebXM and WebQA can identify the URL path that links to this page (learn more)

Now that you've tried WebXACT on a page, find out how Watchfire can help your entire site!

To learn more, choose a product:

  • Watchfire WebXM
  • Watchfire WebQA
  • Watchfire Bobby

Items marked with a Watchfire flame Watchfire flame icon indicate additional information that can be collected by Watchfire WebXM or WebQA.