Since they are the most serious violations, I fixed the two errors first. I added language to the HTML declaration and added [] to delineate the links with more than whitespace. I also added an author and description in the head, as recommended in the general tab. I then corrected an error in journal.html to nest headings properly as well as add language to html.

Check another page: Show Advanced / Accessibility Options Terms of use

Results for http://www.glomagic.com/CSIS139/index.html

Page last checked on Sun 26/11/2006 at 10:12pm.

  General Quality

Accessibility

Privacy

Expand All|Collapse All

This 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 Checkpoints			Manual Checkpoints
	Status	Errors	Instances	Status	Warnings	Instances
Priority 1		0	0		9	25
Priority 2		0	0		15	32
Priority 3		2	11		8	8

Collapse Section|Top of Page

Priority 1 Checkpoints

	Warnings
	9 tests, 25 instances on page	Expand Code Fragments

Guideline		Instances	Line Numbers
1.1	If an image conveys important information beyond what is in its alternative text, provide an extended description.	6	37, 101, 102, 106, 107, 115
2.1	If you use color to convey information, make sure the information is also represented another way.	6	37, 101, 102, 106, 107, 115
4.1	Identify any changes in the document's language.
6.1	If 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.	4	6, 30, 41, 61
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.	4	6, 30, 41, 61
14.1	Use the simplest and most straightforward language that is possible.

Collapse Section|Top of Page

Priority 2 Checkpoints

	Warnings
	15 tests, 32 instances on page	Expand Code Fragments

Guideline		Instances	Line Numbers
2.2	Check that the foreground and background colors contrast sufficiently with each other.	6	37, 101, 102, 106, 107, 115
3.1	Where 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.
6.4	If objects use event handlers, make sure they do not require use of a mouse.
7.2	If this .gif image is animated, make sure it does not contain fast or distracting motion.	3	101, 102, 106
9.2	Make sure that all elements that have their own interface are operable without a mouse.	4	6, 30, 41, 61
10.1	If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening.	4	6, 30, 41, 61
11.1	Use the latest technology specification available whenever possible.
11.2	Avoid use of obsolete language features if possible.	5	36, 40, 88, 111, 120
12.3	Group related elements when possible.
13.1	Make sure that all link phrases make sense when read out of context.
13.1	Add a descriptive title to links when needed.
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.

Collapse Section|Top of Page

Priority 3 Checkpoints

	Errors
	2 tests, 11 instances on page	Expand Code Fragments

Guideline		Instances	Line Numbers
4.3	Identify the language of the text.	1	3
10.5	Separate adjacent links with more than whitespace.	10	90, 91, 92, 93, 94, 95, 101, 102, 106, 116

	Warnings
	8 tests, 8 instances on page

Guideline		Instances	Line Numbers
4.2	Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
9.4	Consider specifying a logical tab order among form controls, links, and objects.
9.5	Consider adding keyboard shortcuts to frequently used links.
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.8	Provide distinguishing information at the beginning of headings, paragraphs, lists, etc.
13.9	If 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

Watchfire WebXM and WebQA can identify pages that do not meet custom accessibility standards (learn more)

Page Links

 Links in:
To help in site maintenance, Watchfire WebXM and WebQA can identify all of the pages that link to this page (learn more)

 Links out: 19

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