<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2006 U (http://www.altova.com) by Ben Caldwell (W3C) -->
<!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by Wendy Chisholm (W3C) -->
<!DOCTYPE spec SYSTEM "http://www.w3.org/WAI/GL/WCAG20/sources/xmlspec-tech.dtd">
<spec w3c-doctype="wd">
	<header>
		<title>General Techniques for WCAG 2.0</title>
		<w3c-designation>WD-WCAG20-GENERAL-20050630</w3c-designation>
		<w3c-doctype>W3C Working Draft</w3c-doctype>
		<pubdate>
			<day>30</day>
			<month>June</month>
			<year>2005</year>
		</pubdate>
		<publoc>
			<loc href="http://www.w3.org/TR/2005/WD-WCAG20-GENERAL-20050630/">http://www.w3.org/TR/2005/WD-WCAG20-GENERAL-20050630/</loc>
		</publoc>
		<latestloc>
			<loc href="http://www.w3.org/TR/WCAG20-GENERAL/">http://www.w3.org/TR/WCAG20-GENERAL/</loc>
		</latestloc>
		<prevlocs>
			<loc href="http://www.w3.org/TR/2004/WD-WCAG20-GENERAL-20041119/">http://www.w3.org/TR/2004/WD-WCAG20-GENERAL-20041119/</loc>
		</prevlocs>
		<authlist>
			<author>
				<name>John Slatin</name>
				<affiliation>University of Texas</affiliation>
			</author>
		</authlist>
		<status>
			<p>
				<emph>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <loc href="http://www.w3.org/TR/">W3C technical reports index</loc> at http://www.w3.org/TR/.</emph>
			</p>
			<p>Since this document helps to clarify the intent of success criteria and provides a bridge to technology-specific information, the <loc href="http://www.w3.org/WAI/GL/">Web Content Accessibility Guidelines Working Group</loc> (WCAG WG) encourages feedback about this Working Draft. In particular, how well does this document explain the intent of success criteria? Is it easy to find technology-specific links to HTML and CSS Techniques. Only Guidelines 1.1, 1.3, 2.1, 2.4, and 3.1 are covered in this draft. In the future, the rest of the guidelines will be incorporated as well as other technologies such as SVG and SMIL.The structure and presentation of the techniques documents will likely change as the WCAG WG determines the relationships between Guidelines, Techniques, and testing documents. As the technology-specific techniques documents and checklists progress, we expect to distinguish between techniques required for conformance versus those that are optional. Please refer to "General Techniques Issues" for a list of open issues related to this Working Draft.</p>
			<p>Please send comments by 2 August 2005 to <loc href="mailto:public-comments-wcag20@w3.org">public-comments-wcag20@w3.org</loc>. The <loc href="http://lists.w3.org/Archives/Public/public-comments-wcag20/">archives for this list</loc> are publicly available. Archives of the <loc href="http://lists.w3.org/Archives/Public/w3c-wai-gl/">WCAG WG mailing list</loc> are also publicly available.</p>
			<p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. This document will be published as a W3C Working Group Note at the time that WCAG 2.0 becomes a W3C Recommendation.</p>
			<p>This document has been produced as part of the W3C <loc href="/WAI/">Web Accessibility Initiative</loc> (WAI). The goals of the WCAG WG are discussed in the <loc href="/WAI/GL/new-charter-2000.html">Working Group charter</loc>. The WCAG WG is part of the <loc href="/WAI/Technical/Activity">WAI Technical Activity</loc>.</p>
		</status>
		<abstract>
			<p>This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" <bibref ref="WCAG20"/> (currently a W3C Working Draft). The techniques in this document can be applied to a wide range of Web technologies. Use of the illustrative techniques provided in this document may make it more likely for Web content to demonstrate conformance to WCAG 2.0 success criteria (by passing the relevant tests in the WCAG 2.0 test suite - <emph>to be developed</emph>) than if these illustrative techniques are not used.</p>
			<p>There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, it is encouraged to submit those techniques to the WCAG WG for consideration for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Deprecated examples illustrate techniques that the Working Group no longer recommends, but may be applicable in some cases.</p>
			<p>This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0.</p>
		</abstract>
		<langusage>
			<language id="en"/>
		</langusage>
		<revisiondesc>
			<p/>
		</revisiondesc>
	</header>
	<front>
		<div1 id="placeholders">
			<head/>
			<p id="UNKNOWN">UNKNOWN</p>
			<p id="media-equiv-real-time-captions">placeholder for media-equiv-real-time-captions</p>
			<p id="media-equiv-sign">placeholder for media-equiv-sign</p>
			<p id="media-equiv-extended-ad">placeholder for media-equiv-extended-ad</p>
			<p id="media-equiv-live-ad">placeholder for media-equiv-live-ad</p>
			<p id="visual-audio-contrast">placeholder for visual-audio-contrast</p>
			<p id="visual-audio-contrast-determined">placeholder for visual-audio-contrast-determined</p>
			<p id="visual-audio-contrast-contrast">placeholder for visual-audio-contrast-contrast</p>
			<p id="visual-audio-contrast-bg-patterns">placeholder for visual-audio-contrast-bg-patterns</p>
			<p id="visual-audio-contrast-dis-audio">placeholder for visual-audio-contrast-dis-audio</p>
			<p id="visual-audio-contrast-nobg">placeholder for visual-audio-contrast-nobg</p>
			<p id="visual-audio-contrast-noaudio">placeholder for visual-audio-contrast-noaudio</p>
			<p id="time-limits-blink">placeholder for time-limits-blink</p>
			<p id="time-limits-pause">placeholder for time-limits-pause</p>
			<p id="time-limits-no-exceptions">placeholder for time-limits-no-exceptions</p>
			<p id="time-limits-postponed">placeholder for time-limits-postponed</p>
			<p id="time-limits-server-timeout">placeholder for time-limits-server-timeout</p>
			<p id="flicker-does-not-violate">placeholder for flicker-does-not-violate</p>
			<p id="flicker-SPT">placeholder for flicker-SPT</p>
			<p id="navigation-mechanisms-refs">placeholder for navigation-mechanisms-refs</p>
			<p id="navigation-mechanisms-location">placeholder for navigation-mechanisms-location</p>
			<p id="minimize-error">placeholder for minimize-error</p>
			<p id="minimize-error-identified">placeholder for minimize-error-identified</p>
			<p id="minimize-error-suggestions">placeholder for minimize-error-suggestions</p>
			<p id="minimize-error-reversible">placeholder for minimize-error-reversible</p>
			<p id="minimize-error-context-help">placeholder for minimize-error-context-help</p>
			<p id="consistent-behavior">placeholder for consistent-behavior</p>
			<p id="consistent-behavior-change-of-context">placeholder for consistent-behavior-change-of-context</p>
			<p id="consistent-behavior-consistent-locations">placeholder for consistent-behavior-consistent-locations</p>
			<p id="consistent-behavior-receive-focus">placeholder for consistent-behavior-receive-focus</p>
			<p id="consistent-behavior-unpredictable-change">placeholder for consistent-behavior-unpredictable-change</p>
			<p id="consistent-behavior-consistent-functionality">placeholder for consistent-behavior-consistent-functionality</p>
			<p id="consistent-behavior-text-equivalents">placeholder for consistent-behavior-text-equivalents</p>
			<p id="consistent-behavior-no-extreme-changes-context">placeholder for consistent-behavior-no-extreme-changes-context</p>
			<p id="technology-supports-access">placeholder for technology-supports-access</p>
			<p id="technology-supports-access-level1">placeholder for technology-supports-access-level1</p>
			<p id="technology-supports-access-plugins">placeholder for technology-supports-access-plugins</p>
			<p id="technology-supports-access-rsv">placeholder for technology-supports-access-rsv</p>
			<p id="technology-supports-access-label">placeholder for technology-supports-access-label</p>
			<p id="technology-supports-access-states">placeholder for technology-supports-access-states</p>
			<p id="technology-supports-access-changes">placeholder for technology-supports-access-changes</p>
			<p id="technology-supports-access-use-access-conventions">placeholder for technology-supports-access-use-access-conventions</p>
			<p id="technology-supports-access-all-reqs">placeholder for technology-supports-access-all-reqs</p>
		</div1>
	</front>
	<body>
		<div1 role="extsrc" id="perceivable">
			<head>Principle 1</head>
			<ednote>
				<edtext>Once we have an introduction to Principle 1 in the Guidelines, that same text could appear here. Otherwise, we could write a new introduction specific to General Techniques.</edtext>
			</ednote>
			<div2 role="extsrc" id="text-equiv">
				<head>Guideline 1.1</head>
				<p>Text alternatives for non-text content can be displayed in a variety of ways by a variety of user agents. Using synthetic speech, screen readers read the text aloud, helping people who do not see well or do not see at all. Such synthetic speech may also be helpful to people who have difficulty reading written text.  Refreshable Braille displays present the text in tactile form for the benefit of people who depend on Braille. Conventional user agents such as desktop browsers include options to enhance legibility of text for people with limited  vision by increasing or decreasing font size as well as changing text and background colors.  People who cannot hear recorded  speech can read transcripts. Providing text alternatives for non-text content thus makes it possible for people with different abilities using different devices to perceive the content of Web-based resources.</p>
				<p>It is important to keep in mind that some people who depend on text alternatives do not have access to the non-text content. In other words, for many users the text alternative is not an "alternative" at all: the text alternative is the content.  For other users, the text alternative is an important supplement to the non-text content.</p>
				<p>When writing text alternatives it is important to ask yourself several questions about each piece of non-text content. For example:</p>
				<ulist>
					<item>
						<p>What is the purpose of the non-text content?</p>
					</item>
					<item>
						<p>Does it provide functionality (such as a graphical link or button)?</p>
					</item>
					<item>
						<p>Does it convey information (such as a chart, diagram, or recording of a speech)?</p>
					</item>
					<item>
						<p>Does it create a specific sensory experience, such as music without words or visual art?</p>
					</item>
					<item>
						<p> If the non-text content does not provide functionality, convey information, or create a specific sensory experience, is it important for users to be aware of it?</p>
					</item>
				</ulist>
				<p>The answers to these questions  will help you determine what the text alternative should include, and may also lead to further questions.</p>
				<div3 role="extsrc" id="text-equiv-informative">
					<head>L1 SC1</head>
					<p/>
					<div4 role="intent">
						<head>Intent of GL 1.1 L1 SC1</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="img-longdesc">Long descriptions of images</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object_description">Long description of objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="img-alt">Short text alternatives for img elements ("alt-text")</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object_shortdescription"> Short text alternatives for object elements </loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object">Text and non-text alternatives for applets and programmatic objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="embed">Embedding multimedia objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="noembed">Alt content for embed</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="embed-alt">Alt text for embed</loc>
								</p>
							</item>
						</ulist>
						<p>CSS Techniques:</p>
						<ulist>
							<item>
								<p>No related CSS Techniques</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<p>In the examples below, a single piece of non-text content is used in different contexts that require different text alternatives.</p>
						<ulist>
							<item>
								<p>A photograph of an historic event. A photograph of two world leaders shaking hands accompanies a news story about an international summit meeting. The text alternative says, "President X of Country X shakes hands with Prime Minister Y of country Y."</p>
							</item>
							<item>
								<p>The same image used in a different context with additional text alternative. The image of the president shaking hands with the prime minister appears on a Web site discussing intricate diplomatic relationships. The first text alternative reads, "President X of country X shakes hands with Prime Minister Y of country Y on January 2, 2009." An additional text alternative describes the room where the leaders are standing, the expressions on the leaders' faces, and identifies the other people in the room.</p>
								<p>The additional description might be included on the same page as the photograph or in a separate file associated with the image through a link or other standard programmatic mechanism.</p>
								<p>An audio recording.  The Web page described in the previous example includes a link to an audio recording of the leaders' press conference.  The page also links to a text transcript of the press conference.  The transcript includes a verbatim record of everything the speakers say.  It identifies who is speaking as well as noting other significant sounds that are part of the recording, such as applause, laughter, questions from the audience, and so on.</p>
								<ednote>
									<edtext>Further discussion and examples are needed for real-time silent video such as webcams.</edtext>
								</ednote>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/2000/08/nba-manual/Overview.html">Excerpts from the NBA Tape Recording Manual, Third Edition.</loc> Information on describing complex images to people who are blind.</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="text-equiv-functional">
					<head>L1 SC2</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion </head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for the Success Criterion</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="img-alt">Short text alternatives for img elements ("alt-text")</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object_shortdescription">Short text alternatives for object elements</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="imagelink">Text for images used as links</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="imagetextlinks">Image and text links side by side</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="imagesubmit-alt">text alternatives for submit buttons</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="ssim_textlinks"> Provide text links for server side image maps</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="area-alt">Provide text alternatives for selectable areas of client-side image maps</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object">Text and non-text alternatives for applets and programmatic objects</loc>
								</p>
							</item>
						</ulist>
						<p>CSS Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="css" href="char-selection">Selecting individual characters or lines</loc> - CSS may be used to create create drop caps and other effects.</p>
							</item>
							<item>
								<p>
									<loc linktype="css" href="text-as-text">Creating stylized text with CSS rather than using raster images</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion</head>
						<ulist>
							<item>
								<p>A graphical navigation link. A navigation bar includes a small image showing a house.  The image is a link to the site's home page.  The text alternative says "Home."</p>
							</item>
							<item>
								<p>A graphical icon.  A Web page provides a text transcript of a press conference.  The page also includes a graphical icon linked to an audio recording of the press conference. The text alternative reads, "Audio recording of press conference."</p>
							</item>
							<item>
								<p>A graphical button. A search form includes a button featuring the image of a magnifying glass. The text alternative for the graphic says "Search."</p>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="text-equiv-sensory">
					<head>L1 SC3</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="object_description">Long description of objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object_shortdescription"> Short text alternatives for object elements </loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="img-longdesc">Long descriptions of images</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="img-alt">Short text alternatives for img elements ("alt-text")</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="object">Text and non-text alternatives for applets and programmatic objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="embed">Embedding multimedia objects</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="noembed">Alt content for embed</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="embed-alt">Alt text for embed</loc>
								</p>
							</item>
						</ulist>
						<p>CSS Techniques:</p>
						<ulist>
							<item>
								<p>No related CSS Techniques</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/2000/08/nba-manual/Overview.html">Excerpts from the NBA Tape Recording Manual, Third Edition.</loc> Information on describing complex images to people who are blind.

										</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="text-equiv-ignored">
					<head>L1 SC4</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="imagelink">Text for images used as links</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="imagetextlinks">Image and text links side by side</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="images-as-spacers">Null alt text</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="background-image"> Background images</loc>
								</p>
							</item>
						</ulist>
						<p>CSS Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="css" href="text-indentation">Indenting text</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="css" href="empty-cells">Displaying empty table cells</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/TR/CSS21/colors.html#propdef-background-image">'background-image'</loc> - from the CSS 2.1 Candidate Recommendation - how to use CSS to specify background images.</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="text-equiv-live-media">
					<head>L1 SC5</head>
				</div3>
				<div3 role="extsrc" id="text-equiv-text-doc">
					<head>L3 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion </head>
						<note>
							<p>Placeholder for technology specific techniques</p>
						</note>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
			<div2 role="extsrc" id="media-equiv">
				<head>Guideline 1.2</head>
				<p>placeholder</p>
			</div2>
			<div2 role="extsrc" id="content-structure-separation">
				<head>Guideline 1.3</head>
				<p>Visual design often provides important cues to the structure of Web content - that is, to the parts into which it is organized and the way those parts are related to each other. However, complex layouts may be difficult to interpret for people who have learning disabilities or cognitive impairments and for older users. A page that appears well organized visually may be difficult to understand for people who are blind if screen readers are not able to identify structures and relationships within the content.</p>
				<p>In other words, visual cues alone can not give sufficient indication of the structure or organization of Web content and the relationships within it to meet the needs of users who have disabilities. This is why it is necessary to ensure that information, structure, and functionality can be separated from presentation (the way the content looks or sounds). Using structural markup correctly ensures that standards-compliant user agents can determine how the content should be presented, even when the user agent must adapt the presentation to meet the needs of people with disabilities. Conversely, <emph>incorrect</emph> use of structural markup-for example, to create visual effects that are not related to the organization and meaning of the content-may create unintended obstacles for users with disabilities.  Using Cascading Style Sheets to control  the appearance and placement of content allows designers to create visually appealing presentations that "transform gracefully" (to borrow a phrase from WCAG 1.0) when adapted to meet the needs of users with disabilities.  Designers can retain control of the presentation under different circumstances by creating alternate style sheets to support users with different needs, for example by offering a high-contrast option with enlarged fonts and icons or alternative color-schemes.  Thus structural markup and Cascading Style Sheets are two sides of one coin.</p>
				<p>It is best to approach accessibility as an integral aspect of design instead of something "added" to a finished product. Content, structure, functionality, and visual design may then be considered together as parts of a complex whole that meets the needs of the largest possible number of users.</p>
				<p>The following sections discuss general techniques for:</p>
				<ulist>
					<item>
						<p>using structural markup to identify individual parts of the content and relationships among those parts; and</p>
					</item>
					<item>
						<p>using markup to clearly define sections of the document or other resource.</p>
						<ednote>
							<edtext>is this more appropriate for 2.4?</edtext>
						</ednote>
					</item>
				</ulist>
				<p>The Technology-Specific Techniques documents provide detailed information about implementing these techniques in several W3C technologies, including (X)HTML, CSS, SVG, Scripting, and others.</p>
				<ednote>
					<edtext>The list of W3C technologies for which there are techniques documents will have to be updated to reflect the documents that are actually available or planned.</edtext>
				</ednote>
				<!-- The phrase "Structures within Web content" should be tagged as a section heading consistent with the logical hierarchy of the doc; I'm not sure at this point what tag to use.-->
				<p>
					<emph role="bold">Structures within Web content</emph>
				</p>
				<p>The list below names some (but not all) of the parts of Web documents or types of content that may be identified through structural markup. Note that some items in this list may include other structural markup.</p>
				<ulist>
					<item>
						<p>paragraphs</p>
					</item>
					<item>
						<p>lists</p>
					</item>
					<item>
						<p>forms </p>
					</item>
					<item>
						<p>data tables</p>
					</item>
					<item>
						<p>images</p>
					</item>
					<item>
						<p>mathematical expressions</p>
					</item>
					<item>
						<p>etc.</p>
					</item>
				</ulist>
				<p>The techniques described below focus primarily on enabling user agents to identify structures and relationships within Web content. This is because actual users depend on what the user agent renders; in other words, users can only perceive what user agents can identify and present.</p>
				<div3 role="extsrc" id="content-structure-separation-programmatic">
					<head>L1 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<note>
							<p>Placeholder</p>
						</note>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="content-structure-separation-emphasis">
					<head>L2 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="em">5.1 Emphasis</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples for this Success Criterion</head>
						<ulist>
							<item>
								<p>
									<emph role="bold">Example 1.</emph> A written text that creates emphasis through grammar and writing style.

    "I. Told. You. Not. To. Do. That," he said through clenched teeth.

    (In this example, the deliberate use of one-word sentence fragments creates

    an impression that the speaker is very angry, and is pausing to emphasize

    each word. Further visual styling may be unnecessary.)

    </p>
							</item>
							<item>
								<p>
									<emph role="bold">Example 2.</emph> A written text in which emphasis is indicated programmatically through

    markup and visually through typography. "I <emph>told</emph> you not to do that," he said through clenched teeth. (The use of

    italics in this example indicates that the word "told" is to

    be spoken more forcefully than the other words in the sentence. The sentence

    contains semantic markup, and the style sheet specifies that visual media

    should render the word in italics while speech output devices should slightly

    increase pitch and speech rate.)

    </p>
							</item>
							<item>
								<p>
									<emph role="bold">Example 3.</emph> An auditory-only presentation delivered over the telephone. Emphasis is

    created entirely through phonetic and lexical markup such as the W3C's Synthetic Speech Markup Language (SSML) or other data models for controlling synthetic speech. 

</p>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="content-presentation-structure-without-color">
					<head>L2 SC2</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>CSS Techniques</p>
						<ulist>
							<item>
								<p>
									<loc linktype="css" href="css-colors">7.2 Specifying color</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<ulist>
							<item>
								<p>
									<emph role="bold">Example 1.</emph> A form has both required and optional fields. Required items are marked

    with an asterisk and shown in red. The asterisk is included in the label

    text and the color is specified in the style sheet.

    </p>
							</item>
							<item>
								<p>
									<emph role="bold">Example 2.</emph> An examination. Students view an SVG image of a chemical compound and

    identify the chemical elements present based on the colors used in the

    diagram. The text alternatives associated with each element name the color

    of the element and indicate the element's position in the diagram. Students

    who cannot perceive color have the same information about the compound

    as their classmates. (This technique also satisfies Guideline 1.1 Level

    1.)

</p>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<p>Placeholder for resources section</p>
					</div4>
				</div3>
				<div3 role="extsrc" id="content-structure-separation-sequence">
					<head>L3 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="hx">Section headings</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="hx-misuse">Header misuse</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="use-css">CSS instead of presentational markup </loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="ol">Ordered lists</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="layouttables_linearize">Linear reading order of tables</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups">Link groups</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="link_structure">The link element and navigation tools</loc>
								</p>
							</item>
						</ulist>
						<ednote>
							<edtext>It would be good to have a technique about ordering DIV elements in the source document to create a linearized reading order.</edtext>
						</ednote>
						<p>CSS Techniques</p>
						<ulist>
							<item>
								<p>
									<loc linktype="css" href="layout">Creating layout, positioning, layering, and alignment</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="css" href="float">Positioning (float, position)</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="css" href="generated-content-clues">Providing additional structural information</loc>
								</p>
								<ednote>
									<edtext>CSS Technique 6.2 has important user agent issues; the :before and :after pseudoclasses are not supported by IE, so this technique should not be used to provide really important structural information.]</edtext>
								</ednote>
							</item>
							<item>
								<p>
									<loc linktype="css" href="acss">Creating auditory presentations</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="css" href="absolute-positioning">Providing structural markup for graceful degradation</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<ulist>
							<item>
								<p>
									<emph role="bold">Example 1:</emph> An online newsletter. </p>
								<p>The main content area of an online newsletter uses a layout that features two columns of text. as There is a "pullquote" in the center of the screen-- that is, a phrase taken from the article and displayed in a larger font to emphasize an important idea.  The pullquote is shown over a shaded background and there is a border around it.  Visually, the pullquote overlaps portions of both columns in the text.  The page also includes a sidebar with a list of phone numbers. The visual layout does not require that the content be read in a certain order. However, it is important that people who use screen readers or text-only displays be able to read the content in a sequence that makes sense. Thus the pullquote and the sidebar should be clearly distinguished from the text in the left and right columns so that user agents can render the content separately.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
		</div1>
		<div1 role="extsrc" id="operable">
			<head>Principle 2</head>
			<div2 role="extsrc" id="keyboard-operation">
				<head>Guideline 2.1</head>
				<p>placeholder</p>
				<div3 role="extsrc" id="keyboard-operation-keyboard-operable">
					<head>L1 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>Placeholder</p>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="keyboard-operation-all-funcs">
					<head>L2 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>Placeholder</p>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
			<div2 role="extsrc" id="time-limits">
				<head>Guideline 2.2</head>
				<p>placeholder</p>
				<div3 role="extsrc" id="time-limits-required-behaviors">
					<head>L1 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<note>
							<p>Placeholder</p>
						</note>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
			<div2 role="extsrc" id="flicker">
				<head>Guideline 2.3</head>
				<p>placeholder</p>
				<div3 role="extsrc" id="flicker-rate-and-warning">
					<head>L1 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>Placeholder</p>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
			<div2 role="extsrc" id="navigation-mechanisms">
				<head>Guideline 2.4</head>
				<p>placeholder</p>
				<div3 role="extsrc" id="navigation-mechanisms-mult-loc">
					<head>L2 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<note>
							<p>Placeholder</p>
						</note>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="navigation-mechanisms-skip">
					<head>L2 SC2</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques:</p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="hx">Section headings</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="hx-misuse">Header misuse</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="title-att">Use of the title attribute</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups">Link groups</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups_tabindex">Tabindex to skip link groups</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups_skip">Skipping link groups</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups_hide">Hide link groups</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="a-accesskey">Keyboard access</loc>
								</p>
							</item>
							<item>
								<p>
									<loc linktype="html" href="frame-title">Frame titles</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
				<div3 role="extsrc" id="navigation-mechanisms-focus">
					<head>L3 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<note>
							<p>Placeholder for description of intent</p>
						</note>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent Techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology Specific Techniques for this Success Criterion</head>
						<p>HTML Techniques></p>
						<ulist>
							<item>
								<p>
									<loc linktype="html" href="form_tabindex">Tab order in forms</loc>
								</p>
								<ednote>
									<edtext>The title (short-name) of this technique (15.7 in HTML Techniques) is misleading, since the technique also addresses use of tabindex to control tab order for links and objects as well as form controls. We might consider a more informative short-name.</edtext>
								</ednote>
							</item>
							<item>
								<p>
									<loc linktype="html" href="linkgroups_tabindex">Tabindex to  skip link groups (future)</loc>
								</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits of this Success Criterion</head>
						<note>
							<p>Placeholder for Benefits section</p>
						</note>
					</div4>
					<div4 role="examples">
						<head>Examples of this Success Criterion </head>
						<note>
							<p>Placeholder for examples</p>
						</note>
					</div4>
					<div4 role="resources">
						<head>Resources for this Success Criterion </head>
						<note>
							<p>Placeholder for Resources section</p>
						</note>
					</div4>
				</div3>
			</div2>
		</div1>
		<div1 role="extsrc" id="understandable">
			<head>Principle 3</head>
			<div2 role="extsrc" id="meaning">
				<head>Guideline 3.1</head>
				<p>placeholder</p>
				<div3 role="extsrc" id="meaning-doc-lang-id">
					<!-- in the guide template, the following would be replaced by heading,"What WCAG 2.0 requires" and then the text of the success criterion, then "Key terms and important concepts," then the definitions pulled from the WCAG 2.0 glossary -->
					<head>L1 SC1</head>
					<ednote>
						<edtext>In future Working Drafts, this section will contain links to relevant sections of General Techniques for WCAG 2.0. The information below is presented to indicate the types of material that are available.</edtext>
					</ednote>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to ensure that user agents present text and other linguistic content correctly.  Both assistive technologies and conventional user agents can render text more accurately when the language of the delivery unit is identified. Screen readers can load the correct pronunciation rules. Visual browsers can display characters and scripts correctly. Media players can show captions correctly. As a result, users with disabilities will be better able to understand the content. </p>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-specific Techniques for Guideline 3.1 L1 SC1</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>
									<loc href="lang-att_primary" linktype="html">Identifying the primary language</loc>
								</p>
							</item>
						</ulist>
						<p>CSS Techniques</p>
						<ulist>
							<item>
								<p>[List goes here; also refer people to I18N information]</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L1 SC1 Helps People with Disabilities</head>
						<p>This Success Criterion helps:</p>
						<ulist>
							<item>
								<p>people who Use screen readers or other technologies that convert text into synthetic speech;</p>
							</item>
							<item>
								<p>people with learning disabilities and cognitive limitations that make it difficult to recognize (decode) individual words and sentences;</p>
							</item>
							<item>
								<p>people with learning disabilities and cognitive limitations that make it difficult to recognize (decode) individual words and sentences;</p>
							</item>
							<item>
								<p>people who rely on captions for multimedia.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L1 SC1</head>
						<p>Example 1: A Spanish Web site</p>
						<p>The Web site of a Spanish non-governmental organization (NGO) identifies the natural language of its home page as Spanish. Screen readers automatically switch to the pronunciation dictionary for Spanish. Desktop browsers use the proper punctuation marks and other symbols.</p>
						<p>Example 2: A news video.</p>
						<p>A news video exists in English, German, and Italian versions. A user selects the Italian version and the media player automatically shows the Italian captions.</p>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#declaring"> W3c I18N Tutorial: Why and how to declare language</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#specifying"> Specifying language attribute values</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#negotiating"> Negotiating language with the server</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.ietf.org/rfc/rfc3066.txt"> RFC 3166</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.loc.gov/standards/iso639-2/langcodes.html"> ISO 639 Codes for the Representation of Language Names</loc>
								</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-other-lang-id">
					<head>L2 SC1</head>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to ensure that user agents can correctly present content written in a language that is different from the language of the delivery unit as a whole. This applies to graphical browsers as well as screen readers, Braille displays, and other voice browsers.</p>
						<p>Both assistive technologies and conventional user agents can render text more accurately if changes of language within the delivery unit are identified. Screen readers can switch to the pronunciation rules for the language of the foreign text, then switch back to the pronunciation rules of the primary language at the end of the foreign phrase or passage. Visual browsers can display characters and scripts in appropriate ways. This is especially important when one language reads from left to right and the other reads from right to left, or when the foreign phrase or passage uses a different alphabet than the primary language.  Users with disabilities who know the language of the foreign passage or phrase as well as the language of the delivery unit as a whole will be better able to understand the content.</p>
						<ednote>
							<edtext>In future Working Drafts, this section will contain links to relevant sections of General Techniques for WCAG 2.0. The information below is presented to indicate the types of material that are available.</edtext>
						</ednote>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-specific Techniques for this Success Criterion </head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/TR/WCAG20-HTML-TECHS/#lang-att_primary"> Identifying the primary language</loc>
								</p>
							</item>
						</ulist>
						<p>Advisory techniques: going beyond Guideline 3.1 L2 SC1</p>
						<ulist>
							<item>
								<p>Make foreign passages or phrases visually different from other text in the delivery unit.    </p>
							</item>
							<item>
								<p>Give the names of any languages  used in foreign passages or phrases.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L2 SC1 Helps People with Disabilities</head>
						<p>This Success Criterion helps :</p>
						<ulist>
							<item>
								<p>people who Use screen readers or other technologies that convert text into synthetic speech;</p>
							</item>
							<item>
								<p>people with learning disabilities and cognitive limitations that make it difficult to recognize (decode) individual words and sentences;</p>
							</item>
							<item>
								<p>people who rely on captions to recognize language changes in the soundtrack of multimedia content.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L2 SC1</head>
						<p>Example 1: A Web site about ancient Greek literature.</p>
						<p>A Web site discusses Friedrich Nietzche's views of Greek tragedy from Aeschylus to Sophocles. English is the primary language of the delivery unit. The delivery unit includes quotations from Nietzsche's work in German as well as passages in ancient Greek from Aeschylus' Oresteia and Sophocles' Oedipus at Colonus.</p>
						<p>Example 2: Captions for a multimedia soundtrack.</p>
						<p>A French academic Web site discusses Asian film of the 1990s. French is identified as the natural language of the delivery unit as a whole. The site includes three 20-second video clips which illustrate important points. The dialogue of the first clip is in Chinese. The dialog of the second clip is in Japanese. The actors in the third clip are speaking Hindi. In each case, the language of the captions is identified.</p>
						<p>Example 3: Text with foreign words that have become part of the delivery unit's language.</p>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<ulist>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#declaring"> W3c I18N Tutorial: Why and how to declare language</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#specifying"> Specifying language attribute values</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.w3.org/International/tutorials/tutorial-lang/#negotiating"> Negotiating language with the server</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.ietf.org/rfc/rfc3066.txt"> RFC 3166</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.loc.gov/standards/iso639-2/langcodes.html"> ISO 639 Codes for the</loc>
								</p>
							</item>
							<item>
								<p>
									<loc href="http://www.ietf.org/rfc/rfc3066.txt"> RFC 3066</loc>
								</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-mech">
					<head>L3 SC1</head>
					<div4 role="terms">
						<head>Key terms and important concepts</head>
						<glist>
							<gitem>
								<label>Text content</label>
								<def>
									<p>[WCAG definition of text goes here]</p>
								</def>
							</gitem>
							<gitem>
								<label>Mechanism</label>
								<def>
									<p>A process or technique for achieving a result</p>
								</def>
							</gitem>
							<gitem>
								<label>Available</label>
								<def>
									<p>Ready for use or service; usable</p>
									<note>
										<p>The baseline impact analysis for guidelines and SC recommended that the phrase "is available]" be used in this and a number of other SC as a way to describe a "functional outcome." I am concerned that the phrase is vague and subject to intentional misinterpretation—e.g., a mechanism is available but we didn't implement it." To aboid this, we may want to consider changing "mechanism is available" to somethinglike "mechanism has been implemented" or "is available to the user."</p>
									</note>
								</def>
							</gitem>
						</glist>
					</div4>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to ensure that definitions are available for all words in the text of the delivery unit.</p>
					</div4>
					<div4 role="techniques">
						<head>Technology-Independent techniques for Guideline 3.1 L3 SC1</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-Specific Techniques for Guideline 3.1 L3 SC1</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>Glossary</p>
							</item>
						</ulist>
						<p>Advisory techniques: going beyond Guideline 3.1 L3 SC1</p>
						<ulist>
							<item>
								<p>Provide access to a dictionary of Sign for the language of the content, to support users who are Deaf</p>
							</item>
							<item>
								<p>Provide access to a talking dictionary, to support users who might have difficulty decoding written definitions.</p>
							</item>
							<item>
								<p>Provide a voice-enabled dictionary search, so that users who have difficulty typing or spelling can speak the word whose definition they need.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L3 SC1 Helps People with Disabilities</head>
						<p>This Success Criterion helps users with limited memory or other limitations that make it difficult to understand the meaning of words.</p>
						<p>People may suffer impaired memory for many reasons, including:</p>
						<ulist>
							<item>
								<p>Accidental brain injury</p>
							</item>
							<item>
								<p>Stroke</p>
							</item>
							<item>
								<p>Disease</p>
							</item>
							<item>
								<p>Aging</p>
							</item>
						</ulist>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L3 SC1</head>
						<p>Example 1: A dictionary search form.</p>
						<p>A Web site includes a search form provided by an online dictionary service. Users enter a word or phrase, and the form returns a list of definitions from the dictionary or dictionaries that it searched.
