This is the first page of a site that is intentionally built
with violations to the WAI guidelines
in order to test the validation/repair tools.

Version 2.3 - 2003-07-31
© Michele Kirchner, ITC-irst, Trento, Italy, 2002, 2003, 2004 (see bottom of page)


NOTE: In the following table all the WAI checkpoints are reported.
If the number of the checkpoint is a link, it links to a page that violates that specific checkpoint;
if it is blue colored, that checkpoint is violated somewhere in the site, without a specific page.


Index of violation pages
Checkpoint Description
Priority 1
1.1(img) Provide a text equivalent for every non-text element 
1.1(ascii art) If ASCII art is present, consider substituting it with an accessible image.
1.1(extdd.descr.) If an image conveys important information beyond what is in its alternative text, provide an extended description.
1.1(img map) Provide a text alternative for image Maps. 
1.1(img-wrng) Provide a text equivalent for every non-text element  (test: alt="name.gif")
1.2 Provide redundant text links for each active region of a server-side image map.
1.3 Until ..., provide an auditory description of the important information of the visual track of a multimedia presentation.
1.4 For any time-based multimedia presentation, synchronize equivalent alternatives with the presentation.
2.1(text) Ensure that all information conveyed with color is also available without color, for example from context or markup.
2.1(image) Ensure that all information conveyed with color is also available without color, for example from context or markup.
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents
5.1 For data tables, identify row and column headers.
5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. 
6.1 Organize documents so they may be read without style sheets.
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. 
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.
7.1 Until ..., avoid causing the screen to flicker.
9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information.
11.4/a Check for the string 'Text Version' within the document.
11.4/b  - Check for a Global Text Version Link within the document.
11.4/c  - Check for an Accessibility Policy Link within the document.
12.1 Title each frame to facilitate frame identification and navigation.
14.1 Use the clearest and simplest language appropriate for a site's content.
Priority 2
2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen
3.1 When an appropriate markup language exists, use markup rather than images to convey information.
3.2 Create documents that validate to published formal grammars.
3.3(partially) Use style sheets to control layout and presentation.
3.4/a - 3.4/b - 3.4/c Use relative rather than absolute units in markup language attribute values and style sheet property values.
3.5 Use header elements to convey document structure and use them according to specification
3.6 Mark up lists and list items properly. 
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. 
5.3 Do not use tables for layout ... or ... provide an alternative equivalent... .
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
6.4 For scripts and applets, ensure that event handlers are input device-independent.
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.
7.2 Until user agents allow users to control blinking, avoid causing content to blink
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
7.4/a - 7.4/b Until ..., do not create periodically auto-refreshing pages.
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically.
8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
10.1 Until ..., do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
10.2 Until ..., for all form controls with implicitly associated labels, ensure that the label is properly positioned.
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
11.2 Avoid deprecated features of W3C technologies. 
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.
12.4 Associate labels explicitly with their controls. 
13.1 Clearly identify the target of each link (attribute title).
13.2 Provide metadata to add semantic information to pages and sites.
13.3 Provide information about the general layout of a site.
13.4  Use navigation mechanisms in a consistent manner.
Priority 3
1.5 Until ..., provide redundant text links for each active region of a client-side image map.
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. 
4.3 Identify the primary natural language of a document.
5.5 Provide summaries for tables.
5.6 Provide abbreviations for header labels.
9.4 Create a logical tab order through links, form controls, and objects.
9.5 Provide keyboard shortcuts to important links form controls, and groups of form controls.
10.3 Until ..., provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.
10.4 Until ..., include default, place-holding characters in edit boxes and text areas.
10.5 Until ..., include non-link, printable characters (surrounded by spaces) between adjacent links. 
11.3 Provide information so that users may receive documents according to their preferences
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.
13.6 Group related links, identify the group (for user agents), and, until ..., provide a way to bypass the group. 
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
13.9 Provide information about document collections
13.10 Provide a means to skip over multi-line ASCII art.
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
14.3 Create a style of presentation that is consistent across pages.


Copyright Notice
© Michele Kirchner, ITC-irst, Trento, Italy, 2003, 2003, 2004
This page and the linked ones are copyright by Michele Kirchner and ITC-irst
They are free software; you can redistribute them and/or modify them under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
They are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
In order to receive a copy of the GNU General Public License, see the GNU-GPL web pages or write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.

You may use these pages for personal use or for research.
You may use these pages to publish any scientific work, but you need written permission by the author BEFORE the work is published.
You may NOT use these pages or the contents of them (even partially) in order to take profits from their use, even indirectly.
If you modify or complete these pages, please give note to the original author: your work may be included in the original pages if it is recognized to improve them.