<?xml version="1.0" encoding="UTF-8"?>
<wcag-tech>
<!-- front matter -->
	<front-matter>
		<abstract>This document describes techniques for authoring accessible Cascading Style
Sheets (<acronym title="Cascading Style Sheets">CSS</acronym>). This is the
first Working Draft associated with the latest Web Content Accessibility
Guidelines 2.0 Working Draft.</abstract>
		<status></status>
	</front-matter>
<!-- introduction -->
	<doc-intro>
		<h2>1 Why CSS?</h2>
		<blockquote>The term "style sheet" comes from the idea of a document that tells a human
		  typesetter the house policies for how documents of particular types (not
		  particular documents) should appear.</blockquote>
		<p><a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2001AprJun/0351.html">David
		Woolley - 7 May 2001</a></p>
		<h3>1 <a id="consistency" name="consistency">Author benefits</a></h3>
		<ul>
		  <li>Increases consistency.</li>
		  <li>Decreases maintenance.</li>
		  <li>Separating markup for content from markup for presentation decreases
		    clutter of markup.</li>
		  <li>Able to create dynamic decorative effects.</li>
		</ul>
		<p>To take advantage of these features in HTML:</p>
		<ul>
		  <li>Identify the various terms included throughout a site and create a look
		    for each in your style sheets.</li>
		  <li>Mark up content properly according to its function, then create classes
		    that further specify the function. For example, if you use the p element
		    to set the byline on an article, create a class called "byline".</li>
		  <li>Use the same "class" name for the same concept in all of the style
		    sheets.</li>
		  <li>Use external style sheets rather than embed style information.</li>
		  <li>Use a minimal number of style sheets for your site.</li>
		</ul>
		<p>Where style sheets have been optional to display HTML content, they are
		required to display information from XML applications. As explained in
		question C.22 of <a href="http://www.ucc.ie/xml/#Author">The XML FAQ</a> by
		Peter Flynn:</p>
		<blockquote>
		  <p>In HTML, default styling is built into the browsers because the tagset of
		  HTML is predefined and hardwired into browsers. In XML, where you can define
		  your own tagset, browsers cannot know what names you are going to use and
		  what they will mean, so you need a stylesheet if you want to display the
		  formatted text.</p>
		</blockquote>
		<p>Therefore, the differences between CSS for XML and HTML are:</p>
		<ul>
		  <li>define styles for elements and attributes (including class if that is
		    defined in the language),</li>
		  <li>content is marked up for function since there is no hardwired
		    presentation,</li>
		  <li>style information is usually required to be in an external style sheet
		    (always?),</li>
		</ul>
		<p>To apply the same external style sheet to both HTML and XML</p>
		<ul>
		  <li>make the HTML class names the same as the XML element names,</li>
		  <li>define each style twice: once with a period (HTML class name) and once
		    without (XML element name). e.g., .copyright, copyright {font-size :
		  .5em}</li>
		</ul>
		<p>@@test and confirm these statements.</p>
		<p>For more information about XML and CSS:</p>
		<ul>
		  <li><a href="http://www.xmlmag.com/upload/free/features/xml/1999/01win99/kc3win99/kc3win99.asp">Create
		    Extensible Web Pages with XML and CSS</a></li>
		  <li><a href="http://www.ucc.ie/xml/">The XML FAQ</a> by Peter Flynn</li>
		</ul>
		<p>For more information about creating accessible XML applications refer to
		the <a href="/WAI/PF/xmlgl/">XML Accessibility Guidelines</a>.</p>
		<h3>2 <a id="user-override" name="user-override">User benefits</a></h3>
		<ul>
		  <li>Ability to change presentation to suit preferences or needs such as: 
		    <ul>
		      <li>higher contrast color combination,</li>
		      <li>increase font size,</li>
		      <li>present the information aurally with a preferred scheme (through a
			screen reader or over the phone),</li>
		      <li>present the information in Braille with a preferred scheme,</li>
		      <li>present the information on a smaller screen (mobile device with a
			small screen, such as a PDA).</li>
		    </ul>
		  </li>
		  <li>Ability to turn off style sheets if have a slow modem connection</li>
		</ul>
		<p>In CSS2, if a user's style sheet contains "!important", it takes precedence
		over any rule in an author's style sheet. This is different from CSS1, where
		the author always has final say over styles. For more information on the
		!important selector refer to the CSS1 and CSS2 specifications. Also, note that
		since !important was introduced with CSS1 and is more widely implemented than
		CSS2, the author might have preference over the user in most of the existing
		user agents. However, it seems that !important is rarely used in author style
		sheets and therefore might work as defined in CSS2.</p>
		<p>For examples of user's style sheets, refer to Appendix ?? - Example user's
		style sheets.</p>
		<p>For more information on the accessibility of CSS refer to:</p>
		<ul>
		  <li><a href="http://www.w3.org/TR/REC-CSS2/intro.html#q6">CSS Design
		    Principles</a> in the CSS2 Spec</li>
		  <li><a href="http://www.w3.org/TR/CSS-access">Accessibility Features of
		    CSS</a> by Ian Jacobs and Judy Brewer</li>
		</ul>	
	</doc-intro>