</p>
						<p>Example 2: A medical Web site.</p>
						<p>A medical website provides information for both doctors and patients.  The site includes a set of cascading dictionaries.  A very specialized medical dictionary is first, followed by a second medical dictionary for the general public. The cascade also includes a list of abbreviations that are unique to the site, and finally there is a standard dictionary as well.
</p>
						<p>The standard dictionary at the end of the list provides definitions for most words in the text. The specialized medical dictionary yields definitions of unusual medical terms. Definitions for words that appear in more than one dictionary are listed in the order of the cascade. The meaning of abbreviations is provided by the list of abbreviations.
</p>
						<p>Example 3: A Web site about technology for people with disabilities.</p>
						<p>A Web site describes operating system features that help people who can use only one hand. The site includes the term "StickyKeys." A user asks for a definition. The only definition the dictionary cascade can find is in the Web site's own glossary.
</p>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<p>[Note: The inclusion of a product or vendor name in the list below does not constitute an endorsement by the Web Content Accessibility Guidelines Working Group or the Web Accessibility Initiative of the World Wide Web Consortium. This list is provided simply for convenience.]
</p>
						<ulist>
							<item>
								<p>[List of some online dictionaries and dictionary services will appear here.]</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-idioms">
					<head>L3 SC2</head>
					<div4 role="terms">
						<head>Key terms and important concepts</head>
						<glist>
							<gitem>
								<label>Text content</label>
								<def>
									<p>[WCAG definition of text goes here]</p>
								</def>
							</gitem>
							<gitem>
								<label>Mechanism</label>
								<def>
									<p>a process or technique for achieving a result</p>
								</def>
							</gitem>
							<gitem>
								<label>Available</label>
								<def>
									<p>Ready for use or service; usable</p>
									<note>
										<p>The baseline impact analysis for guidelines and SC recommended that the phrase "is available]" be used in this and a number of other SC as a way to describe a "functional outcome." I am concerned that the phrase is vague and subject to intentional misinterpretation—e.g., a mechanism is available but we didn't implement it." To aboid this, we may want to consider changing "mechanism is available" to somethinglike "mechanism has been implemented" or "is available to the user."</p>
									</note>
								</def>
							</gitem>
							<gitem>
								<label>Intended definition</label>
								<def>
									<p>the exact definition that users must know in order to understand the content</p>
								</def>
							</gitem>
						</glist>
					</div4>
					<div4 role="intent">
						<head>Intent of Guidline 3.1 L3 SC2 </head>
						<p>The intent of this Success Criterion is to ensure that definitions are available for:</p>
						<ulist>
							<item>
								<p>Idiomatic expressions (words or phrases specific to a region or language that do not mean what the dictionary definitions of the individual words say. For example, the English phrase "he blew his stack" means that someone became very angry.</p>
							</item>
							<item>
								<p>Jargon (words used in a particular way by people in a particular field. For example, the word StickyKeys is jargon from the field of assistive technology/accessibility.)
</p>
							</item>
							<item>
								<p>Words used in such a way that users must know exactly what definition to apply in order to understand the content correctly. For example, the word "representational" means something quite different if it occurs in a discussion of visual art as opposed to a treatise on government, but the appropriate definition can be determined from context. . By contrast, the word "text" is used in a very specific way in WCAG 2.0, so a definition is supplied in the Glossary. </p>
							</item>
						</ulist>
						<ednote>
							<edtext>Editorial note: In future Working Drafts, this section will contain links to relevant sections of General Techniques for WCAG 2.0. The information below is presented to indicate the types of material that are available.</edtext>
						</ednote>
					</div4>
					<div4 role="techniques">
						<head>Technology Independent techniques for this Success Criterion</head>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-specific Techniques for Guideline 3.1 L3 SC1</head>
						<p>Advisory techniques: going beyond Guideline 3.1 L3 SC1</p>
						<ulist>
							<item>
								<p>Use markup and visual formatting to help users recognize words that have special meaning.</p>
							</item>
							<item>
								<p>Provide a voice-enabled dictionary search, so that users who have difficulty typing or spelling can speak the word whose definition they need.
</p>
							</item>
							<item>
								<p>Provide a Sign language dictionary to help Deaf users find the necessary definitions </p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L3 SC1 Helps People with Disabilities</head>
						<p>This Success Criterion helps people whose disabilities make reading difficult or impossible. These include:</p>
						<ulist>
							<item>
								<p>People with learning disabilities or cognitive limitations that impair the ability to read</p>
							</item>
							<item>
								<p>People with low vision. Screen magnification may reduce contextual cues.</p>
							</item>
							<item>
								<p>People with memory loss</p>
							</item>
						</ulist>
						<p>This Success Criterion helps people with disabilities that affect their ability to use context to aid understanding. This includes people with certain learning disabilities and cognitive impairments. In addition, people with low vision often lose context when screen magnifiers zoom in on a small area of the screen. This Success Criterion also helps people who have difficulty recognizing words (decoding) by limiting the number of dictionary entries they must read in order to find the definition that fits the context.
</p>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L3 SC1</head>
						<p>Example 1: Text that includes a definition for a word used in an unusual way.</p>
						<p>Organize the list or "cascade" of dictionaries and other resources so that the definition search will find the intended definitions instead of displaying definitions from other sources in the "cascade."  (The "cascade" lists the dictionaries and other reference materials in the order most likely to bring up the right definition. This controls the order to follow when searching for definitions.)</p>
						<p>Example 2: Including definitions in the dictionary cascade.</p>
						<p>WCAG 2.0 uses the word "text" in a specific way. If the Glossary for WCAG 2.0 appears first in the dictionary cascade, users who want a definition of "text" will get the definition as it appears in the Glossary.  Users who request definitions for words that are not defined in the Glossary will get definitions that appear in whatever dictionary appears in the cascade.</p>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<p>[Note: The inclusion of a product or vendor name in the list below does not constitute an endorsement by the Web Content Accessibility Guidelines Working Group or the Web Accessibility Initiative of the World Wide Web Consortium. This list is provided simply for convenience, and to give users an idea of what resources may be available.]</p>
						<ulist>
							<item>
								<p>Free bilingual dictionaries for a number of languages are available from the <loc href="http://www.freedict.org">Freedict.org Web site</loc>. The dictionaries are of uneven quality and size, as noted on the site. Retrieved 9 April 2005.</p>
							</item>
							<item>
								<p>The Free Dictionaries and Search Engines site provides access to free online dictionaries and search engines in many languages. For more information, see http://www.stars21.com/index.html?lang=en&amp;pname=african @@broken link. Retrieved 9 April 2005. </p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-located">
					<head>L3 SC3</head>
					<div4 role="terms">
						<head>Key terms and important concepts</head>
						<glist>
							<gitem>
								<label>Text content</label>
								<def>
									<p>WCAG definition of text goes here]</p>
								</def>
							</gitem>
							<gitem>
								<label>Available</label>
								<def>
									<p>Ready for use or service; usable</p>
									<note>
										<p>[Note: The baseline impact analysis for guidelines and SC recommended that the phrase "is available]" be used in this and a number of other SC as a way to describe a "functional outcome." I am concerned that the phrase is vague and subject to intentional misinterpretation—e.g., a mechanism is available but we didn't implement it." To avoid this, we may want to consider changing "mechanism is available" to something like "mechanism has been implemented" or "is available to the user."]</p>
									</note>
								</def>
							</gitem>
							<gitem>
								<label>Acronym</label>
								<def>
									<p>A word made from the initial letters of a name that contains several words. For example, NOAA is a word made from the initial letters of the National Oceanic and Atmospheric Administration in the United States. SNCF is a French acronym that contains the initial letters of the Societe National des Chemins de Fer, the French national railroad.</p>
								</def>
							</gitem>
							<gitem>
								<label>Abbreviation</label>
								<def>
									<p>The shortened form of a word. For example, "Dr." is the abbreviation for the English word "doctor." "M." is the abbreviation for the French word "Monsieur."</p>
								</def>
							</gitem>
						</glist>
					</div4>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to ensure that users can access the expanded form of acronymns and abbreviations.
</p>
					</div4>
					<div4 role="techniques">
						<head>Technology-Independent techniques for Guideline 3.1 L3 SC3</head>
						<ednote>
							<edtext>In future Working Drafts, this section will contain links to relevant sections of General Techniques for WCAG 2.0. The information below is presented to indicate the types of material that are available.</edtext>
						</ednote>
						<p>There are several ways to address this Success Criterion.</p>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-Specific Techniques for Guideline 3.1 L3 SC3</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>Acronyms</p>
							</item>
							<item>
								<p>Abbreviations</p>
							</item>
						</ulist>
						<p>Advisory techniques: going beyond Guideline 3.1 L3 SC3</p>
						<ulist>
							<item>
								<p>Use visual formatting to help users recognize acronyms and abbreviations.</p>
							</item>
							<item>
								<p>Provide access to a talking dictionary, to support users who might have difficulty decoding written definitions. </p>
							</item>
							<item>
								<p>Provide a voice-enabled dictionary search, so that users who have difficulty typing or spelling can speak the word whose definition they need. </p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L3 SC3 Helps People with Disabilities</head>
						<p>This Success Criterion helps people whose disabilities make reading difficult or impossible. These include:</p>
						<ulist>
							<item>
								<p> People with learning disabilities or cognitive limitations that impair the ability to read</p>
							</item>
							<item>
								<p>People with low vision. Screen magnification may reduce contextual cues.</p>
							</item>
							<item>
								<p>People with memory loss This Success Criterion also helps people with disabilities that affect their ability to recognize words as well as their ability to use context to aid understanding. Acronyms and abbreviations may confuse these readers in different ways:</p>
								<ulist>
									<item>
										<p>Some acronyms spell common words, but are used in different ways. For example, "JAWS" is an acronym for a screen reader whose full name is "Job Access with Speech." It is also a common English word referring to the part of the mouth that holds the teeth. The acronym is used differently than the common word.</p>
									</item>
									<item>
										<p>Some acronyms sound like common words but are spelled differently. For example, the acronym for Synchronized Multimedia Integration Language, S M I L, is pronounced like the English word "smile."</p>
									</item>
									<item>
										<p>Some abbreviations do not look like normal words and cannot be pronounced according to the usual rules of the language. For example, the English word "room" is abbreviated as "rm," which does not correspond to any English word or phoneme. The user has to know that "rm" is an abbreviation for the word "room" in order to say it correctly.</p>
									</item>
									<item>
										<p>Sometimes the same abbreviation means different things in different contexts. For example, in the English sentence "Dr. Johnson lives on Boswell Dr.," the first "Dr." is an abbreviation for "Doctor" and the second instance is an abbreviation for the word "Drive" (a word that means "street"). Users must be able to understand the context in order to know what the abbreviations mean. </p>
									</item>
								</ulist>
							</item>
						</ulist>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L3 SC3</head>
						<p>Example 1: A dictionary search form. </p>
						<p>A Web site includes a search form provided by an online acronym service. Users enter an acronym and the form returns a list of possible expansions from the sources that it searched. </p>
						<p>Example 2: A medical Web site. </p>
						<p>A medical website provides information for both doctors and patients. The site includes a set of cascading dictionaries. A very specialized medical dictionary is first, followed by a second medical dictionary for the general public. The cascade also includes a list of acronyms and abbreviations that are unique to the site, and finally there is a standard dictionary as well. The standard dictionary at the end of the list provides definitions for most words in the text. The specialized medical dictionary yields definitions of unusual medical terms. Definitions for words that appear in more than one dictionary are listed in the order of the cascade. The meaning of acronyms and abbreviations is provided by the list of acronyms and abbreviations. </p>
						<p>Example 3: An abbreviation whose expansion is provided the first time the abbreviation appears in the content. </p>
						<p>The name, World Wide Web Consortium," appears as the first heading on the organization's home page. The abbreviation, "W3C," is enclosed in parentheses in the same heading.</p>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-sect-titles">
					<head>L3 SC4</head>
					<div4 role="terms">
						<head>Key terms and important concepts</head>
						<glist>
							<gitem>
								<label>Section titles</label>
								<def>
									<p>Text that identifies portions of a larger document, especially text marked as a heading.</p>
								</def>
							</gitem>
						</glist>
					</div4>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to help users understand how content is organized.  </p>
					</div4>
					<div4 role="techniques">
						<head>Technology-Independent techniques for Guideline 3.1 L3 SC4</head>
						<ednote>
							<edtext>Editorial note: In future Working Drafts, this section will contain links to relevant sections of General Techniques for WCAG 2.0. The information below is presented to indicate the types of material that are available.</edtext>
						</ednote>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-Specific Techniques for Guideline 3.1 L3 SC4</head>
						<p>HTML Techniques</p>
						<ulist>
							<item>
								<p>Section headings</p>
							</item>
							<item>
								<p>Header misuse</p>
							</item>
						</ulist>
						<p>Advisory techniques: going beyond Guideline 3.1 L3  SC4</p>
						<ulist>
							<item>
								<p>Put the most important words at the beginning of the link or section heading. </p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L3 SC4 Helps People with Disabilities</head>
						<p>This Success Criterion helps people who use screen readers by ensuring that section titles convey meaningful information when heard out of context—for example in a Table of Contents , or when jumping from heading to heading within a page.</p>
						<p>This Success Criterion may also help users with low vision who may see only a few words at a time.
</p>
						<p>Users with reading disabilities benefit when section titles make it possible to predict what each section contains.
</p>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L3 SC4</head>
						<p>Example 1: A news site.</p>
						<p>The home page of a news site lists the headlines for the top stories of the hour. Under each heading are the first 35 words of the story and a link to the full article. Each headline gives a clear idea of the article's subject. 
</p>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<ulist>
							<item>
								<p>Theofanos, M.F., and Redish, J. (2003). Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers. Interactions, Volume X, Issue 6, November-December 2003, pages 38-51,  http://doi.acm.org/10.1145/947226.947227. Retrieved 3 May 2005 from http://redish.net/content/papers/interactions.html.
</p>
							</item>
						</ulist>
					</div4>
				</div3>
				<div3 role="extsrc" id="meaning-supplements">
					<head>L3 SC5</head>
					<div4 role="terms">
						<head>Key terms and important concepts</head>
						<glist>
							<gitem>
								<label>Supplement</label>
								<def>
									<p>A version of content which some users may choose instead of or in addition to another version of the content. Supplements may use different media. For example, there may be versions in text, graphics, and audio.</p>
								</def>
							</gitem>
							<gitem>
								<label>Intended audience</label>
								<def>
									<p>The people for whom the Web site, application, or other resource has been created.  The audience may be large or small, local or global.  The intended audience may be deeply knowledgeable about the topic, or completely uninformed. </p>
								</def>
							</gitem>
							<gitem>
								<label>Education level</label>
								<def>
									<p>Years of school completed, or highest degree achieved.</p>
								</def>
							</gitem>
							<gitem>
								<label>Upper secondary education level</label>
								<def>
									<p>Typically begins at ages 15 or 16 and lasts for approximately 3 years. The educational programmes included at this level typically require the completion of some 9 years of full-time education (since the beginning of level 1 [primary education]) for admission or a combination of education and vocational or technical experience and with as minimum entrance requirements the completion of level 2[lower secondary education, such as middle school or junior high school in the US] or demonstrable ability to handle programmes at this level. (Source: International Standard Classification of Education 1997.  UNESCO. Retrieved 22 June 2005 from <loc href="http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm">http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm</loc>.)</p>
								</def>
							</gitem>
							<gitem>
								<label>Primary education level</label>
								<def>
									<p>Usually begins at age 5, 6, or 7 and continues for six years of full-time schooling. Source: International Standard Classification of Education 1997.  UNESCO. Retrieved 22 June 2005 from <loc href="http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm">http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm</loc>.)</p>
								</def>
							</gitem>
							<gitem>
								<label>Readability formula</label>
								<def>
									<p>Readability formulas predict whether text will be easy or difficult to read. Readability formulas assume that longer sentences are more complex than shorter ones, and therefore harder to read. Readability formulas also assume that shorter words are easier to read than longer ones.</p>
									<p>In some languages, readability formulas measure sentence-length by counting characters instead of words. Readability formulas for languages that use multiple scripts within a single document (such as Japanese katakana and hiragana) may also consider the number of different scripts used in the text as a measure of difficulty.</p>
									<p>Results of readability tests are often expressed in terms of the education level needed to recognize words and sentences in the text. Thus readability formulas can help authors write content that matches the education level or reading ability of the intended audience.</p>
								</def>
							</gitem>
							<gitem>
								<label>Delivery unit</label>
								<def>
									<note>
										<p>[Note: add plain-language paraphrase approved at 2005-04-28 call.]</p>
									</note>
									<p>A set of material transferred between two cooperating web programs as the response to a single HTTP request. The transfer might, for example, be between an origin server and a user agent.</p>
								</def>
							</gitem>
						</glist>
					</div4>
					<div4 role="intent">
						<head>Intent of this Success Criterion</head>
						<p>The intent of this Success Criterion is to ensure that supplementary aids are provided for complex text.  It defines a threshold that establishes when simpler alternatives are required. It also defines the required reading level for one type of alternative, the text summary.
