Draft general technique for SC 1.3.3 (variations in presentation of text)

Hi, all.

Here is a draft for a general technique for SC 1.3.3. I've used the
headings from the Techniques template in the WIKI
(http://trace.wisc.edu/wcag_wiki/index.php?title=Technique_Template)

Wasn't sure what to list in the Resources section-- suggestions welcome!


A version in .rtf is attached.
John
 

<draftTechnique>

1.3.3 When information is conveyed through variations in presentation of
text, the information is available in text or the variations in
presentation of text can be programmatically determined.


Applicability
Technologies that support changes in the visual presentation of text,
all baselines
Description
Changing the visual appearance of text is an effective way to convey
information. You can make the information accessible by also doing the
following:
*	Using semantic markup,
*	Stating the information explicitly in the text,
*	Or both.
If semantic markup cannot be used, then:
*	State the information explicitly in the text.
Examples
Example 1: Typographical conventions in technical documentation
Examples of HTML source code are included in a document that explains
how to make Web content accessible. The code examples are semantically
marked (with the HTML <code> element, for example). Visually, the
examples are indented from the left margin and displayed in a different
font than the body text.
Example 2: Font variations within a sentence
An online test requires students to write a short summary of a longer
document. When a sentence in the original document contains a word or
phrase that must be used in the summary, the word or phrase is shown in
a different font than the rest of the sentence. The words and phrases
are semantically marked for emphasis, and a style sheet is used to
change the default visual rendering of the semantic element.
Example 3: Font variations and explicit statements
An online document has gone through multiple drafts. Insertions are
underlined and deletions are struck through. At the end of the draft a
"change history" lists all changes made to each draft.
Resources
Tests
1.	Determine whether variations in presentation of text are used to
convey information.
2.	2. Determine whether the technology used by the content supports
semantic markup.
a.	If yes, then check code for appropriate use of
technology-specific semantic markup. (For example, Example 1 above
should contain the HTML <code> element. If the code examples are cited
from other sources, the <blockquote> element may be used to indent the
example from the left margin; otherwise styling should be used. Example
2 could use HTML <strong> or <em> elements, whose visual appearance
should be controlled by a style sheet.
b.	If the technology does not support semantic markup, then review
the document manually to determine if information conveyed visually is
also stated explicitly in text. (In Example 3 above, words and phrases
shown as underlined or struck through are also listed separately in the
text.) 
</draftTechnique>

"Good design is accessible design."

Dr. John M. Slatin, Director 
Accessibility Institute
University of Texas at Austin 
FAC 248C 
1 University Station G9600 
Austin, TX 78712 
ph 512-495-4288, fax 512-495-4524 
email jslatin@mail.utexas.edu 
Web http://www.utexas.edu/research/accessibility