W3C

Checklist of AERT Techniques

Introduction

This checklist is generated from the list of checkpoints and techniques in the Techniques for Accessibility Evaluation and Repair Tools (AERT). It is intended to be used to evaluate tools to determine which AERT techniques are implemented. Note that there are two axes a tool can be evaluated on: evaluation support and repair support. Along each of these axes are the degrees to which this is supported:

A-Prompt Specific:

The following version of the checklist contains all the points that the first version of A-Prompt covers. These items are marked with an 'A'. Most of the checkpoints are supported, at least partially, but some, such as checking SMIL files for synchronized media, may be covered in a later version of the program.

Bobby Specific:

The following version of the checklist contains all the points that version 3.2 of Bobby covers. These items are marked with a 'B'. 'Automatic' is subject to some amount of judgement, such as correctness of ALT text. We hope to add interactive questions to change most Semi-automatic to Automatic (really auto-ask) in version 4.

Status of this document

This is a very rough working draft for review by the Evaluation and Repair Tools Working Group (ER WG).

Checkpoint 1.1 - Provide a text equivalent for every non-text element
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 1.1.1 [priority 1] Check IMG elements for valid "alt" attribute A,B         A    
Technique 1.1.2 [priority 1] Verify that valid IMG element descriptions ("longdesc" attribute or d-link) are provided where necessary. A B       A    
Technique 1.1.3 [priority 1] Check INPUT elements of type="image" for valid "alt" attribute A,B         A    
Technique 1.1.4 [priority 1] Check APPLET elements for valid HTML equivalent A,B         A    
Technique 1.1.5 [priority 1] Check OBJECT elements of type="image_MIME_types" for valid text equivalents and descriptions (where necessary) A B       A    
Technique 1.1.6 [priority 1] Verify that text equivalents are provided for linked audio files where necessary A B       A    
Technique 1.1.7 [priority 1] Verify that text equivalents are provided for embedded audio files where necessary A B       A    
Technique 1.1.8 [priority 1] Check FRAME elements for valid "longdesc" attribute A B       A    
Technique 1.1.9 [priority 1] Check AREA elements for valid "alt" attribute A,B         A    
Technique 1.1.10 [priority 1] Check SCRIPT elements for valid equivalents where necessary A B       A    
Technique 1.1.11 [priority 1] Check A elements for valid text content A (13.1.1)     B   A (13.1.1)    
Technique 1.1.12 [priority 1] Verify that valid text equivalents are provided for PRE and XMP elements used to create ASCII art. A   B     A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 1.2 - Provide redundant text links for each active region of a server-side image map
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 1.2.1 [priority 1] Verify that a server-side image map has associated text links. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 1.3 - Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 1.3.1 [priority 1] Verify that multimedia have audio descriptions. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 1.4 - For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 1.4.1 [priority 1] Verify that multimedia have synchronized equivalents.   B A       A  
Technique 1.4.2 [priority 1] Check SMIL files for synchronized media       A,B       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 1.5 - Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 1.5.1 [priority 3] Verify that text links are provided for client-side image maps. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 2.1 - Ensure that all information conveyed with color is also available without color, for example from context or markup
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 2.1.1 [priority 1] Verify that information conveyed with color is available without color A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 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
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 2.2.1 [priority 3] Test the color attributes of the following elements for visibility: A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.1 - When an appropriate markup language exists, use markup rather than images to convey information
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.1.1 [priority 2] Verify that elements do not need to be converted to an appropriate markup language.     A,B         A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.2 - Create documents that validate to published formal grammars
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.2.1 [priority 2] Check document for public text identifier A   B   A      
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.3 - Use style sheets to control layout and presentation
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.3.1 [priority 2] Check document for use of style sheets. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.4 - Use relative rather than absolute units in markup language attribute values and style sheet property values
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.4.1 [priority 2] Check document for relative units of measure. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.5 - Use header elements to convey document structure and use them according to specification
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.5.1 [priority 2] Check document for header nesting B A       A    
Technique 3.5.2 [priority 2] Check document for missing header markup   A   B   A    
Technique 3.5.3 [priority 2] Verify that header elements are not used for formatting. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.6 - Mark up lists and list items properly
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.6.1 [priority 2] Check that list elements are within a list container and well nested. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 3.7 - Mark up quotations. Do not use quotation markup for formatting effects such as indentation
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 3.7.1 [priority 2] Verify instances where quote markup should be used. A B       A    
Technique 3.7.2 [priority 2] Verify that Q and BLOCKQUOTE are used properly A B       A    
Technique 3.7.3 [priority 2] Verify that BLOCKQUOTE is not used for formatting A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 4.1 - Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions)
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 4.1.1 [priority 1] Verify changes in the natural language of document.   B A         A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 4.2 - Specify the expansion of each abbreviation or acronym in a document where it first occurs
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 4.2.1 [priority 3] Verify that abbreviations and acronyms need expanding. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 4.3 - Identify the primary natural language of a document
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 4.3.1 [priority 3] Verify the primary language of the document A,B       A      
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 5.1 - For data tables, identify row and column headers
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.1.1 Determine the purpose of the table   A   B       A
Technique 5.1.2 [priority 1] Check data table for row and column headers A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 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
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.2.1 - [Priority 1] Check data tables for multiple levels of row and column headers   B A       A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 5.3 - Do not use tables for layout unless the table makes sense when linearized
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.3.1 [priority 2] Verify that layout tables make sense when linearized   A,B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 5.4 - If a table is used for layout, do not use any structural markup for the purpose of visual formatting
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.4.1 [priority 2] Check layout tables for structural markup A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 5.5 - Provide summaries for tables
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.5.1 [priority 3] Check TABLE elements for valid "summary" attribute A,B         A    
Technique 5.5.2 [priority 2] Check TABLE elements for valid CAPTION element. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 5.6 - Provide abbreviations for header labels
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 5.6.1 [priority 3] Check table for header abbreviations A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 6.1 - Organize documents so they may be read without style sheets
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 6.1.1 [priority 1] Verify that the document is readable when style sheets are not applied. A B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 6.2 - Ensure that equivalents for dynamic content are updated when the dynamic content changes
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 6.2.1 [priority 1] Check the source of FRAME and IFRAME elements for valid markup files. A,B         A    
Technique 6.2.2 [priority 1] Verify that equivalents of dynamic content are updated and available as often as the dynamic content. A   B       A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 6.3 - Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 6.3.1 [priority 1] Verify that the page is usable when programmatic objects are disabled. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 6.4 - For scripts and applets, ensure that event handlers are input device-independent
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 6.4.1 [priority 2] Check for device independent event handlers.   B   A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 6.5 - Ensure that dynamic content is accessible or provide an alternative presentation or page
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 6.5.1 [priority 2] Check that a NOFRAMES element exists within each FRAMESET. A,B         A    
Technique 6.5.2 [priority 2] @@Need something for scripts and programmatic objects?     B          
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 7.1 - Until user agents allow users to control flickering, avoid causing the screen to flicker
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 7.1.1 [priority 1] Verify that the page does not cause flicker.   B   A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 7.2 - Until user agents allow users to control blinking, avoid causing content to blink
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 7.2.1 [priority 1] Check for BLINK elements A,B       A      
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 7.3 - Until user agents allow users to freeze moving content, avoid movement in pages
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 7.3.1 [priority 1] Check for MARQUEE elements A,B       A      
Technique 7.3.2 [priority 1] Verify that programmatic objects do not create moving content A B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 7.4 - Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 7.4.A [priority 2] Remove auto-refresh attributes from META elements A,B       A      
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 7.5 - Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 7.5.1 [priority 2] Check auto-redirect attributes on META elements A,B       A      
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 8.1 - Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 8.1.1 [priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2] Verify that programmatic objects are directly accessible. A B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 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
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 9.1.1 [priority 1] Check for use of server-side image maps A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 9.2 - Ensure that any element that has its own interface can be operated in a device-independent manner
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 9.3 - For scripts, specify logical event handlers rather than device-dependent event handlers
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 9.3.1 [priority 2] Check scripts for logical event handlers   B   A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 9.4 - Create a logical tab order through links, form controls, and objects
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 9.4.1 [priority 3] Check for "tabindex" attribute A B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 9.5 - Provide keyboard shortcuts to important links, form controls, and groups of form controls
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 9.5.1 [priority 3] Check for "accesskey" attribute. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 10.1 - Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 10.1.1 [priority 1] Check A and AREA elements for valid "target" attributes A B       A    
Technique 10.1.2 [priority 1] Verify that scripts do not spawn new windows.   B   A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 10.2 - Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 10.2.1 [priority 2] Verify that LABEL elements are properly positioned. A B         A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 10.3 - Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 10.3.1 [priority 3] Verify that a linearized version of tables used for layout is provided.   B A       A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 10.4 - Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 10.4.1 [priority 3] Check for valid default values of INPUT, TEXTAREA, and SELECT elements. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 10.5 - Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 10.5.1 [priority 3] Check for non-whitespace characters between consecutive A elements. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 11.1 - Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 11.1.1 [priority 2] Verify that W3C technologies are used, where possible and appropriate.     B A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 11.2 - Avoid deprecated features of W3C technologies
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 11.2.1 [priority 2] Check for deprecated features of W3C technologies. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 11.3 - Provide information so that users may receive documents according to their preferences
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 11.3.1 [priority 3] Check that documents are served per user preferences.     B A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 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 (or functionality), and is updated as often as the inaccessible (original) page
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 11.4.1 [priority 1] Verify that the page has passed all checkpoints of the desired conformance level. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 12.1 - Title each frame to facilitate frame identification and navigation
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 12.1.1 [priority 1] Check FRAME elements for valid "title" attributes A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 12.2 - Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 12.3 - Divide large blocks of information into more manageable groups where natural and appropriate
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 12.4 - Associate labels explicitly with their controls
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 12.4.1 [priority 2] Check LABEL elements for valid "for" attribute values. A,B         A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.1 - Clearly identify the target of each link
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.1.1 [priority 2] Verify that the target of each link is clearly identified. A B       A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.2 - Provide metadata to add semantic information to pages and sites
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.2.1 [priority 2] Check for META, ADDRESS, TITLE and LINK elements. A   B     A    
Technique 13.2.2 [priority 2] Check for use of RDF.       A,B       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.3 - Provide information about the general layout of a site
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.4 - Use navigation mechanisms in a consistent manner
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.5 - Provide navigation bars to highlight and give access to the navigation mechanism
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.6 - Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.6.1 [Priority 3] Verify if links should be grouped.     B A       A
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.7 - If search functions are provided, enable different types of searches for different skill levels and preferences
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.7.1 [priority 3] Verify that search functions enable a variety of skill levels and preferences. A   B       A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.8 - Place distinguishing information at the beginning of headings, paragraphs, lists, etc
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.9 - Provide information about document collections
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.9.1 [priority 3] Verify that information about document collections is provided. A,B           A  
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 13.10 - Provide a means to skip over multi-line ASCII art
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 13.10.1 [priority 3] Verify that one can skip over multi-line ASCII art. A   B     A    
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 14.1 - Use the clearest and simplest language appropriate for a site's content
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 14.2 - Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Suggestions for techniques to evaluate or repair this checkpoint                

Checkpoint 14.3 - Create a style of presentation that is consistent across pages
  Evaluation Repair
Technique Automatic Semi-automatic Prompt No support Automatic Semi-automatic Prompt No support
Technique 14.3.1 [priority 3] Verify that a consistent style of presentation is used across pages. A   B       A  
Suggestions for techniques to evaluate or repair this checkpoint                

insert copyright info here

$Date: 2000/11/08 08:17:33 $ Wendy Chisholm