</p>
						<p>The threshold for deciding when text is complex enough to require supplemental versions is set at the upper secondary education level as defined by the International Standard Classification of Education (UNESCO, 1997). . In the United States and Japan, for example, as well as other countries, this corresponds to the 10th grade.
</p>
						<p>The readability requirement for text summaries is set no higher than primary education because many people with learning disabilities read at or below this level.
</p>
						<p>Here are some additional points to consider:
</p>
						<ulist>
							<item>
								<p>There are people with disabilities at every education level. They include people with learning disabilities and cognitive impairments as well as people with physical and sensory limitations.
</p>
							</item>
							<item>
								<p>Research shows that most readers have difficulty understanding text at or above the tenth grade level. </p>
							</item>
							<item>
								<p>According to Canada's Northwest Territories Literacy Council, text that requires reading ability at or above the tenth grade level is appropriate only when presenting specialized information to an audience that already knows the topic.
</p>
							</item>
							<item>
								<p>Education levels and compulsory education requirements vary a great deal from country to country. </p>
							</item>
							<item>
								<p>Reading ability also varies from country to country, and sometimes from region to region within the same country.  </p>
							</item>
							<item>
								<p>Reading ability does not always match education level. For example, 2004 data show that over 85% of adults in the United States have finished high school (upper secondary). But the International Adult Literacy Survey (1994-98) found the reading ability of most adults in the US was closer to the end of lower secondary (eighth grade). And the US ranked last among 19 high-performing economies for the reading ability of adults who had not completed high school (upper secondary).</p>
							</item>
							<item>
								<p>It has been estimated that 15-20 per cent of adults have learning disabilities</p>
							</item>
							<item>
								<p>As many as 80 per cent of adults with low literacy skills are likely to have learning disabilities.</p>
							</item>
							<item>
								<p>Researchers in New Zealand found that approximately 80% of adults with self-reported reading/learning disabilities had literacy levels below the minimum level required for meeting the complex demands of daily life in information-based societies.  (Chapman, J.W., Tunmer, W.E., and Allen, R. (2003). New Zealand IALS results. Dyslexia 9.2 (May 2003): 75-98. Abstract retrieved 29 April 2005 from http://www.ingentaconnect.com/content/jws/dys/2003/00000009/00000002/art00002)</p>
							</item>
						</ulist>
						<p>This Success Criterion leaves authors free to present complex ideas and information while also meeting the needs of people with reading disabilities.
</p>
					</div4>
					<div4 role="techniques">
						<head>Technology-Independent techniques for Guideline 3.1 L3 SC5</head>
						<ulist>
							<item>
								<p>Measure the readability of the text.</p>
							</item>
							<item>
								<p>If the results indicate that the text requires an education level of 10 years or more, do one of the following:</p>
								<ulist>
									<item>
										<p>Make the text easier to read.</p>
									</item>
									<item>
										<p>Provide one or more supplementary versions</p>
									</item>
								</ulist>
							</item>
						</ulist>
					</div4>
					<div4 role="tech-specific">
						<head>Technology-Specific Techniques for Guideline 3.1 L3 SC5</head>
						<p>[List techniques for linking to spoken versions and/or grouping text and accompanying illustration in a DIV, etc.]</p>
						<p>Advisory techniques: going beyond Guideline 3.1 L3 SC5</p>
						<ulist>
							<item>
								<p>Text on navigational and landing pages requires reading ability no higher than primary education level</p>
							</item>
							<item>
								<p>Text on interior pages requires reading ability below upper secondary education level.</p>
							</item>
							<item>
								<p>Signing versions are available for information, ideas, and processes that must be understood in order to use the content.</p>
							</item>
						</ulist>
					</div4>
					<div4 role="benefits">
						<head>Benefits: How Guideline 3.1 L3 SC5 Helps People with Disabilities</head>
						<p>This Success Criterion benefits people with reading disabilities who can understand complex ideas and processes presented in highly readable text or by other means, such as graphics illustrating relationships and processes or through the spoken word.</p>
						<p>Reading disabilities such as dyslexia affect the ability to recognize individual words.  Decoding must be automatic in order for people to read fluently.  The act of decoding text word by word consumes much of the mental energy that most people are able to use for understanding what they read.</p>
						<p>People with reading disabilities have become successful scientists, engineers, artists, actors, attorneys, surgeons, and skilled professionals in many other fields. But they are often at a significant disadvantage when ideas and information they need are available only in complex textual presentations. This Success Criterion does not limit the complexity of textual presentation. Instead, it asks authors and other content providers to present ideas and information more than one way in addition to the textual presentation. </p>
					</div4>
					<div4 role="examples">
						<head>Examples of Guideline 3.1 L3 SC5</head>
						<p>Example 1: A scientific journal including readable summaries of complex research articles</p>
						<p>A scientific journal includes articles written in highly technical language aimed at specialists in the field. The journal's Table of Contents page includes a plain-language summary of each article. The summaries are intended for a general audience with eight years of school. The metadata for the journal uses the Dublin Core specification to identify the education level of the articles' intended audience as "advanced" and the education level of the intended audience for the summaries as "eight years of school." </p>
						<p>Example 2: Medical information for members of the public
</p>
						<p>A medical school operates a Web site that explains recent medical and scientific discoveries. The articles on the site are written for people who are not doctors. Each article uses the Dublin Core metadata specification to identify the education level of the intended audience as having completed 8 years of school and includes the Flesch Reading Ease score for the article. A link on each page displays the education level and other metadata. No supplementary versions are required because adults who have not begun upper secondary education can read the articles.</p>
						<p>Example 3: An e-learning application.</p>
						<p>An online course about Spanish cultural history includes a unit on Moorish architecture. The unit includes text written for students with different reading abilities.  Photographs and drawings of buildings illustrate architectural concepts and styles. Graphic organizers are used to illustrate complex relationships, and an audio version using synthetic speech is available. The metadata for each version describes the academic level of the content and includes a readability score based on formulas developed for Spanish-language text. The learning application uses this metadata and metadata about the students to provide versions of instructional content that match the needs of individual students.</p>
						<p>Example 3: A moderately difficult description of a complex and unfamiliar natural event.</p>
						<p>In a dazzling and dramatic portrait painted by the Sun, the long thin shadows of Saturn's rings sweep across the planet's northern latitudes. Within the shadows, bright bands represent areas where the ring material is less dense, while dark strips and wave patterns reveal areas of denser material.
</p>
						<p>The shadow darkens sharply near upper right, corresponding to the boundary of the thin C ring with the denser B ring. A wide-field, natural color view of these shadows can be seen here.</p>
						<p>The globe of Saturn's moon Mimas (398 kilometers, or 247 miles across) has wandered into view near the bottom of the frame. A few of the large craters on this small moon are visible.
</p>
						<p>Note: The description in Example 1 is taken from NASA – Sun-Striped Saturn, at http://www.nasa.gov/mission_pages/cassini/multimedia/pia06574.html.   Retrieved 2005-03-08.
</p>
						<p>Note: This description received a Flesch Reading Ease score of 57.9 and a Flesch-Kinkaid Grade Level of 9.9. This result means that people in the United States who have finished almost 10 years of school should be able to recognize the words and sentences.
</p>
						<p>Example 4: Description of a complex and unfamiliar natural event, rewritten to improve readability
</p>
						<p>The long thin shadows of Saturn's rings sweep across the planet's northern regions. Bright bands within the shadows show areas where the ring material is less dense. Dark strips and wave patterns show denser areas.
</p>
						<p>The shadow darkens sharply near the top right.  This is where the thin C ring meets the denser B ring. This shows a wide-field, natural color view of these shadows.
</p>
						<p>The globe of Saturn's moon Mimas (398 kilometers, or 247 miles across) appears near the bottom of the frame. A few of the large craters on this small moon are visible.
</p>
						<p>[Note: This edited version of the description was rated at 72.1 on the Flesch Reading Ease scale, meaning that people beginning their sixth year of school should be able to read the description. The changes include: 
</p>
						<ulist>
							<item>
								<p>Introductory phrases were deleted or moved to the end of the sentence.</p>
							</item>
							<item>
								<p>Some sentences were shortened.</p>
							</item>
							<item>
								<p>Some longer sentences were divided into two sentences.
</p>
							</item>
							<item>
								<p>Some longer words such as "latitudes" and "reveal" were replaced by shorter words with similar meanings ("regions," "show"). ]</p>
							</item>
						</ulist>
					</div4>
					<div4 role="resources">
						<head>Related resources</head>
						<ulist>
							<item>
								<p>· A Plain Language Audit Tool provides a checklist for determining whether documents can be edited for clarity and "plain language." The checklist includes a readability assessment. Available from the Northwest Territories (Canada) Literacy Council at http://www.nwt.literacy.ca/plainlng/auditool/cover.htm.</p>
							</item>
							<item>
								<p>The Plain Language Network Web site provides many useful resources to help writers produce documents that communicate clearly in a variety of cultural and rhetorical contexts.  See http://www.plainlanguagenetwork.org/.</p>
							</item>
							<item>
								<p>The US government's plain language Web site at http://www.plainlanguage.gov provides general information about plain language as well as information about use of plain language in US government documents, including legal requirements</p>
							</item>
							<item>
								<p>The Plain English Campaign Web site provides useful information and guidance for authors writing in English.  Available at http://www.plainenglish.co.uk/.</p>
							</item>
							<item>
								<p>The Swedish government's Plain Language site provides similar information about plain language efforts in Sweden.  Available at http://www.regeringen.se/sb/d/4409.</p>
							</item>
							<item>
								<p>Hall, T., and Strangman, N. CAST: Graphic organizers. Retrieved 5 April 2005 from http://www.cast.org/publications/ncac/ncac_go.html#startcontent. This article illustrates several different kinds of graphic organizers, explains how each type may be useful, and summarizes research findings that graphic organizers support learning, especially among students with learning disabilities.</p>
							</item>
						</ulist>
					</div4>
				</div3>
			</div2>
		</div1>
	</body>
	<back>
		<inform-div1 id="references">
			<head>References</head>
			<ednote>
				<edtext>Add references section and other appendix information as needed.</edtext>
			</ednote>
			<blist>
				<bibl id="WCAG20" key="WCAG20">"<titleref href="http://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0</titleref>", B. Caldwell, W. Chisholm, J. White, and G. Vanderheiden, eds.</bibl>
			</blist>
		</inform-div1>
	</back>
</spec>