<!-- categories-->
	<category id="style-fonts" name="Fonts">
		<intro> 
		</intro>
	</category>
	<category id="style-colors" name="Colors">
		<intro>
		</intro>
	</category>
	<category id="units" name="Units of Measure">
		<intro>
			<blockquote>Think about what needs to change in size and what doesn't.  Raster images, for example, have fixed width and heights.  We specify them in the
			img tag in pixels...Similarly, if I just want to move the text away from the border of the page, setting the padding on the body to 5 px shouldn't be a
			  problem.  Text, on the other hand, should always be free to change size (a good reason not to use text in images).  But when my text doubles in size,
			  do I need the gutter next to it to double in size as well?  Probably not. In  fact, doubling the gutter might even decrease the usability of the page.
			</blockquote>
			<p><a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2001AprJun/0338.html">Charles Munat - 6 May 2001</a></p>
		</intro>
	</category>
	<category id="style-text" name="Text style effects">
		<intro><p>The following CSS2 properties can be used to style text:</p>
			<ul>
				<li>Case: 'text-transform' (for uppercase, lowercase, and capitalization).</li>
				<li>Shadow effects: 'text-shadow'</li>
				<li>Underlines, overlinks, blinking: 'text-decoration'.</li>
			</ul>
			<p><strong>Note.</strong> If blinking content (e.g., a headline that appears and disappears at regular intervals) is used, provide a mechanism for
			stopping the blinking. In CSS, 'text-decoration: blink' will cause content to blink and will allow users to stop the effect by turning off style
			sheets or overriding the rule in a user style sheet. Do not use the BLINK and MARQUEE elements. These elements are not part of any W3C specification
			for HTML (i.e., they are non-standard elements).</p>
			<p>@@ there are no techniques for this category</p>
		</intro>
	</category>
	<category id="generated-content" name="Generated content">
		<intro><p>CSS2 includes several mechanisms that allow content to be generated from style sheets:</p>
			<ul>
				<li>the :before and :after pseudo-elements and the 'content' property. When
				used together, these allow authors to insert markers (e.g., counters and
				constant strings such as "End Example" in the examples below) before or
				after and element's content.</li>
				<li>the 'cue', 'cue-before', and 'cue-after' properties. This properties
				allow users to play a sound before or after an element's content.</li>
				<li>List styles, which may be numbers, glyphs, or images (usually associated
				with the LI element in HTML). CSS2 adds international list styles to the
				styles defined in CSS1. See the 'list-style-type' and 'content'
				properties.</li>
			</ul>
			<p>Generated content can serve as markers to help users navigate a document
			and stay oriented when they can't access visual clues such as proportional
			scrollbars, frames with tables of contents, etc.</p>
		</intro>
	</category>
	<category id="" name="">
		<intro>
		</intro>
	</category>
	<category id="" name="">
		<intro>
		</intro>
	</category>
