Techniques Document Checkpoints 4.3- 6

Comments continued.  As before, I've labeled comments as "minor:
signficicant", "important"

This has most text of original.  I've preceded my comments with LRK:: so
you can quickly skip to them.
>  ------------------------------------------------------------------------
>
>Checkpoint 4.3 - Identify the primary natural language of a document
>
>Technique 4.3.A [priority 3] Check the primary language of the document
>
>   * HTML element must contain a valid LANG attribute
>       1. The value of the LANG attribute must be set to one of the ISO 639
>          language codes
>
>Language for missing/invalid LANG attribute: The primary language of this
>document has not been set.
>
>Link to test file for this technique.
>
>  ------------------------------------------------------------------------
>
>Guideline 5. Create tables that transform gracefully
>
>Checkpoint 5.1 - For data tables, identify row and column headers
>
>Technique 5.1.A [priority 1] Check the table for row and column headers
>
>   * Check the elements between the TABLE start element and TABLE end
>     element for TH (table header) elements
>       1. Each row in the table must start with a TH element
>       2. Each column in the table must start with a TH element
>
>If both row and column headers are missing, notify the user with this
>language: Table is missing headers.
>
>If either row or column headers are missing, notify the user with this
>message: Table has row/column headers but may require column/row headers.

LLink to test file for this technique.
>
>  ------------------------------------------------------------------------
>
>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
>
>Link to discussion on this technique.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 5.3 - Do not use tables for layout unless the table makes sense
>when linearized
>
>(I don't think this can be machine tested. Put up a notification?)
>
LRK:: important: display linearized version to user to check if it makes
sense.  
LRK:: significant: preferably display table and linearized version side by
side with yoked highlighting that move along to check item by item.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 5.4 - If a table is used for layout, do not use any structural
>markup for the purpose of visual formatting
>
>(I don't think this can be machine tested. Put up a notification?)
>
>  ------------------------------------------------------------------------
>
>Checkpoint 5.5 - Provide summaries for tables
>
>Technique 5.5.A [priority 1] Check table for valid SUMMARY
>
>   * TABLE elements must have a valid SUMMARY attribute
>       1. Not allowed - NULL SUMMARY value ("")
>       2. Not allowed - SUMMARY value of spaces (" ")
>       3. Suspicious - SUMMARY value of placeholder SUMMARY values
>
>Language for missing table summary: Summary missing for this table.
>
>Link to test file for this technique.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 5.6 - Provide abbreviations for header labels
>
>Technique 5.6.A [priority 1] Check table for header abbreviations
>
>   * TH elements should have a valid ABBR attribute
>       1. Not allowed - NULL ABBR value ("")
>       2. Not allowed - ABBR value of spaces (" ")
>       3. Suspicious - ABBR value of placeholder ABBR values
>
>Language for missing table header abbreviations: Table header is missing an
>abbreviation. Header names longer than 5 characters should have an
>abbreviation.
>
>Link to test file for this technique.
>
>  ------------------------------------------------------------------------
>
>Guideline 6. Ensure that pages featuring new technologies transform
>gracefully
>
>Checkpoint 6.1 - Organize documents so they may be read without style
>sheets
>
>(I don't think this can be machine tested. User notification?)

LRK:: important: display document without style sheets to visually check
what happens.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 6.2 - Ensure that equivalents for dynamic content are updated
>when the dynamic content changes
>
>Technique 6.2.A [priority 1] Check the FRAME source to ensure it is an HTML
>document.
>
>   * FRAME SRC attribute must have a value of an HTML document
>       1. FRAME SRC attribute value must end with ".html" or ".htm"
>
>Language for frame source not HTML: Frame source (frame source file name)
>should be an HTML document but is not.
>
>Link to test file for this technique.
>
>Link to discussion on this technique.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 6.3 - Ensure that pages are usable when scripts, applets, or
>other programmatic objects are turned off or not supported
>
>Link to discussion on this technique.

LRK:: important: display page with script applet or other programmatic
objects displayed, but "greyed out", e.g. boxed in by a special css box.
Then indicate alternative contents that shows when the objects are turned
off.  This facilitates ready comparison.
>
>  ------------------------------------------------------------------------
>
>Checkpoint 6.4 - For scripts and applets, ensure that event handlers are
>input device-independent
>
>(Can't be machine checked. Notify user?)

LRK:: significant: This is worry of PF I believe in that HTML doesn't have
logical handlers yet, right?
>
>  ------------------------------------------------------------------------
>
>Checkpoint 6.5 - Ensure that dynamic content is accessible or provide an
>alternative presentation or page
>
>Technique 6.5.A [priority 2] Check if there is a NOFRAMES section after a
>FRAMES section.
>
>   * Immediately following a FRAME end element must be a NOFRAMES element.
>
>Language for missing NOFRAMES section: No NOFRAMES section following a
>FRAME section.
>
>Link to test file for this technique.

LRK:: important: continuing the theme of show the author what's happening,
show the noframes content together with the frame content to check them
visually.
>

-------
Leonard R. Kasday, Ph.D.
Universal Design Engineer, Institute on Disabilities/UAP, and
Adjunct Professor, Electrical Engineering
Temple University

Ritter Hall Annex, Room 423, Philadelphia, PA 19122
kasday@acm.org        
(215} 204-2247 (voice)
(800) 750-7428 (TTY)

Received on Monday, 26 July 1999 17:19:03 UTC