[techs] HTML Techs Checklist Items as T/F statements

Hi,

These are some old notes from the 2003 Technical Plenary F2F that take the
"rules" from the last HTML Techniques draft and rewrite them as true/false
statements.

These true/false statements would map to the checklist-items in our
techniques DTD and be utilized in the WCAG 2.0 checklists.

Use the TITLE element to describe the document. --> 	
	The TITLE element is used (mandatory). 
		-or-
	The TITLE element describes the document.

Use the ADDRESS element to define a page's author. -->	
	The ADDRESS element is used.
	(note: what does knowing who (or what process) authored a page have
to 	do with accessibility? Should this technique be removed?)

Avoid using <META HTTP-EQUIV="refresh"> to automatically redirect users. -->
Users are automatically redirected.
	Techniques for accessible automatic redirection are applied.
(provide 	list)

Avoid using <META HTTP-EQUIV="refresh"> to refresh pages periodically. -->
Pages are periodically refreshed.
	Techniques for accessible periodical refresh are applied. (provide
list - are there any??)

Use the !DOCTYPE statement to define the HTML or XHTML version of your
document. --> 	
	The !DOCTYPE statement defines the HTML or XHTML version of
documents.

Use the LINK element to describe the structure of your document. --> 	
	For document collections (??) the LINK element is used to describe
the 	structure of documents.

Use the LINK element to refer to accessible alternative documents. --> 	
	An alternate version of the content is available in an accessible
form 	that meets all of the level 1 criterion.
		-or-
	The LINK element is used to refer to the alternate version of the
content.

Use HTML header elements H1 through H6, in order, to define the structure of
the document. -->	
	Header elements (H1 through H6) are used, in order, to define the
structure of the document.

Use CSS, not HTML header elements, to create font effects. --> 	
	CSS (not HTML header elements) are used to create font effects.

Use the lang attribute to identify the natural language used in a document.
--> 	
	The lang attribute is used to identify the natural language of
document(s).
(upper level ? is do you use multiple languages?)	
	The lang attribute is used to identify changes in the natural
language 	of document(s).

Use the strong and em elements, rather than b and i, to denote emphasis. -->
STRONG and EM elements (not B and I elements) are used to denote
emphasis.

Use the acronym element to expand acronyms where they first occur. -->
ACRONYM elements are used to expand acronyms where they first occur.

Use the abbr element to expand abbreviations where they first occur. -->
ABBR elements are used to expand abbreviations where they first occur.

--
Ben Caldwell | caldwell@trace.wisc.edu
Trace Research and Development Center (http://trace.wisc.edu)

Received on Thursday, 10 July 2003 15:46:27 UTC