<!-- techniques -->
	<technique id="fallback-font">
		<category-ref idref="style-fonts"/>
		<name></name>
		<applies-to checkpoint="" success-criteria=""/>
		<description></description>
		<rule>Always specify a fallback generic font.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>BODY { font-family: "Gill Sans", sans-serif }</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="css-fonts-over-deprecated">
		<category-ref idref="style-fonts"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>Use CSS properties to format text (: 'font-family', 'font-size', 'font-size-adjust', 'font-stretch', 'font-style', 'font-variant',
		and 'font-weight'.) Instead of the following deprecated font elements and attributes in HTML:
		FONT, BASEFONT, "face", and "size".</description>
		<rule>Instead of using deprecated presentation elements and attributes, use the many CSS properties to
		control font characteristics.
		</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code><pre>&lt;STYLE type="text/css"&gt;
				P.important { font-weight: bold }
				P.less-important { font-weight: lighter; font-size: smaller }
				H2.subsection { font-family: Helvetica, sans-serif }
				&lt;/STYLE&gt;</pre>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="html-non-deprecated">
		<category-ref idref="style-fonts"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>If you must use HTML elements to control font information, use BIG and SMALL, which are not deprecated.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="number-not-name">
		<category-ref idref="style-colors"/>
		<name>Color Contrast</name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Use numbers, not names, for colors.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation></explanation>
			<sample>
				<code>
				<pre>H1 {color: #808000}
				H1 {color: rgb(50%,50%,0%)}</pre>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<example type="deprecated">
			<explanation></explanation>
			<sample>
				<code><pre> H1 {color: red}</pre></code>
			</sample>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	
	<technique id="css-colors">
		<category-ref idref="style-colors"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Use these CSS properties to specify colors:
			<ul>
				<li>'color', for foreground text color.</li>
				<li>'background-color', for background colors.</li>
				<li>'border-color', 'outline-color' for border colors.</li>
				<li>For link colors, refer to the :link, :visited, and :active  pseudo-classes.</li>
			</ul>
		</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="good-contrast">
		<category-ref idref="style-colors"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Ensure that foreground and background colors contrast well.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href="">For more information about colors and contrasts, refer to <cite><a href="#ref-LIGHTHOUSE" title="Link to reference LIGHTHOUSE">[LIGHTHOUSE]</a></cite>
		</see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<test>To test whether color contrast is sufficient to be read by people with color deficiencies or by those with low
		resolution monitors, print pages on a black and white printer (with backgrounds and colors appearing in
		grayscale). Also try taking the printout and copying it for two or three generations to see how it degrades. This will
		show you where you need to add redundant cues (example: hyperlinks are usually
		underlined on Web pages), or whether the cues are too small or indistinct to hold up well.</test>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="specify-fore-and-back">
		<category-ref idref="style-colors"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>If specifying a foreground color, always specify a background color as well (and vice versa).</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="style-info-not-in-color-alone">
		<category-ref idref="style-colors"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>For example, when asking for input from users, do not write "Please select an item from
		those listed in green." Instead, ensure that information is available through other style effects (e.g., a font
		effect) and through context (e.g,. comprehensive text links).</description>
		<rule>Ensure that information is not conveyed through color alone</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>For instance, in this document, examples are styled by default (through style sheets) as follows:
				<ul>
					<li>They are surrounded by a border.</li>
					<li>They use a different background color.</li>
					<li>They begin with the word "Example" or "Deprecated Example".</li>
					<li>They also end with the phrase "End example", but that phrase is hidden by default with
					'display: none'. For user agents that don't support style sheets or when style sheets are
					turned off, this text helps delineate the end of an example for readers who may not be
					able to see the border around the example.</li>
				</ul>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<test>To test whether your document still works without colors, examine it with a monochrome monitor or
		browser colors turned off. Also, try setting up a color scheme in your browser that only uses black,
		white, and the four browser-safe greys and see how your page holds up.
		</test>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="units-that-change">
		<category-ref idref="units"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>
		</description>
		<rule><p>Use "em" or % for properties that need to change:</p>
			<ul>
				<li>font size,</li>
				<li>line height,</li>
				<li>@@create exhaustive list.  any exceptions?</li>
			</ul>
		</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>Use em to set font sizes</explanation>
			<sample><pre>H1 { font-size: 2em }</pre></sample>
			<screen href=""/>
		</example>
		<example type="deprecated">
			<explanation>Rather than</explanation>
			<sample><pre>H1 { font-size: 12pt }</pre></sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="units-for-static">
		<category-ref idref="units"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Use px for properties that do not need to change:
			<ul>
			<li>height and width of raster images,</li>
			<li>margins,</li>
			<li>@@create exhaustive list. any exceptions?</li>
			</ul>
		</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>Use relative length units and percentages (@@needs to be fixed).</explanation>
			<sample>
				<code><pre>BODY { margin-left: 15%; margin-right: 10%}</pre></code>
			</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation>Use absolute length units when the physical characteristics of the output medium are known.</explanation>
			<sample>
				<code><pre>.businesscard { font-size: 8pt }</pre></code>
			</sample>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="text-as-text">
		<category-ref idref=""/>
		<name></name>
		<applies-to checkpoint=""/>
		<description><p>Using text instead of images means that the information will be available to a greater number of users
		(with speech synthesizers, braille displays, graphical displays, etc.). Using style sheets will also allow users to
		override author styles and change colors or fonts sizes more easily.</p>
		<p>If it is necessary to use a raster-based images to create a text effect the image must be accessible
		(refer to the section on <a href="http://www.w3.org/TR/WCAG10-TECHS/#def-text-equivalent">
		 text equivalents</a> ).</p></description>
		<rule>Use style sheets to style text rather than representing text in images. </rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example type="deprecated">
			<explanation>The image shows the word "Example" in large, red characters. The <code>alt</code> attribute denotes this.
			</explanation>
			<sample>
				<code><pre>&lt;P&gt;This is an 
				&lt;IMG src="BigRedExample.gif" alt="example"&gt; 
				 of what we mean.
				&lt;/P&gt;</pre></code>
			</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation>This is how to create the large, red character effect with CSS</explanation>
			<sample>@@to add</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation>This image shows text effects that can not yet be created via CSS</explanation>
			<sample>@@to be created</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="text-formatting">
		<category-ref idref=""/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>
			<ul>
				<li>Indentation: 'text-indent'. Do not use the BLOCKQUOTE or any other  structural element to indent text.</li>
				<li>Letter/word spacing: 'letter-spacing', 'word-spacing'. </li>
				<li>White space: 'white-space'. This property controls the white space  processing of an element's content.</li>
				<li>Text direction: 'direction', 'unicode-bidi'.</li>
				<li>The :first-letter and :first-line pseudo-elements allow authors to refer to the first letter or line of a paragraph of text.</li>
			</ul>
		</description>
		<rule>Use CSS2 properties to control the formatting and position of text</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>When letters are separated by whitespace they are read as individual letters. Thus,
			<code>"<p>H E L L O</p>"</code>  will be read by a screen reader as the individual letters, 'H', 'E', 'L', 'L', 'O' rather than the word "hello."
			Create the same visual effect with the 'word-spacing' property applied to "HELLO". Text without spaces will be
			transformed effectively to speech.
			</explanation>
			<sample>
				<code>@@example showing use of "word-spacing"
				</code>
			</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation>This example shows how to use style sheets to create a drop-cap effect.
			</explanation>
			<sample>
				<pre>&lt;HEAD&gt;
				&lt;TITLE&gt;Drop caps&lt;/TITLE&gt;
				&lt;STYLE type="text/css"&gt;
				      .dropcap { font-size : 120%; font-family : Helvetica } 
				&lt;/STYLE&gt;
				&lt;/HEAD&gt;
				&lt;BODY&gt;
				&lt;P&gt;&lt;SPAN class="dropcap"&gt;O&lt;/SPAN&gt;nce upon a time...
				&lt;/BODY&gt;</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="rules-and-borders">
		<category-ref idref=""/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>
			<p>Rules and borders may convey the notion of "separation" to visually enabled
			users but that meaning cannot be inferred out of a visual context.</p>
			<p>Use these CSS properties to specify border styles:</p>
				<ul>
					<li>'border', 'border-width', 'border-style', 'border-color'.</li>
					<li>'border-spacing' and 'border-collapse' for tables.</li>
					<li>'outline, 'outline-color', 'outline-style', and 'outline-width' for dynamic outlines.</li>
				</ul>
		</description>
		<rule>Use style sheets to create rules and borders.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			In this example, the H1 element will have a top border that is 2px thick,
			red, and separated from the content by 1em.
			</explanation>
			<sample>
				<pre>   &lt;HEAD&gt;
					   &lt;TITLE&gt;Redline with style sheets&lt;/TITLE&gt;
					   &lt;STYLE type="text/css"&gt;
					        H1 { padding-top: 1em; border-top: 2px red }
					   &lt;/STYLE&gt;
					   &lt;/HEAD&gt;
					   &lt;BODY&gt;
					   &lt;H1&gt;Chapter 8 - Auditory and Tactile Displays&lt;/H1&gt;
					   &lt;/BODY&gt;</pre>
			</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation>
			If a rule (e.g., the HR element) is used to indicate structure, be sure to
			indicate the structure in a non-visual way as well. (e.g., by using structural markup).
			In this example, the DIV element is used to create a navigation bar, which includes a horizontal separator.
			</explanation>
			<sample>
				<pre>&lt;DIV class="navigation-bar"&gt;
					&lt;HR&gt;
					&lt;A rel="Next" href="next.html"&gt;[Next page]&lt;/A&gt;
				        &lt;A rel="Previous" href="previous.html"&gt;[Prevous page]&lt;/A&gt;
					&lt;A rel="First" href="first.html"&gt;[First page]&lt;/A&gt;
					&lt;/DIV&gt;</pre>
			</sample>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="generated-content-equivalents">
		<category-ref idref="generated-content"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Provide a text equivalent for any important image or text generated by style sheets
		(e.g., via the 'background-image', 'list-style', or 'content'  properties). @@isn't this saying the same
		basic thing as the other rule? thus, putting all of the examples in the other rule. assume we can get
		rid of this one?</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="generated-content-in-dom">
		<category-ref idref="generated-content"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule>Ensure that important content appears in the document object. Text
		generated by style sheets is not part of the document source and will not
		be available to assistive technologies that access content through the
		Document Object Model Level 1 ([[DOM1]). @@remove specific reference to Level 1?</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>The following user style sheet generates the words "End Example"
			after each example in the document.  Examples are contained in <code>div</code> elements
			marked as class "example."
			</explanation>
			<sample>
			<pre> 
			DIV.example:after {     
			  content: End Example  
			}</pre>
			</sample>
		</example>
		<example>
			<explanation>Users can number paragraphs to help locate current reading position in a document.</explanation>
			<sample>
				<pre> 
				P:before {     
				  content: counter(paragraph) ". " ;
  			          counter-increment: paragraph  
				}</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="contextual-html-lists">
		<category-ref idref="generated-content"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>If lists are marked up correctly, i.e. with <code>UL</code> for unordered lists and <code>OL</code> for
		ordered lists, CSS can be used to provide contextual clues in lists.</description>
		<rule></rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>This CSS2 style sheet provides compound numbers for nested lists created with either UL or OL
			elements. Items are numbered as "1", "1.1", "1.1.1", etc.</explanation>
			<sample>
				<pre>&lt;STYLE type="text/css"&gt;
				    UL, OL { counter-reset: item }
				    LI { display: block }
				    LI:before { content: counters(item, "."); counter-increment: item }
				&lt;/STYLE&gt;</pre>
			</sample>
			<screen href=""/>
		</example>
		<example>
			<explanation><p>Until either CSS2 is widely supported by user agents or user agents allow
			users to control rendering of lists through other means,
			consider providing contextual clues in nested lists. The following CSS1
			mechanism shows how to hide the end of a list when style sheets are turned on,
			and to reveal it when style sheets are turned off, when user style sheets
			override the hiding mechanism, or when style sheets aren't supported.</p>
			<p>Note: This example does not help the case of wrapping list items. With some
			more effort, the author could put similar markup at the end of each list item.</p>
			<!-- p>@@Question: Perhaps it's also helpful to use this mechanism at the
			beginning of each list to say how many items are in the list. Any thoughts?</p -->
			<!-- p>@@Need to create test file determine what users think of this proposal.</p -->
			</explanation>
			<sample>
			<pre>  &lt;STYLE type="text/css"&gt;
			      .endoflist { display: none }
			  &lt;/STYLE&gt;
			  &lt;UL&gt;
			     &lt;LI&gt;Paper:
				&lt;UL&gt;
				   &lt;LI&gt;Envelopes
				   &lt;LI&gt;Notepaper
				   &lt;LI&gt;Letterhead
				   &lt;LI&gt;Poster paper 
				   &lt;span class="endoflist"&gt;(End of Paper)&lt;/span&gt;
				&lt;/UL&gt;
			     &lt;LI&gt;Pens:
				&lt;UL&gt;
				   &lt;LI&gt;Blue writing pens
				   &lt;LI&gt;whiteboard pens 
				   &lt;span class="endoflist"&gt;(End of Pens)&lt;/span&gt;
				&lt;/UL&gt;
			     &lt;LI&gt;Fasteners:
				&lt;UL&gt;
				   &lt;LI&gt;paper clips
				   &lt;LI&gt;staples
				   &lt;LI&gt;Big lengths of rope. 
				   &lt;span class="endoflist"&gt;(End of Fasteners)&lt;/span&gt;
				&lt;/UL&gt; 
			     &lt;span class="endoflist"&gt;(End of Office Supplies)&lt;/span&gt;
			  &lt;/UL&gt;</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="layout">
		<category-ref idref="style-alignment"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>
			<p>Layout, positioning, layering, and alignment should be done through style sheets (notably by using CSS floats and absolute positioning):</p>
			<ul>
			  <li>'text-indent', 'text-align', 'word-spacing', 'font-stretch'. Each of
			    these properties allows users to control spacing without adding additional
			    spaces. Use 'text-align: center' instead of the deprecated CENTER
			  element.</li>
			  <li>'margin', 'margin-top', 'margin-right', 'margin-bottom', 'margin-left'.
			    With these properties, authors can create space on four sides of an
			    element's content instead of adding non-breaking spaces (&amp;nbsp;).</li>
			  <li>'float', 'position', 'top', 'right', 'bottom', 'left'. With these
			    properties, the user can control the visual position of almost any element
			    in a manner independent of where the element appears in the document.
			    Authors should always design documents that make sense without style
			    sheets (i.e., the document should be written in a "logical" order) and
			    then apply style sheets to achieve visual effects. The positioning
			    properties may be used to create margin notes (which may be automatically
			    numbered), side bars, frame-like effects, simple headers and footers, and
			    more.</li>
			  <li>The 'empty-cells' property allows users to leave table cells empty and
			    still give them proper borders on the screen or on paper. A data cell that
			    is meant to be empty should not be filled with white space or a
			    non-breaking space just to achieve a visual effect.</li>
			</ul>
		</description>
		<rule>Use style sheets to create layout, positioning, layering, and alignment.</rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="images-as-spacers">
		<category-ref idref="layout"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>If content developers cannot use style sheets and must use invisible or
		transparent images (e.g., with IMG) to lay out images on the page, they should use <code>alt=""</code>.
		@@instead put a section in HTML techniques and link to that instead of recreating it?</description>
		<rule></rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example type="deprecated">
			<explanation>Do <strong>not</strong> use &amp;nbsp; or the text "spacer" as the text equivalent for
			images. </explanation>
			<sample>
				<pre>   my poem requires a big space&lt;IMG src="10pttab.gif" alt="&amp;nbsp;&amp;nbsp;&amp;nbsp;"&gt;here
					   &lt;IMG src="spacer.gif" alt="spacer"&gt;
					   &lt;IMG src="colorfulwheel.gif" alt="The wheel of fortune"&gt;
				</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="absolute-positioning">
		<category-ref idref="layout"/>
		<name></name>
		<applies-to checkpoint=""/>
		<description>Using the positioning properties of CSS2, content may be displayed at any
		position on the user's viewport. The order in which items appear on a screen
		may be different than the order they are found in the source document. </description>
		<rule>@@something about using structural markup and document order </rule>
		<test>Turn off style sheets to determine the reading order.</test>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example type="deprecated">
			<explanation><p>The following example demonstrates a few principles:</p>
				<ol>
				  <li>the text appears visually in the browser in a different order than in
				    the markup.</li>
				  <li>CSS positioning may be used to create tabular effects. A TABLE element
				    could have been used to create the same effect.</li>
				</ol>
				<p>Note that a class is defined for each object that is being positioned. The
				use of "id" could be substituted for "class" in these examples. "Class" was
				used because in the live example, the objects are replicated and thus not
				unique.</p>
			</explanation>
			<sample>
				<pre>&lt;head&gt;&lt;style type="text/css"&gt;
				  .menu1 { position: absolute; top: 3em; left: 0em; 
					   margin: 0px; font-family: sans-serif; 
					   font-size: 120%; color: red; background-color: white }  
				  .menu2 { position: absolute; top: 3em; left: 10em; 
					   margin: 0px; font-family: sans-serif; 
					   font-size: 120%; color: red; background-color: white }
				  .item1 { position: absolute; top: 7em; left: 0em; margin: 0px }
				  .item2 { position: absolute; top: 8em; left: 0em; margin: 0px }
				  .item3 { position: absolute; top: 9em; left: 0em; margin: 0px }
				  .item4 { position: absolute; top: 7em; left: 14em; margin: 0px }
				  .item5 { position: absolute; top: 8em; left: 14em; margin: 0px }
				  #box { position: absolute; top: 5em; left: 5em } 
				&lt;/style&gt;&lt;/head&gt;
				&lt;body&gt;
				&lt;div class="box"&gt;
				  &lt;span class="menu1"&gt;Products&lt;/span&gt; 
				  &lt;span class="menu2"&gt;Locations&lt;/span&gt; 
				  &lt;span class="item1"&gt;Telephones&lt;/span&gt; 
				  &lt;span class="item2"&gt;Computers&lt;/span&gt; 
				  &lt;span class="item3"&gt;Portable MP3 Players&lt;/span&gt; 
				  &lt;span class="item5"&gt;Wisconsin&lt;/span&gt; 
				  &lt;span class="item4"&gt;Idaho&lt;/span&gt;
				&lt;/div&gt;
				&lt;/body&gt;</pre>
			</sample>
			<screen href="cssimages/style-sheet-tg1.gif"
				alt="Screen shot of the example code as it appears when style sheets applied">
				<description>When style sheets are applied, the text appears in two columns. Elements of
				class "menu1" (Products) and "menu2" (Locations) appear as column headings.
				"Telephones, Computers, and Portable MP3 Players" are listed under Products
				and "Wisconsin" and "Idaho" are listed under Locations.</description>
			</screen>
			<screen href="cssimages/style-sheet-tg2.gif"
				alt="Screen shot of the example code as it appears without style sheets">
				<description>When style sheets are not applied, all of the text appears in one line of
				words, "Products Locations Telephones Computers Portable MP3 Players Wisconsin
				Idaho". They appear in the order in which they are written in the source.
				Therefore, what appear as column headings when style sheets are applied are
				the first phrases since they were defined first in the source.</description>
			</screen>
		</example>
		<example>
			<explanation>The following example shows that the same visual appearance may be created
			in a browser that support style sheets as well as creating a more meaningful
			presentation when style sheets are not applied. Structural markup (definition
			lists) have been applied to the content. Note that the margins have been set
			to 0 since in HTML browsers, definition lists are displayed with a margin set
			on the DD element.
			</explanation>
			<sample>
				<pre>&lt;head&gt;&lt;style type="text/css"&gt;
				  .menu1 { position: absolute; top: 3em; left: 0em; 
					   margin: 0px; font-family: sans-serif; 
					   font-size: 120%; color: red; background-color: white }  
				  .menu2 { position: absolute; top: 3em; left: 10em; 
					   margin: 0px; font-family: sans-serif; 
					   font-size: 120%; color: red; background-color: white }
				  .item1 { position: absolute; top: 7em; left: 0em; margin: 0px }
				  .item2 { position: absolute; top: 8em; left: 0em; margin: 0px }
				  .item3 { position: absolute; top: 9em; left: 0em; margin: 0px }
				  .item4 { position: absolute; top: 7em; left: 14em; margin: 0px }
				  .item5 { position: absolute; top: 8em; left: 14em; margin: 0px }
				  #box { position: absolute; top: 5em; left: 5em } 
				&lt;/style&gt;&lt;/head&gt;
				&lt;body&gt;
				&lt;div class="box"&gt;
				&lt;dl&gt;
				  &lt;dt class="menu1"&gt;Products&lt;/dt&gt;
				    &lt;dd class="item1"&gt;Telephones&lt;/dd&gt;
				    &lt;dd class="item2"&gt;Computers&lt;/dd&gt;
				    &lt;dd class="item3"&gt;Portable MP3 Players&lt;/dd&gt;
				  &lt;dt class="menu2"&gt;Locations&lt;/dt&gt;
				   &lt;dd class="item4"&gt;Idaho&lt;/span&gt;
				   &lt;dd class="item5"&gt;Wisconsin&lt;/span&gt;
				  &lt;/dt&gt;
				&lt;/dl&gt;
				&lt;/div&gt;
				&lt;/body&gt;</pre>
			</sample>
			<screen href="cssimages/style-sheet-tg3.gif"
				alt="Example code as it appears when style sheets not applied but transform gracefully">
				<description>When style sheets are applied, it looks as it did before. However, now when the style sheets are not applied,
				the text appears in a definition list rather than a string of words. What
				appear as column headings when style sheets are applied, appear as defined
				terms when style sheets are not applied.
				</description>
			</screen>
		</example>
		<admin href="">
			<source type="" href="cssimages/style-tg.html"/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="scripting">
		<category-ref idref=""/>
		<name></name>
		<applies-to checkpoint=""/>
		<description><p>@@discuss ECMAscript, and style sheets, point to the MWC example or "the
		company" example. examples w/diff markup languages? e.g. HTML, SVG, MathML?
		points to make/demonstrate:</p>
			<ul>
			  <li>hide/show content,</li>
			  <li>change presentation (movement and colors)</li>
			</ul></description>
		<rule></rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="acss">
		<category-ref idref=""/>
		<name>Aural Cascading Style Sheets</name>
		<applies-to checkpoint=""/>
		<description><p>CSS2's aural properties provide information to non-sighted users and
		voice-browser users much in the same way fonts provide visual information.</p>
			<p>The following properties are part of CSS2's aural cascading style
			sheets.</p>
			<ul>
			  <li>'volume' controls the volume of spoken text.</li>
			  <li>'speak' controls whether content will be spoken and, if so, whether it
			    will be spelled or spoken as words.</li>
			  <li>'pause', 'pause-before', and 'pause-after' control pauses before and
			    after content is spoken. This allows users to separate content for better
			    comprehension.</li>
			  <li>'cue', 'cue-before', and 'cue-after' specify a sound to be played before
			    and after content, which can be valuable for orientation (much like a
			    visual icon).</li>
			  <li>'play-during' controls background sounds while an element is rendered
			    (much like a background image).</li>
			  <li>'azimuth' and 'elevation' provide dimension to sound, which allows users
			    to distinguish voices, for example.</li>
			  <li>'speech-rate', 'voice-family', 'pitch', 'pitch-range', 'stress', and
			    'richness' control the quality of spoken content. By varying these
			    properties for different elements, users can fine-tune how content is
			    presented aurally.</li>
			  <li>'speak-punctuation' and 'speak-numeral' control how numbers and
			    punctuation are spoken, which has an effect on the quality of the
			    experience of aural browsing.</li>
			</ul>
			<p>Furthermore, the 'speak-header' property describes how table header
			information is to be spoken before a table cell.</p>
		</description>
		<rule></rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>This example shows how various sound qualities (including 'voice-family',
				which is something like an audio font) can let a user know that spoken content is a heading.
			</explanation>
			<sample>
				<pre> 
				H1 {     
				  voice-family: paul;     
				  stress: 20;     
				  richness: 90;     
				  cue-before: url("ping.au")     
				}</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="alt-rendering">
		<category-ref idref=""/>
		<name>Access to alternative representations of content</name>
		<applies-to checkpoint=""/>
		<description>
			<p>CSS2 lets users access alternative representations of content that is
			specified in attribute values when the following are used together:</p>
			<ul>
			  <li>attribute selectors.</li>
			  <li>the attr() function and the 'content' property'</li>
			  <li>the :before and :after pseudo-elements</li>
			</ul>
		</description>
		<rule></rule>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
				The value of the "alt" attribute for the IMG element is rendered after the image (visually, aurally, etc.).
				Note that the value of the attribute is displayed even though the image may
				not be (e.g., the user has turned off images through the user interface).
			</explanation>
			<sample>
				<pre> IMG:after { 
				    content: attr(alt) 
				 }</pre>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
	<technique id="media-types">
		<category-ref idref=""/>
		<name>Media types</name>
		<applies-to checkpoint=""/>
		<description>
			The CSS2 "media types" (used with @media rules) allow authors and users to
			design style sheets that will cause documents to render more appropriately on
			certain target devices. These style sheets can tailor content for presentation
			on braille devices, speech synthesizers, or <acronym
			title="teletypewriter">TTY</acronym> devices. Using "@media" rules can also
			reduce download times by allowing user agents to ignore inapplicable
			rules.
		</description>
		<rule></rule>
		<test></test>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
<!-- template -->
	<technique id="">
		<category-ref idref=""/>
		<name></name>
		<applies-to checkpoint=""/>
		<description></description>
		<rule></rule>
		<test></test>
		<ua-issues name="" version=""></ua-issues>
		<user-issues>
			<affects group=""></affects>
			<see-also href=""></see-also>
		</user-issues>
		<see-also href=""></see-also>
		<source type="" href=""/>
		<example>
			<explanation>
			</explanation>
			<sample>
				<code>
				</code>
			</sample>
			<screen href="" alt=""/>
		</example>
		<admin href="">
			<source type="" href=""/>
			<author uri=""></author>
			<comment></comment>
		</admin>
	</technique>
</wcag-tech>
