You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2642 lines
100 KiB
2642 lines
100 KiB
<?xml version="1.0"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<meta name="generator" content="HTML Tidy, see www.w3.org" />
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
|
<title>Techniques for Web Content Accessibility Guidelines 1.0</title>
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/StyleSheets/TR/W3C-NOTE" />
|
|
<link rel="STYLESHEET" href="style/default.css" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class="navbar"><map id="navbar-top" name="navbar-top"
|
|
title="Navigation Bar">
|
|
<p>[<a href="#toc">contents</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/">Core Techniques</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/">HTML Techniques</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/">CSS Techniques</a>] </p>
|
|
|
|
<hr class="navbar" title="Navigation area separator" />
|
|
</map></div>
|
|
|
|
<div class="head">
|
|
<p><a href="http://www.w3.org/" title="Go to W3C Home Page"><img height="48"
|
|
width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p>
|
|
|
|
<h1 class="notoc">Techniques for Web Content Accessibility Guidelines 1.0</h1>
|
|
|
|
<h2 class="notoc">W3C Note 6 November 2000</h2>
|
|
|
|
<dl>
|
|
<dt>This version:</dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106/">
|
|
http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106/</a></dd>
|
|
|
|
<dd>(<a href="wcag10-tech.txt">plain text</a>, <a href="wcag10-tech.ps">
|
|
PostScript</a>, <a href="wcag10-tech.pdf">PDF</a>, <a href="wcag10-tech.tgz">
|
|
gzip tar file of HTML</a>, <a href="wcag10-tech.zip">zip archive of
|
|
HTML</a>)</dd>
|
|
|
|
<dt>Latest version:</dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/WCAG10-TECHS/">
|
|
http://www.w3.org/TR/WCAG10-TECHS/</a> <!--
|
|
<DT>Latest public version:
|
|
<DD><A HREF="http://www.w3.org/TR/WCAG10-TECHS/">http://www.w3.org/TR/WCAG10-TECHS/</A>
|
|
--></dd>
|
|
|
|
<dt>Previous version:</dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20000920/">
|
|
http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20000920/</a></dd>
|
|
|
|
<dt>Editors:</dt>
|
|
|
|
<dd>Wendy Chisholm, <a href="http://www.w3.org/">W3C</a>;<br />
|
|
Gregg Vanderheiden, <a href="http://www.tracecenter.org/">Trace R & D
|
|
Center</a>, University of Wisconsin -- Madison;<br />
|
|
Ian Jacobs, <a href="http://www.w3.org/">W3C</a></dd>
|
|
</dl>
|
|
|
|
<p class="copyright"><a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
|
|
©1999 - 2000 <a href="http://www.w3.org/"><abbr
|
|
title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a
|
|
href="http://www.lcs.mit.edu/"><abbr
|
|
title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
|
|
href="http://www.inria.fr/"><abbr lang="fr"
|
|
title="Institut National de Recherche en Informatique et Automatique">
|
|
INRIA</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights
|
|
Reserved. W3C <a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
|
|
liability</a>, <a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">
|
|
trademark</a>, <a
|
|
href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document
|
|
use</a> and <a
|
|
href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software
|
|
licensing</a> rules apply.</p>
|
|
</div>
|
|
|
|
<hr />
|
|
<h2 class="nonb"><a id="Abstract" name="Abstract">Abstract</a></h2>
|
|
|
|
<p>This document is the gateway to a series of related documents that provide
|
|
techniques for satisfying the requirements defined in "Web Content
|
|
Accessibility Guidelines 1.0" <cite><a href="#ref-WCAG10"
|
|
title="Link to reference WCAG10">[WCAG10]</a></cite>. This series includes:</p>
|
|
|
|
<ol>
|
|
<li><cite>"Techniques for Web Content Accessibility Guidelines 1.0"</cite>, the
|
|
current document, which is the gateway to the other documents.</li>
|
|
|
|
<li><cite>"Core Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-CORE-TECHNIQUES"
|
|
title="Link to reference WCAG10-CORE-TECHNIQUES">[WCAG10-CORE-TECHNIQUES]</a></cite>),
|
|
which discusses the accessibility themes and general techniques that apply
|
|
across technologies (e.g., <a id="validation" name="validation">validation</a>,
|
|
testing, etc.).</li>
|
|
|
|
<li><cite>"HTML Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-HTML-TECHNIQUES"
|
|
title="Link to reference WCAG10-HTML-TECHNIQUES">[WCAG10-HTML-TECHNIQUES]</a></cite>),
|
|
which provides examples and strategies for authoring accessible Hypertext
|
|
Markup Language (<acronym>HTML</acronym>) content.</li>
|
|
|
|
<li><cite>"CSS Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-CSS-TECHNIQUES"
|
|
title="Link to reference WCAG10-CSS-TECHNIQUES">[WCAG10-CSS-TECHNIQUES]</a></cite>),
|
|
which provides examples and strategies to help authors write Cascading Style
|
|
Sheets (<acronym title="Cascading Style Sheets">CSS</acronym>) as part of
|
|
accessible content design.</li>
|
|
</ol>
|
|
|
|
<h2 class="nonb"><a id="Status" name="Status">Status of this document</a></h2>
|
|
|
|
<p>This version has been published to correct some broken links in the previous
|
|
version.</p>
|
|
|
|
<p>The 6 November 2000 version of this document is a Note in a series of Notes
|
|
produced and endorsed by the <a href="http://www.w3.org/WAI/GL/">Web Content
|
|
Accessibility Guidelines Working Group</a>. This Note has not been reviewed or
|
|
endorsed by W3C Members. The series of documents supersedes the <a
|
|
href="http://www.w3.org/TR/1999/WAI-WEBCONTENT-TECHS-19990505/">5 May 1999 W3C
|
|
Note "Techniques for Web Content Accessibility Guidelines 1.0"</a>. That single
|
|
document has been divided into technology-specific documents that may evolve
|
|
independently. Smaller technology-specific documents also allow authors to
|
|
focus on a particular technology.</p>
|
|
|
|
<p>While the "Web Content Accessibility Guidelines 1.0" Recommendation <cite><a
|
|
href="#ref-WCAG10" title="Link to reference WCAG10">[WCAG10]</a></cite> is a
|
|
stable document, this series of companion documents is expected to evolve as
|
|
technologies change and content developers discover more effective techniques
|
|
for designing accessible Web sites and pages. In the near future, the Working
|
|
Group intends to incorporate techniques for the Synchronized Multimedia
|
|
Integration Language (<acronym
|
|
title="Synchronized Multimedia Integration Language">SMIL</acronym>) <cite><a
|
|
href="#ref-SMIL" title="Link to reference SMIL">[SMIL]</a></cite> described in
|
|
"Accessibility Features of SMIL" (<cite><a href="#ref-SMIL-ACCESS"
|
|
title="Link to reference SMIL-ACCESS">[SMIL-ACCESS]</a></cite>) and techniques
|
|
for Scalable Vector Graphics (<acronym
|
|
title="Scalable Vector Graphics">SVG</acronym>) <cite><a href="#ref-SVG"
|
|
title="Link to reference SVG">[SVG]</a></cite> described in "Accessibility
|
|
Features of SVG" (<cite><a href="#ref-SVG-ACCESS"
|
|
title="Link to reference SVG-ACCESS">[SVG-ACCESS]</a></cite>). The Working
|
|
Group also intends to incorporate techniques for non-W3C technologies such as
|
|
ECMAScript, <acronym title="Portable Document Format">PDF</acronym> and
|
|
Flash.</p>
|
|
|
|
<p>The <a href="http://www.w3.org/WAI/GL/wai-gl-techniques-changes.html">
|
|
history of changes to the series of documents</a> as well as the <a
|
|
href="http://www.w3.org/WAI/GL/wai-gl-tech-issues.html">list of open and closed
|
|
issues</a> are available. Readers are encouraged to comment on the document and
|
|
propose resolutions to current issues. Please send detailed comments on this
|
|
document to the Working Group at <a href="mailto:w3c-wai-gl@w3.org">
|
|
w3c-wai-gl@w3.org</a>; <a
|
|
href="http://lists.w3.org/Archives/Public/w3c-wai-gl/">public archives</a> are
|
|
available.</p>
|
|
|
|
<p>The English version of this document is the only normative version. However,
|
|
for translations in other languages see <a
|
|
href="http://www.w3.org/WAI/GL/WAI-WEBCONTENT-TRANSLATIONS">
|
|
"http://www.w3.org/WAI/GL/WAI-WEBCONTENT-TRANSLATIONS"</a>.</p>
|
|
|
|
<p>The list of known errors in this document is available at <a
|
|
href="http://www.w3.org/WAI/GL/WAI-WEBCONTENT-ERRATA">"Errata in Web Content
|
|
Accessibility Guidelines</a>." Please report errors in this document to <a
|
|
href="mailto:wai-wcag-editor@w3.org">wai-wcag-editor@w3.org</a>.</p>
|
|
|
|
<p>The <a href="http://www.w3.org/WAI/">Web Accessibility Initiative (<acronym
|
|
title="Web Accessibility Initiative">WAI</acronym>)</a> of the World Wide Web
|
|
Consortium (<acronym title="Web Accessibility Initiative">W3C</acronym>) makes
|
|
available a variety of <a href="http://www.w3.org/WAI/#Resources">resources on
|
|
Web accessibility</a>. WAI Accessibility Guidelines are produced as part of the
|
|
<a href="http://www.w3.org/WAI/Technical/Activity">WAI Technical Activity</a>.
|
|
The goals of the WCAG WG are described in <a
|
|
href="http://www.w3.org/WAI/GL/new-charter-2000.html">the charter</a>.</p>
|
|
|
|
<p>A list of <a href="http://www.w3.org/TR/">current W3C Recommendations and
|
|
other technical documents</a> is available.</p>
|
|
|
|
<!--NewPage--><!-- this is for html2ps -->
|
|
<div class="toc">
|
|
<h2 class="notoc"><a id="toc" name="toc">Table of Contents</a></h2>
|
|
|
|
<ul class="toc">
|
|
<li class="tocline2"><a id="toc-Abstract" href="#Abstract" name="toc-Abstract"
|
|
class="tocxref">Abstract</a></li>
|
|
|
|
<li class="tocline2"><a id="toc-Status" href="#Status" name="toc-Status"
|
|
class="tocxref">Status of this document</a></li>
|
|
|
|
<li class="tocline2"><a id="toc-organization" href="#organization"
|
|
name="toc-organization" class="tocxref">1 How this Document is Organized</a>
|
|
|
|
<ul class="toc">
|
|
<li class="tocline3"><a id="toc-priorities" href="#priorities"
|
|
name="toc-priorities" class="tocxref">1.1 Priorities</a></li>
|
|
</ul>
|
|
</li>
|
|
|
|
<li class="tocline2"><a id="toc-Techniques" href="#Techniques"
|
|
name="toc-Techniques" class="tocxref">2 Techniques for Web Content
|
|
Accessibility Guidelines</a>
|
|
|
|
<ul class="toc">
|
|
<li class="tocline3"><a id="toc-gl-provide-equivalents"
|
|
href="#gl-provide-equivalents" name="toc-gl-provide-equivalents"
|
|
class="tocxref">1. Provide equivalent alternatives to auditory and visual
|
|
content.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-color" href="#gl-color" name="toc-gl-color"
|
|
class="tocxref">2. Don't rely on color alone.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-structure-presentation"
|
|
href="#gl-structure-presentation" name="toc-gl-structure-presentation"
|
|
class="tocxref">3. Use markup and style sheets and do so properly.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-abbreviated-and-foreign"
|
|
href="#gl-abbreviated-and-foreign" name="toc-gl-abbreviated-and-foreign"
|
|
class="tocxref">4. Clarify natural language usage</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-table-markup" href="#gl-table-markup"
|
|
name="toc-gl-table-markup" class="tocxref">5. Create tables that transform
|
|
gracefully.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-new-technologies"
|
|
href="#gl-new-technologies" name="toc-gl-new-technologies" class="tocxref">6.
|
|
Ensure that pages featuring new technologies transform gracefully.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-movement" href="#gl-movement"
|
|
name="toc-gl-movement" class="tocxref">7. Ensure user control of time-sensitive
|
|
content changes.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-own-interface" href="#gl-own-interface"
|
|
name="toc-gl-own-interface" class="tocxref">8. Ensure direct accessibility of
|
|
embedded user interfaces.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-device-independence"
|
|
href="#gl-device-independence" name="toc-gl-device-independence"
|
|
class="tocxref">9. Design for device-independence.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-interim-accessibility"
|
|
href="#gl-interim-accessibility" name="toc-gl-interim-accessibility"
|
|
class="tocxref">10. Use interim solutions.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-use-w3c" href="#gl-use-w3c"
|
|
name="toc-gl-use-w3c" class="tocxref">11. Use W3C technologies and
|
|
guidelines.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-complex-elements"
|
|
href="#gl-complex-elements" name="toc-gl-complex-elements" class="tocxref">12.
|
|
Provide context and orientation information.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-facilitate-navigation"
|
|
href="#gl-facilitate-navigation" name="toc-gl-facilitate-navigation"
|
|
class="tocxref">13. Provide clear navigation mechanisms.</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-gl-facilitate-comprehension"
|
|
href="#gl-facilitate-comprehension" name="toc-gl-facilitate-comprehension"
|
|
class="tocxref">14. Ensure that documents are clear and simple.</a></li>
|
|
</ul>
|
|
</li>
|
|
|
|
<li class="tocline2"><a id="toc-glossary" href="#glossary" name="toc-glossary"
|
|
class="tocxref">3 Glossary</a></li>
|
|
|
|
<li class="tocline2"><a id="toc-References" href="#References"
|
|
name="toc-References" class="tocxref">4 References</a></li>
|
|
|
|
<li class="tocline2"><a id="toc-Resources" href="#Resources"
|
|
name="toc-Resources" class="tocxref">5 Resources</a>
|
|
|
|
<ul class="toc">
|
|
<li class="tocline3"><a id="toc-OtherGuidelines" href="#OtherGuidelines"
|
|
name="toc-OtherGuidelines" class="tocxref">5.1 Other Guidelines</a></li>
|
|
|
|
<li class="tocline3"><a id="toc-ToolResources" href="#ToolResources"
|
|
name="toc-ToolResources" class="tocxref">5.2 User agents and other
|
|
tools</a></li>
|
|
</ul>
|
|
</li>
|
|
|
|
<li class="tocline2"><a id="toc-Acknowledgments" href="#Acknowledgments"
|
|
name="toc-Acknowledgments" class="tocxref">6 Acknowledgments</a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="noprint">
|
|
<hr title="Separator from Introduction" />
|
|
</div>
|
|
|
|
<!--NewPage--><!-- this is for html2ps -->
|
|
<h2>1 <a id="organization" name="organization">How this Document is
|
|
Organized</a></h2>
|
|
|
|
<p>Section 2 of this document reproduces the guidelines and checkpoints of the
|
|
"Web Content Accessibility Guidelines 1.0" <cite><a href="#ref-WCAG10"
|
|
title="Link to reference WCAG10">[WCAG10]</a></cite>. Each guideline
|
|
includes:</p>
|
|
|
|
<ul>
|
|
<li>The guideline number.</li>
|
|
|
|
<li>The statement of the guideline.</li>
|
|
|
|
<li>A list of checkpoint definitions. Checkpoints are ordered according to
|
|
their <a href="#priorities">priority</a>, e.g., Priority 1 before Priority
|
|
2.</li>
|
|
</ul>
|
|
|
|
<p>Each checkpoint definition includes:</p>
|
|
|
|
<ul>
|
|
<li>The checkpoint number.</li>
|
|
|
|
<li>The statement of the checkpoint.</li>
|
|
|
|
<li>The priority of the checkpoint.</li>
|
|
|
|
<li>A link back to the definition of the checkpoint in "Web Content
|
|
Accessibility Guidelines 1.0" <cite><a href="#ref-WCAG10"
|
|
title="Link to reference WCAG10">[WCAG10]</a></cite>. Definitions may also
|
|
include informative notes, examples, cross references, and commentary to help
|
|
readers understand the scope of the checkpoint.</li>
|
|
</ul>
|
|
|
|
<p>Each checkpoint is followed by one or more links to techniques in the
|
|
following documents:</p>
|
|
|
|
<ul>
|
|
<li><cite>"Core Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-CORE-TECHNIQUES"
|
|
title="Link to reference WCAG10-CORE-TECHNIQUES">[WCAG10-CORE-TECHNIQUES]</a></cite>),
|
|
which discusses the accessibility themes and general techniques that apply
|
|
across technologies.</li>
|
|
|
|
<li><cite>"HTML Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-HTML-TECHNIQUES"
|
|
title="Link to reference WCAG10-HTML-TECHNIQUES">[WCAG10-HTML-TECHNIQUES]</a></cite>),
|
|
which provides examples and strategies for authoring accessible Hypertext
|
|
Markup Language (<acronym>HTML</acronym>) content.</li>
|
|
|
|
<li><cite>"CSS Techniques for Web Content Accessibility Guidelines 1.0"</cite>
|
|
(<cite><a href="#ref-WCAG10-CSS-TECHNIQUES"
|
|
title="Link to reference WCAG10-CSS-TECHNIQUES">[WCAG10-CSS-TECHNIQUES]</a></cite>),
|
|
which provides examples and strategies to help authors write Cascading Style
|
|
Sheets (<acronym title="Cascading Style Sheets">CSS</acronym>) as part of
|
|
accessible content design.</li>
|
|
</ul>
|
|
|
|
<h3>1.1 <a id="priorities" name="priorities">Priorities</a></h3>
|
|
|
|
<p>Each checkpoint has a priority level assigned by the Working Group based on
|
|
the checkpoint's impact on accessibility.</p>
|
|
|
|
<dl>
|
|
<dt><a id="wc-priority-1" name="wc-priority-1">[Priority 1]</a></dt>
|
|
|
|
<dd>A Web content developer <strong>must</strong> satisfy this checkpoint.
|
|
Otherwise, one or more groups will find it impossible to access information in
|
|
the document. Satisfying this checkpoint is a basic requirement for some groups
|
|
to be able to use Web documents.</dd>
|
|
|
|
<dt><a id="wc-priority-2" name="wc-priority-2">[Priority 2]</a></dt>
|
|
|
|
<dd>A Web content developer <strong>should</strong> satisfy this checkpoint.
|
|
Otherwise, one or more groups will find it difficult to access information in
|
|
the document. Satisfying this checkpoint will remove significant barriers to
|
|
accessing Web documents.</dd>
|
|
|
|
<dt><a id="wc-priority-3" name="wc-priority-3">[Priority 3]</a></dt>
|
|
|
|
<dd>A Web content developer <strong>may</strong> address this checkpoint.
|
|
Otherwise, one or more groups will find it somewhat difficult to access
|
|
information in the document. Satisfying this checkpoint will improve access to
|
|
Web documents.</dd>
|
|
</dl>
|
|
|
|
<p>Some checkpoints specify a priority level that may change under certain
|
|
(indicated) conditions. <!--NewPage--><!-- this is for html2ps --></p>
|
|
|
|
<div class="noprint"></div>
|
|
|
|
<h2>2 <a id="Techniques" name="Techniques">Techniques for Web Content
|
|
Accessibility Guidelines</a></h2>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 1. <a id="gl-provide-equivalents"
|
|
name="gl-provide-equivalents">Provide equivalent alternatives to auditory and
|
|
visual content.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-text-equivalent"
|
|
name="tech-text-equivalent">1.1</a></span> Provide a text equivalent for every
|
|
non-text element (e.g., via "alt", "longdesc", or in element content). <em>This
|
|
includes</em>: images, graphical representations of text (including symbols),
|
|
image map regions, animations (e.g., animated GIFs), applets and programmatic
|
|
objects, <acronym title="American Standard Code for Information Interchange">
|
|
ASCII</acronym> art, frames, scripts, images used as list bullets, spacers,
|
|
graphical buttons, sounds (played with or without user interaction),
|
|
stand-alone audio files, audio tracks of video, and video. <span
|
|
class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-text-equivalent">Checkpoint
|
|
1.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#text-equivalent">Text
|
|
equivalents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#list-images">Images used as
|
|
bullets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text-images">Text for images
|
|
used as links</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#image-text-equivalent">Short text
|
|
equivalents for images ("alt-text")</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#long-descriptions">Long
|
|
descriptions of images</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#client-side-text-equivs">Text
|
|
equivalents for client-side image maps</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#applet-text-equivalent">Text and
|
|
non-text equivalents for applets and programmatic objects</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-equivs-multimedia">Text
|
|
equivalents for multimedia</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-text-equivalent">Describing
|
|
frame relationships</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#noframes">Writing for browsers
|
|
that do not support FRAME</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-graphical-buttons">
|
|
Graphical buttons</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-alt">Alternative
|
|
presentation of scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-redundant-server-links" name="tech-redundant-server-links">
|
|
1.2</a></span> Provide redundant text links for each active region of a
|
|
server-side image map. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-redundant-server-links">Checkpoint
|
|
1.2</a>)</dt>
|
|
|
|
<dd class="checkpoint">Refer also to <a href="#tech-redundant-client-links"
|
|
class="noxref">checkpoint 1.5</a> and <a href="#tech-client-side-maps"
|
|
class="noxref">checkpoint 9.1</a>.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#text-equivalent">Text
|
|
equivalents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#server-side">Server-side image
|
|
maps</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-auditory-descriptions" name="tech-auditory-descriptions">
|
|
1.3</a></span> <a href="wcag10-tech.html#def-until-user-agents">Until user
|
|
agents</a> can automatically read aloud the text equivalent of a visual track,
|
|
provide an auditory description of the important information of the visual
|
|
track of a multimedia presentation. <span class="priority1">
|
|
[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-auditory-descriptions">Checkpoint
|
|
1.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#video-information">Visual
|
|
information and motion</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-synchronize-equivalents" name="tech-synchronize-equivalents">
|
|
1.4</a></span> For any time-based multimedia presentation (e.g., a movie or
|
|
animation), synchronize equivalent alternatives (e.g., captions or auditory
|
|
descriptions of the visual track) with the presentation. <span
|
|
class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-synchronize-equivalents">Checkpoint
|
|
1.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#audio-information">Audio
|
|
information</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-redundant-client-links" name="tech-redundant-client-links">
|
|
1.5</a></span> <a href="wcag10-tech.html#def-until-user-agents">Until user
|
|
agents</a> render text equivalents for client-side image map links, provide
|
|
redundant text links for each active region of a client-side image map. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-redundant-client-links">Checkpoint
|
|
1.5</a>)</dt>
|
|
|
|
<dd class="checkpoint">Refer also to <a href="#tech-redundant-server-links"
|
|
class="noxref">checkpoint 1.2</a> and <a href="#tech-client-side-maps"
|
|
class="noxref">checkpoint 9.1</a>.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#text-equivalent">Text
|
|
equivalents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#client-side-redundant-text">
|
|
Redundant text links for client-side image maps</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 2. <a id="gl-color" name="gl-color">Don't rely
|
|
on color alone.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-color-convey"
|
|
name="tech-color-convey">2.1</a></span> Ensure that all information conveyed
|
|
with color is also available without color, for example from context or markup.
|
|
<span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-color-convey">Checkpoint
|
|
2.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-info-not-in-color-alone">
|
|
Ensuring information is not in color alone</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-color-contrast"
|
|
name="tech-color-contrast">2.2</a></span> Ensure that foreground and background
|
|
color combinations provide sufficient contrast when viewed by someone having
|
|
color deficits or when viewed on a black and white screen. [Priority 2 for
|
|
images, Priority 3 for text]. (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-color-contrast">Checkpoint
|
|
2.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#color-images">Color in
|
|
images</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-color-contrast">Color
|
|
Contrast</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 3. <a id="gl-structure-presentation"
|
|
name="gl-structure-presentation">Use markup and style sheets and do so
|
|
properly.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-use-markup"
|
|
name="tech-use-markup">3.1</a></span> When an appropriate markup language
|
|
exists, use markup rather than images to convey information. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-use-markup">Checkpoint
|
|
3.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-markup">Markup and style
|
|
sheets rather than images: The example of math</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#Generated">
|
|
Generated content</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-identify-grammar"
|
|
name="tech-identify-grammar">3.2</a></span> Create documents that validate to
|
|
published formal grammars. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-identify-grammar">Checkpoint
|
|
3.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#doctype">
|
|
The !DOCTYPE statement</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-style-sheets"
|
|
name="tech-style-sheets">3.3</a></span> Use style sheets to control layout and
|
|
presentation. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-style-sheets">Checkpoint
|
|
3.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-emphasis">Emphasis</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#text-not-images">Text instead of
|
|
images</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-text-formatting">Text
|
|
formatting and position</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-alignment">Layout,
|
|
positioning, layering, and alignment</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-relative-units"
|
|
name="tech-relative-units">3.4</a></span> Use relative rather than absolute
|
|
units in markup language attribute values and style sheet property values.
|
|
<span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-relative-units">Checkpoint
|
|
3.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<!-- @@In next draft of guidelines s/header/heading -IJ @@ -->
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-relative-size">Sizing
|
|
frames with relative units</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#units">
|
|
Units of measure</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-logical-headings"
|
|
name="tech-logical-headings">3.5</a></span> Use header elements to convey
|
|
document structure and use them according to specification. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-logical-headings">Checkpoint
|
|
3.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-headers">Section
|
|
headings</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-list-structure"
|
|
name="tech-list-structure">3.6</a></span> Mark up lists and list items
|
|
properly. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-list-structure">Checkpoint
|
|
3.6</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#lists">
|
|
Lists</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#lists">
|
|
Providing contextual clues in HTML lists</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-quotes"
|
|
name="tech-quotes">3.7</a></span> Mark up quotations. Do not use quotation
|
|
markup for formatting effects such as indentation. <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-quotes">Checkpoint 3.7</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-quotes">Quotations</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 4. <a id="gl-abbreviated-and-foreign"
|
|
name="gl-abbreviated-and-foreign">Clarify natural language usage</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-identify-changes"
|
|
name="tech-identify-changes">4.1</a></span> Clearly identify changes in the
|
|
natural language of a document's text and any <a
|
|
href="wcag10-tech.html#def-text-equivalent">text equivalents</a> (e.g.,
|
|
captions). <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-identify-changes">Checkpoint
|
|
4.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#changes-in-lang">Identifying
|
|
changes in language</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-expand-abbr"
|
|
name="tech-expand-abbr">4.2</a></span> Specify the expansion of each
|
|
abbreviation or acronym in a document where it first occurs. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-expand-abbr">Checkpoint
|
|
4.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-abbr">Acronyms and
|
|
abbreviations</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-identify-lang"
|
|
name="tech-identify-lang">4.3</a></span> Identify the primary natural language
|
|
of a document. <span class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-identify-lang">Checkpoint
|
|
4.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#identify-primary-lang">
|
|
Identifying the primary language</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 5. <a id="gl-table-markup"
|
|
name="gl-table-markup">Create tables that transform gracefully.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-table-headers"
|
|
name="tech-table-headers">5.1</a></span> For data tables, identify row and
|
|
column headers. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-table-headers">Checkpoint
|
|
5.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#identifying-table-rows-columns">
|
|
Identifying rows and column information</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-table-structure"
|
|
name="tech-table-structure">5.2</a></span> For data tables that have two or
|
|
more logical levels of row or column headers, use markup to associate data
|
|
cells and header cells. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-table-structure">Checkpoint
|
|
5.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#identifying-table-rows-columns">
|
|
Identifying rows and column information</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-avoid-table-for-layout" name="tech-avoid-table-for-layout">
|
|
5.3</a></span> Do not use tables for layout unless the table makes sense when
|
|
linearized. Otherwise, if the table does not make sense, provide an alternative
|
|
equivalent (which may be a <a href="wcag10-tech.html#def-linearized-table">
|
|
linearized version</a>). <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-table-for-layout">Checkpoint
|
|
5.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout">Tables for
|
|
layout</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-alignment">Layout,
|
|
positioning, layering, and alignment</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-table-layout"
|
|
name="tech-table-layout">5.4</a></span> If a table is used for layout, do not
|
|
use any structural markup for the purpose of visual formatting. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-table-layout">Checkpoint
|
|
5.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout">Tables for
|
|
layout</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-table-summaries"
|
|
name="tech-table-summaries">5.5</a></span> Provide summaries for tables. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-table-summaries">Checkpoint
|
|
5.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#table-summary-info">Providing
|
|
summary information</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-abbreviate-labels"
|
|
name="tech-abbreviate-labels">5.6</a></span> Provide abbreviations for header
|
|
labels. <span class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-abbreviate-labels">Checkpoint
|
|
5.6</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#table-summary-info">Providing
|
|
summary information</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p><a href="#tech-linear-tables" class="noxref">Refer also to checkpoint
|
|
10.3</a>.</p>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 6. <a id="gl-new-technologies"
|
|
name="gl-new-technologies">Ensure that pages featuring new technologies
|
|
transform gracefully.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-order-style-sheets"
|
|
name="tech-order-style-sheets">6.1</a></span> Organize documents so they may be
|
|
read without style sheets. For example, when an HTML document is rendered
|
|
without associated style sheets, it must still be possible to read the
|
|
document. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-order-style-sheets">Checkpoint
|
|
6.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#Generated">
|
|
Generated content</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-rules">Rules and
|
|
borders</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-transform-gracefully">Using
|
|
style sheet positioning and markup to transform gracefully</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-dynamic-source"
|
|
name="tech-dynamic-source">6.2</a></span> Ensure that equivalents for dynamic
|
|
content are updated when the dynamic content changes. <span class="priority1">
|
|
[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-dynamic-source">Checkpoint
|
|
6.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#applet-text-equivalent">Text and
|
|
non-text equivalents for applets and programmatic objects</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-has-html-src">Frame
|
|
sources</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-alt">Alternative
|
|
presentation of scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-scripts"
|
|
name="tech-scripts">6.3</a></span> Ensure that pages are usable when scripts,
|
|
applets, or other programmatic objects are turned off or not supported. If this
|
|
is not possible, provide equivalent information on an alternative accessible
|
|
page. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-scripts">Checkpoint 6.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#applet-text-equivalent">Text and
|
|
non-text equivalents for applets and programmatic objects</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts">
|
|
Directly accessible scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-keyboard-operable-scripts" name="tech-keyboard-operable-scripts">
|
|
6.4</a></span> For scripts and applets, ensure that event handlers are input
|
|
device-independent. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-operable-scripts">Checkpoint
|
|
6.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure">Structure vs.
|
|
Presentation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts">
|
|
Directly accessible scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-fallback-page"
|
|
name="tech-fallback-page">6.5</a></span> Ensure that dynamic content is
|
|
accessible or provide an alternative presentation or page. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-fallback-page">Checkpoint
|
|
6.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#audio-information">Audio
|
|
information</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-alternative-docs">The LINK
|
|
element and alternative documents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#noframes">Writing for browsers
|
|
that do not support FRAME</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-gt">Graceful
|
|
transformation of scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p><a href="#tech-alt-pages" class="noxref">Refer also to checkpoint
|
|
11.4</a>.</p>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 7. <a id="gl-movement" name="gl-movement">
|
|
Ensure user control of time-sensitive content changes.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-avoid-flicker"
|
|
name="tech-avoid-flicker">7.1</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> allow users
|
|
to control flickering, avoid causing the screen to flicker. <span
|
|
class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-flicker">Checkpoint
|
|
7.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#flicker">
|
|
Screen flicker</a></li>
|
|
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#video-information">Visual
|
|
information and motion</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-flicker">Scripts that
|
|
cause flickering</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-avoid-blinking"
|
|
name="tech-avoid-blinking">7.2</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> allow users
|
|
to control blinking, avoid causing content to blink (i.e., change presentation
|
|
at a regular rate, such as turning on and off). <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-blinking">Checkpoint
|
|
7.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-movement-blinking">
|
|
Scripts that cause movement and blinking</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-text">Text style
|
|
effects</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-avoid-movement"
|
|
name="tech-avoid-movement">7.3</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> allow users
|
|
to freeze moving content, avoid movement in pages. <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-movement">Checkpoint
|
|
7.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#video-information">Visual
|
|
information and motion</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#animated-images">Animated
|
|
images</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-movement-blinking">
|
|
Scripts that cause movement and blinking</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-movement">Creating movement
|
|
with style sheets and scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-no-periodic-refresh" name="tech-no-periodic-refresh">7.4</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> provide the
|
|
ability to stop the refresh, do not create periodically auto-refreshing pages.
|
|
<span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-no-periodic-refresh">Checkpoint
|
|
7.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#auto-page-refresh">Automatic page
|
|
refresh</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#meta-element">The META
|
|
element</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#script-refresh">Page updates and
|
|
new windows</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-no-auto-forward"
|
|
name="tech-no-auto-forward">7.5</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> provide the
|
|
ability to stop auto-redirect, do not use markup to redirect pages
|
|
automatically. Instead, configure the server to perform redirects. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-no-auto-forward">Checkpoint
|
|
7.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#auto-page-refresh">Automatic page
|
|
refresh</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#meta-element">The META
|
|
element</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#script-refresh">Page updates and
|
|
new windows</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<!-- this statement should be in html-techniques somewhere... WC -->
|
|
<p><strong>Note.</strong> The BLINK and MARQUEE elements are not defined in any
|
|
W3C HTML specification and should not be used. <a href="#gl-use-w3c"
|
|
class="noxref">Refer also to guideline 11</a>.</p>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 8. <a id="gl-own-interface"
|
|
name="gl-own-interface">Ensure direct accessibility of embedded user
|
|
interfaces.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoint:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-directly-accessible" name="tech-directly-accessible">8.1</a></span>
|
|
Make programmatic elements such as scripts and applets directly accessible or
|
|
compatible with assistive technologies [<span
|
|
class="priority1">Priority 1</span> if functionality is <a
|
|
href="wcag10-tech.html#def-important">important</a> and not presented
|
|
elsewhere, otherwise Priority 2.] (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-directly-accessible">Checkpoint
|
|
8.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"><a href="#gl-new-technologies" class="noxref">Refer also
|
|
to guideline 6</a>.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts">
|
|
Directly accessible scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 9. <a id="gl-device-independence"
|
|
name="gl-device-independence">Design for device-independence.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-client-side-maps"
|
|
name="tech-client-side-maps">9.1</a></span> Provide client-side image maps
|
|
instead of server-side image maps except where the regions cannot be defined
|
|
with an available geometric shape. <span class="priority1">
|
|
[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-client-side-maps">Checkpoint
|
|
9.1</a>)</dt>
|
|
|
|
<dd class="checkpoint">Refer also to <a href="#tech-text-equivalent"
|
|
class="noxref">checkpoint 1.1</a>, <a href="#tech-redundant-server-links"
|
|
class="noxref">checkpoint 1.2</a>, and <a href="#tech-redundant-client-links"
|
|
class="noxref">checkpoint 1.5</a>.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#client-vs-server-side">
|
|
Client-side versus server-side image maps</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-keyboard-operable"
|
|
name="tech-keyboard-operable">9.2</a></span> Ensure that any element that has
|
|
its own interface can be operated in a device-independent manner. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-operable">Checkpoint
|
|
9.2</a>)</dt>
|
|
|
|
<dd class="checkpoint">Refer to the definition of <a
|
|
href="#def-device-independent" rel="glossary"
|
|
title="Definition of Device independent"><span class="dfn-instance">device
|
|
independence</span></a>.</dd>
|
|
|
|
<dd class="checkpoint"><a href="#gl-own-interface" class="noxref">Refer also to
|
|
guideline 8</a>.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-device-independent-events" name="tech-device-independent-events">
|
|
9.3</a></span> For scripts, specify logical event handlers rather than
|
|
device-dependent event handlers. <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-device-independent-events">Checkpoint
|
|
9.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts">
|
|
Directly accessible scripts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-tab-order"
|
|
name="tech-tab-order">9.4</a></span> Create a logical tab order through links,
|
|
form controls, and objects. <span class="priority3">[Priority 3]</span>
|
|
(<a href="http://www.w3.org/TR/WCAG10-TECHS/#tech-tab-order">Checkpoint
|
|
9.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-accesskey">Keyboard
|
|
access</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-keyboard-access">Keyboard
|
|
access to forms</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-keyboard-shortcuts"
|
|
name="tech-keyboard-shortcuts">9.5</a></span> Provide keyboard shortcuts to
|
|
important links (including those in <a href="wcag10-tech.html#def-image-map">
|
|
client-side image maps</a>), form controls, and groups of form controls. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts">Checkpoint
|
|
9.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-accesskey">Keyboard
|
|
access</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-keyboard-access">Keyboard
|
|
access to forms</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 10. <a id="gl-interim-accessibility"
|
|
name="gl-interim-accessibility">Use interim solutions.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-avoid-pop-ups"
|
|
name="tech-avoid-pop-ups">10.1</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> allow users
|
|
to turn off spawned windows, do not cause pop-ups or other windows to appear
|
|
and do not change the current window without informing the user. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-pop-ups">Checkpoint
|
|
10.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#anchors-targets">Anchors and
|
|
targets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets">Directly
|
|
accessible applets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#no-new-windows">Using FRAME
|
|
targets</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#script-refresh">Page updates and
|
|
new windows</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-unassociated-labels" name="tech-unassociated-labels">10.2</a></span>
|
|
<a href="wcag10-tech.html#def-until-user-agents">Until user agents</a> support
|
|
explicit associations between labels and form controls, for all form controls
|
|
with implicitly associated labels, ensure that the label is properly
|
|
positioned. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels">Checkpoint
|
|
10.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<!-- somehow the text from here until content-preferences was deleted... WC -->
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels">Labeling form
|
|
controls</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-linear-tables"
|
|
name="tech-linear-tables">10.3</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> (including
|
|
assistive technologies) render side-by-side text correctly, provide a linear
|
|
text alternative (on the current page or some other) for <em>all</em> tables
|
|
that lay out text in parallel, word-wrapped columns. <span class="priority3">
|
|
[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-linear-tables">Checkpoint
|
|
10.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#wrapped-text">Linearizing
|
|
tables</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-place-holders"
|
|
name="tech-place-holders">10.4</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> handle
|
|
empty controls correctly, include default, place-holding characters in edit
|
|
boxes and text areas. <span class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-place-holders">Checkpoint
|
|
10.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-specific">Techniques for
|
|
specific controls</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-divide-links"
|
|
name="tech-divide-links">10.5</a></span> <a
|
|
href="wcag10-tech.html#def-until-user-agents">Until user agents</a> (including
|
|
assistive technologies) render adjacent links distinctly, include non-link,
|
|
printable characters (surrounded by spaces) between adjacent links. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-divide-links">Checkpoint
|
|
10.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#group-bypass">Grouping and
|
|
bypassing links</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 11. <a id="gl-use-w3c" name="gl-use-w3c">Use
|
|
W3C technologies and guidelines.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-latest-w3c-specs"
|
|
name="tech-latest-w3c-specs">11.1</a></span> Use W3C technologies when they are
|
|
available and appropriate for a task and use the latest versions when
|
|
supported. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-latest-w3c-specs">Checkpoint
|
|
11.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#access-reviewed">Technologies
|
|
Reviewed for Accessibility</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-avoid-deprecated"
|
|
name="tech-avoid-deprecated">11.2</a></span> Avoid deprecated features of W3C
|
|
technologies. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated">Checkpoint
|
|
11.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#html-index">Index of HTML
|
|
elements and attributes</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#user-override">User override of
|
|
styles</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-fonts">Fonts</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-content-preferences" name="tech-content-preferences">11.3</a></span>
|
|
Provide information so that users may receive documents according to their
|
|
preferences (e.g., language, content type, etc.) <span class="priority3">
|
|
[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-content-preferences">Checkpoint
|
|
11.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"><strong>Note.</strong> Use content negotiation where
|
|
possible.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#content-negotiation">Content
|
|
negotiation</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#acss">Aural
|
|
Cascading Style Sheets</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#Alt">Access
|
|
to alternative representations of content</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#Media">
|
|
Media types</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-alt-pages"
|
|
name="tech-alt-pages">11.4</a></span> If, <a
|
|
href="wcag10-tech.html#alt-page-note">after best efforts</a>, you cannot create
|
|
an <a href="wcag10-tech.html#def-accessible">accessible</a> page, provide a
|
|
link to an alternative page that uses W3C technologies, is accessible, has <a
|
|
href="wcag10-tech.html#def-equivalent">equivalent</a> information (or
|
|
functionality), and is updated as often as the inaccessible (original) page.
|
|
<span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-alt-pages">Checkpoint
|
|
11.4</a>)</dt>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#alt-pages">Alternative
|
|
pages</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<p><a id="alt-page-note" name="alt-page-note"><strong>Note.</strong></a>
|
|
Content developers should only resort to alternative pages when other solutions
|
|
fail because alternative pages are generally updated less often than "primary"
|
|
pages. An out-of-date page may be as frustrating as one that is inaccessible
|
|
since, in both cases, the information presented on the original page is
|
|
unavailable. Automatically generating alternative pages may lead to more
|
|
frequent updates, but content developers must still be careful to ensure that
|
|
generated pages always make sense, and that users are able to navigate a site
|
|
by following links on primary pages, alternative pages, or both. Before
|
|
resorting to an alternative page, reconsider the design of the original page;
|
|
making it accessible is likely to improve it for all users.</p>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 12. <a id="gl-complex-elements"
|
|
name="gl-complex-elements">Provide context and orientation
|
|
information.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-frame-titles"
|
|
name="tech-frame-titles">12.1</a></span> Title each frame to facilitate frame
|
|
identification and navigation. <span class="priority1">[Priority 1]</span>
|
|
(<a href="http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-titles">Checkpoint
|
|
12.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-names">Providing a frame
|
|
title</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-frame-longdesc"
|
|
name="tech-frame-longdesc">12.2</a></span> Describe the purpose of frames and
|
|
how frames relate to each other if it is not obvious by frame titles alone.
|
|
<span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-longdesc">Checkpoint
|
|
12.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#text-equivalent">Text
|
|
equivalents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-text-equivalent">Describing
|
|
frame relationships</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-group-information"
|
|
name="tech-group-information">12.3</a></span> Divide large blocks of
|
|
information into more manageable groups where natural and appropriate. <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-group-information">Checkpoint
|
|
12.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#grouping">Structural
|
|
grouping</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-grouping">Grouping form
|
|
controls</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-associate-labels"
|
|
name="tech-associate-labels">12.4</a></span> Associate labels explicitly with
|
|
their controls. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-associate-labels">Checkpoint
|
|
12.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels">Labeling form
|
|
controls</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 13. <a id="gl-facilitate-navigation"
|
|
name="gl-facilitate-navigation">Provide clear navigation mechanisms.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-meaningful-links"
|
|
name="tech-meaningful-links">13.1</a></span> Clearly identify the target of
|
|
each link. <span class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-meaningful-links">Checkpoint
|
|
13.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text">Link text</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-use-metadata"
|
|
name="tech-use-metadata">13.2</a></span> Provide metadata to add semantic
|
|
information to pages and sites. <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-use-metadata">Checkpoint
|
|
13.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-meta">Metadata</a></li>
|
|
|
|
<li>CSS Techniques: <a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#lists">
|
|
Providing contextual clues in HTML lists</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-site-description"
|
|
name="tech-site-description">13.3</a></span> Provide information about the
|
|
general layout of a site (e.g., a site map or table of contents). <span
|
|
class="priority2">[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-site-description">Checkpoint
|
|
13.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-clear-nav-mechanism" name="tech-clear-nav-mechanism">13.4</a></span>
|
|
Use navigation mechanisms in a consistent manner. <span class="priority2">
|
|
[Priority 2]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-clear-nav-mechanism">Checkpoint
|
|
13.4</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-nav-bar"
|
|
name="tech-nav-bar">13.5</a></span> Provide navigation bars to highlight and
|
|
give access to the navigation mechanism. <span class="priority3">
|
|
[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-nav-bar">Checkpoint
|
|
13.5</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-group-links"
|
|
name="tech-group-links">13.6</a></span> Group related links, identify the group
|
|
(for user agents), and, <a href="wcag10-tech.html#def-until-user-agents">until
|
|
user agents</a> do so, provide a way to bypass the group. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-group-links">Checkpoint
|
|
13.6</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#group-bypass">Grouping and
|
|
bypassing links</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-searches"
|
|
name="tech-searches">13.7</a></span> If search functions are provided, enable
|
|
different types of searches for different skill levels and preferences. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-searches">Checkpoint
|
|
13.7</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-front-loading"
|
|
name="tech-front-loading">13.8</a></span> Place distinguishing information at
|
|
the beginning of headings, paragraphs, lists, etc. <span class="priority3">
|
|
[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-front-loading">Checkpoint
|
|
13.8</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#comprehension">
|
|
Comprehension</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-bundled-version"
|
|
name="tech-bundled-version">13.9</a></span> Provide information about document
|
|
collections (i.e., documents comprising multiple pages.). <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-bundled-version">Checkpoint
|
|
13.9</a>)</dt>
|
|
|
|
<dd class="checkpoint">For example, in HTML specify document collections with
|
|
the LINK element and the "rel" and "rev" attributes. Another way to create a
|
|
collection is by building an archive (e.g., with zip, tar and gzip, stuffit,
|
|
etc.) of the multiple pages.</dd>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#bundled-documents">Bundled
|
|
documents</a></li>
|
|
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-metadata">The LINK element
|
|
and navigation tools</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-skip-over-ascii"
|
|
name="tech-skip-over-ascii">13.10</a></span> Provide a means to skip over
|
|
multi-line ASCII art. <span class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-skip-over-ascii">Checkpoint
|
|
13.10</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>HTML Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#ascii-art">Ascii art</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<div class="guideline-box">
|
|
<h3 class="guideline">Guideline 14. <a id="gl-facilitate-comprehension"
|
|
name="gl-facilitate-comprehension">Ensure that documents are clear and
|
|
simple.</a></h3>
|
|
</div>
|
|
|
|
<p>Checkpoints:</p>
|
|
|
|
<dl class="checkpoints">
|
|
<dt class="checkpoint"><span class="checkpoint"><a
|
|
id="tech-simple-and-straightforward" name="tech-simple-and-straightforward">
|
|
14.1</a></span> Use the clearest and simplest language appropriate for a site's
|
|
content. <span class="priority1">[Priority 1]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-simple-and-straightforward">Checkpoint
|
|
14.1</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#comprehension">
|
|
Comprehension</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-icons"
|
|
name="tech-icons">14.2</a></span> Supplement text with graphic or auditory
|
|
presentations where they will facilitate comprehension of the page. <span
|
|
class="priority3">[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-icons">Checkpoint 14.2</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#comprehension">
|
|
Comprehension</a></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt class="checkpoint"><span class="checkpoint"><a id="tech-consistent-style"
|
|
name="tech-consistent-style">14.3</a></span> Create a style of presentation
|
|
that is consistent across pages. <span class="priority3">
|
|
[Priority 3]</span> (<a
|
|
href="http://www.w3.org/TR/WCAG10-TECHS/#tech-consistent-style">Checkpoint
|
|
14.3</a>)</dt>
|
|
|
|
<dd class="checkpoint"></dd>
|
|
|
|
<dd class="checkpoint">
|
|
<ul>
|
|
<li>Core Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation">Navigation</a></li>
|
|
|
|
<li>CSS Techniques: <a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/#consistency">Decrease maintenance
|
|
and increase consistency</a></li>
|
|
</ul>
|
|
</dd>
|
|
</dl>
|
|
|
|
<hr />
|
|
<h2>3 <a id="glossary" name="glossary">Glossary</a></h2>
|
|
|
|
<!-- Others: text, derived equivalent, video equivalent
|
|
HTML, RDF -->
|
|
<dl>
|
|
<dt class="glossary"><a id="def-accessible" name="def-accessible"><dfn><b>
|
|
Accessible</b></dfn></a></dt>
|
|
|
|
<dd class="GLOSSARY">Content is accessible when it may be used by someone with
|
|
a disability.</dd>
|
|
|
|
<dt class="glossary"><a id="def-applet" name="def-applet"><dfn><b>
|
|
Applet</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A program inserted into a Web page.</dd>
|
|
|
|
<dt class="glossary"><a id="def-assistive-tech" name="def-assistive-tech"><dfn>
|
|
<b>Assistive technology</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Software or hardware that has been specifically designed
|
|
to assist people with disabilities in carrying out daily activities. Assistive
|
|
technology includes wheelchairs, reading machines, devices for grasping, etc.
|
|
In the area of Web Accessibility, common software-based assistive technologies
|
|
include screen readers, screen magnifiers, speech synthesizers, and voice input
|
|
software that operate in conjunction with graphical desktop browsers (among
|
|
other <a href="#def-user-agent" rel="glossary"
|
|
title="Definition of User agent"><span class="dfn-instance">user
|
|
agents</span></a>). Hardware assistive technologies include alternative
|
|
keyboards and pointing devices.</dd>
|
|
|
|
<dt class="glossary"><a id="def-ascii-art" name="def-ascii-art"><dfn><b>ASCII
|
|
art</b></dfn></a></dt>
|
|
|
|
<dd class="glossary"><acronym
|
|
title="American Standard Code for Information Interchange">ASCII</acronym> art
|
|
refers to text characters and symbols that are combined to create an image. For
|
|
example <acronym title="smiley">";-)"</acronym> is the smiley emoticon. The
|
|
following is an ASCII figure showing the relationship between flash frequency
|
|
and photoconvulsive response in patients with eyes open and closed [<a
|
|
id="ascii-chart" name="ascii-chart" href="#def-authoring-tool">skip over ASCII
|
|
figure</a> or consult a <a rel="Alternate"
|
|
href="images/ascii-chart-longdesc.html">description of chart</a>]:
|
|
|
|
<pre>
|
|
|
|
% __ __ __ __ __ __ __ __ __ __ __ __ __ __
|
|
100 | * |
|
|
90 | * * |
|
|
80 | * * |
|
|
70 | @ * |
|
|
60 | @ * |
|
|
50 | * @ * |
|
|
40 | @ * |
|
|
30 | * @ @ @ * |
|
|
20 | |
|
|
10 | @ @ @ @ @ |
|
|
0 5 10 15 20 25 30 35 40 45 50 55 60 65 70
|
|
Flash frequency (Hertz)
|
|
</pre>
|
|
</dd>
|
|
|
|
<dt class="glossary"><a id="def-authoring-tool" name="def-authoring-tool"><dfn>
|
|
<b>Authoring tool</b></dfn></a></dt>
|
|
|
|
<dd class="glossary"><acronym title="Hypertext Markup Language">HTML</acronym>
|
|
editors, document conversion tools, tools that generate Web content from
|
|
databases are all authoring tools. Refer to the "Authoring Tool Accessibility
|
|
Guidelines 1.0" (<cite><a href="#ref-ATAG10"
|
|
title="Link to reference ATAG10">[ATAG10]</a></cite>) for information about
|
|
developing accessible tools.</dd>
|
|
|
|
<dt class="glossary"><a id="def-backward-compatible"
|
|
name="def-backward-compatible"><dfn><b>Backward compatible</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Design that continues to work with earlier versions of a
|
|
language, program, etc.</dd>
|
|
|
|
<dt class="glossary"><a id="def-braille" name="def-braille"><dfn><b>
|
|
Braille</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Braille uses six raised dots in different patterns to
|
|
represent letters and numbers to be read by people who are blind with their
|
|
fingertips. The word "Accessible" in braille follows:</dd>
|
|
|
|
<dd class="GLOSSARY"><img src="images/access.gif" width="300" height="75"
|
|
alt="Accessible" /></dd>
|
|
|
|
<dd class="glossary">A <a id="def-braille-display" name="def-braille-display">
|
|
<dfn><b>braille display,</b></dfn></a> commonly referred to as a "dynamic
|
|
braille display," raises or lowers dot patterns on command from an electronic
|
|
device, usually a computer. The result is a line of braille that can change
|
|
from moment to moment. Current dynamic braille displays range in size from one
|
|
cell (six or eight dots) to an eighty-cell line, most having between twelve and
|
|
twenty cells per line.</dd>
|
|
|
|
<dt class="glossary"><a id="def-content-developer"
|
|
name="def-content-developer"><dfn><b>Content developer</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Someone who authors Web pages or designs Web sites.</dd>
|
|
|
|
<dt class="glossary"><a id="def-deprecated" name="def-deprecated"><dfn><b>
|
|
Deprecated</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A deprecated element or attribute is one that has been
|
|
outdated by newer constructs. Deprecated elements may become obsolete in future
|
|
versions of HTML. The <a id="html-index" name="html-index"
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#html-index">index of HTML
|
|
elements and attributes in the Techniques Document</a> indicates which elements
|
|
and attributes are deprecated in HTML 4.01.</dd>
|
|
|
|
<dd class="glossary">Authors should avoid using deprecated elements and
|
|
attributes. User agents should continue to support them for reasons of backward
|
|
compatibility.</dd>
|
|
|
|
<dt class="glossary"><a id="def-device-independent"
|
|
name="def-device-independent"><dfn><b>Device independent</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Users must be able to interact with a user agent (and the
|
|
document it renders) using the supported input and output devices of their
|
|
choice and according to their needs. Input devices may include pointing
|
|
devices, keyboards, braille devices, head wands, microphones, and others.
|
|
Output devices may include monitors, speech synthesizers, and braille
|
|
devices.</dd>
|
|
|
|
<dd class="glossary">Please note that "device-independent support" does not
|
|
mean that user agents must support every input or output device. User agents
|
|
should offer redundant input and output mechanisms for those devices that are
|
|
supported. For example, if a user agent supports keyboard and mouse input,
|
|
users should be able to interact with all features using either the keyboard or
|
|
the mouse.</dd>
|
|
|
|
<dt class="glossary"><a id="def-content-structure"
|
|
name="def-content-structure"><dfn><b>Document Content, Structure, and
|
|
Presentation</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">The content of a document refers to what it says to the
|
|
user through natural language, images, sounds, movies, animations, etc. The
|
|
structure of a document is how it is organized logically (e.g., by chapter,
|
|
with an introduction and table of contents, etc.). An <a href="#def-element"
|
|
rel="glossary" title="Definition of Element"><span class="dfn-instance">
|
|
element</span></a> (e.g., P, STRONG, BLOCKQUOTE in HTML) that specifies
|
|
document structure is called a <a id="def-structural-element"
|
|
name="def-structural-element"><dfn><b>structural element</b></dfn></a>. The
|
|
presentation of a document is how the document is rendered (e.g., as print, as
|
|
a two-dimensional graphical presentation, as an text-only presentation, as
|
|
synthesized speech, as braille, etc.) An <a href="#def-element" rel="glossary"
|
|
title="Definition of Element"><span class="dfn-instance">element</span></a>
|
|
that specifies document presentation (e.g., B, FONT, CENTER) is called a <a
|
|
id="def-presentation-element" name="def-presentation-element"><dfn><b>
|
|
presentation element</b></dfn></a>.</dd>
|
|
|
|
<dd class="GLOSSARY">Consider a document heading, for example. The content of
|
|
the heading is what the heading says (e.g., "Sailboats"). In HTML, the heading
|
|
is a structural element marked up with, for example, an H2 element. Finally,
|
|
the presentation of the heading might be a bold block text in the margin, a
|
|
centered line of text, a title spoken with a certain voice style (like an aural
|
|
font), etc.</dd>
|
|
|
|
<dt class="glossary"><a id="def-dhtml" name="def-dhtml"><dfn><b>Dynamic HTML
|
|
(DHTML)</b></dfn></a></dt>
|
|
|
|
<dd class="glossary"><acronym title="Dynamic HTML">DHTML</acronym> is the
|
|
marketing term applied to a mixture of standards including HTML, <a
|
|
href="#def-style-sheet" rel="glossary" title="Definition of Style sheets"><span
|
|
class="dfn-instance">style sheets</span></a>, the Document Object Model <cite>
|
|
<a href="#ref-DOM1" title="Link to reference DOM1">[DOM1]</a></cite> and
|
|
scripting. However, there is no W3C specification that formally defines DHTML.
|
|
Most guidelines may be applicable to applications using DHTML, however the
|
|
following guidelines focus on issues related to scripting and style sheets: <a
|
|
href="#gl-provide-equivalents" class="noxref">guideline 1</a>, <a
|
|
href="#gl-structure-presentation" class="noxref">guideline 3</a>, <a
|
|
href="#gl-new-technologies" class="noxref">guideline 6</a>, <a
|
|
href="#gl-movement" class="noxref">guideline 7</a>, and <a
|
|
href="#gl-device-independence" class="noxref">guideline 9</a>.</dd>
|
|
|
|
<dt class="glossary"><a id="def-element" name="def-element"><dfn><b>
|
|
Element</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">This document uses the term "element" both in the strict
|
|
SGML sense (an element is a syntactic construct) and more generally to mean a
|
|
type of content (such as video or sound) or a logical construct (such as a
|
|
heading or list). The second sense emphasizes that a guideline inspired by HTML
|
|
could easily apply to another markup language.</dd>
|
|
|
|
<dd class="glossary">Note that some (SGML) elements have content that is
|
|
rendered (e.g., the P, LI, or TABLE elements in HTML), some are replaced by
|
|
external content (e.g., IMG), and some affect processing (e.g., STYLE and
|
|
SCRIPT cause information to be processed by a style sheet or script engine). An
|
|
element that causes text characters to be part of the document is called a <a
|
|
id="def-text-element" name="def-text-element"><dfn><b>text
|
|
element</b></dfn></a>.</dd>
|
|
|
|
<dt class="glossary"><a id="def-equivalent" name="def-equivalent"><dfn><b>
|
|
Equivalent</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Content is "equivalent" to other content when both fulfill
|
|
essentially the same function or purpose upon presentation to the user. In the
|
|
context of this document, the equivalent must fulfill essentially the same
|
|
function for the person with a disability (at least insofar as is feasible,
|
|
given the nature of the disability and the state of technology), as the primary
|
|
content does for the person without any disability. For example, the text "The
|
|
Full Moon" might convey the same information as an image of a full moon when
|
|
presented to users. Note that equivalent information focuses on <strong>
|
|
fulfilling the same function</strong>. If the image is part of a link and
|
|
understanding the image is crucial to guessing the link target, an equivalent
|
|
must also give users an idea of the link target. Providing equivalent
|
|
information for inaccessible content is one of the primary ways authors can
|
|
make their documents accessible to people with disabilities.</dd>
|
|
|
|
<dd class="GLOSSARY">As part of fulfilling the same function of content an
|
|
equivalent may involve a description of that content (i.e., what the content
|
|
looks like or sounds like). For example, in order for users to understand the
|
|
information conveyed by a complex chart, authors should describe the visual
|
|
information in the chart.</dd>
|
|
|
|
<dd class="GLOSSARY">Since text content can be presented to the user as
|
|
synthesized speech, braille, and visually-displayed text, these guidelines
|
|
require <a id="def-text-equivalent" name="def-text-equivalent"><dfn><b>text
|
|
equivalents</b></dfn></a> for graphic and audio information. Text equivalents
|
|
must be written so that they convey all essential content. <a
|
|
id="def-non-text-equivalent" name="def-non-text-equivalent"><dfn><b>Non-text
|
|
equivalents</b></dfn></a> (e.g., an auditory description of a visual
|
|
presentation, a video of a person telling a story using sign language as an
|
|
equivalent for a written story, etc.) also improve accessibility for people who
|
|
cannot access visual information or written text, including many individuals
|
|
with blindness, cognitive disabilities, learning disabilities, and
|
|
deafness.</dd>
|
|
|
|
<dd class="GLOSSARY">Equivalent information may be provided in a number of
|
|
ways, including through attributes (e.g., a text value for the "alt" attribute
|
|
in HTML and SMIL), as part of element content (e.g., the OBJECT in HTML), as
|
|
part of the document's prose, or via a linked document (e.g., designated by the
|
|
"longdesc" attribute in HTML or a <a id="def-d-link" name="def-d-link"><dfn><b>
|
|
description link</b></dfn></a>). Depending on the complexity of the equivalent,
|
|
it may be necessary to combine techniques (e.g., use "alt" for an abbreviated
|
|
equivalent, useful to familiar readers, in addition to "longdesc" for a link to
|
|
more complete information, useful to first-time readers).</dd>
|
|
|
|
<dd class="GLOSSARY">A <a id="def-text-transcript" name="def-text-transcript">
|
|
<dfn><b>text transcript</b></dfn></a> is a text equivalent of audio information
|
|
that includes spoken words and non-spoken sounds such as sound effects. A <a
|
|
id="def-caption" name="def-caption"><dfn><b>caption</b></dfn></a> is a text
|
|
transcript for the audio track of a video presentation that is synchronized
|
|
with the video and audio tracks. Captions are generally rendered visually by
|
|
being superimposed over the video, which benefits people who are deaf and
|
|
hard-of-hearing, and anyone who cannot hear the audio (e.g., when in a crowded
|
|
room). A <a id="def-collated-text-transcript"
|
|
name="def-collated-text-transcript"><dfn><b>collated text
|
|
transcript</b></dfn></a> combines (collates) captions with text descriptions of
|
|
video information (descriptions of the actions, body language, graphics, and
|
|
scene changes of the video track). These text equivalents make presentations
|
|
accessible to people who are deaf-blind and to people who cannot play movies,
|
|
animations, etc. It also makes the information available to search
|
|
engines.</dd>
|
|
|
|
<dd class="GLOSSARY">One example of a non-text equivalent is an <a
|
|
id="def-auditory-description" name="def-auditory-description"><dfn><b>auditory
|
|
description</b></dfn></a> of the key visual elements of a presentation. The
|
|
description is either a prerecorded human voice or a synthesized voice
|
|
(recorded or generated on the fly). The auditory description is synchronized
|
|
with the audio track of the presentation, usually during natural pauses in the
|
|
audio track. Auditory descriptions include information about actions, body
|
|
language, graphics, and scene changes.</dd>
|
|
|
|
<dt class="glossary"><a id="def-image" name="def-image"><dfn><b>
|
|
Image</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A graphical presentation.</dd>
|
|
|
|
<dt class="glossary"><a id="def-image-map" name="def-image-map"><dfn><b>Image
|
|
map</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">An image that has been divided into regions with
|
|
associated actions. Clicking on an active region causes an action to
|
|
occur.</dd>
|
|
|
|
<dd class="GLOSSARY"><a id="def-client-side-map" name="def-client-side-map">
|
|
<dfn><b>When a user clicks on an active region of a client-side image
|
|
map,</b></dfn></a> the user agent calculates in which region the click occurred
|
|
and follows the link associated with that region. <a id="def-server-side-map"
|
|
name="def-server-side-map"><dfn><b>Clicking on an active region of a
|
|
server-side image map</b></dfn></a> causes the coordinates of the click to be
|
|
sent to a server, which then performs some action.</dd>
|
|
|
|
<dd class="GLOSSARY">Content developers can make client-side image maps
|
|
accessible by providing device-independent access to the same links associated
|
|
with the image map's regions. Client-side image maps allow the user agent to
|
|
provide immediate feedback as to whether or not the user's pointer is over an
|
|
active region.</dd>
|
|
|
|
<dt class="glossary"><a id="def-important" name="def-important"><dfn><b>
|
|
Important</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">Information in a document is important if understanding
|
|
that information is crucial to understanding the document.</dd>
|
|
|
|
<dt class="glossary"><a id="def-linearized-table" name="def-linearized-table">
|
|
<dfn><b>Linearized table</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A table rendering process where the contents of the cells
|
|
become a series of paragraphs (e.g., down the page) one after another. The
|
|
paragraphs will occur in the same order as the cells are defined in the
|
|
document source. Cells should make sense when read in order and should include
|
|
<a href="#def-structural-element" rel="glossary"
|
|
title="Definition of structural element"><span class="dfn-instance">structural
|
|
elements</span></a> (that create paragraphs, headings, lists, etc.) so the page
|
|
makes sense after linearization.</dd>
|
|
|
|
<dt class="glossary"><a id="def-link-text" name="def-link-text"><dfn><b>Link
|
|
text</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">The rendered text content of a link.</dd>
|
|
|
|
<dt class="glossary"><a id="def-natural-language" name="def-natural-language">
|
|
<dfn><b>Natural Language</b></dfn></a></dt>
|
|
|
|
<dd>Spoken, written, or signed human languages such as French, Japanese,
|
|
American Sign Language, and braille. The natural language of content may be
|
|
indicated with the "lang" attribute in HTML (<cite><a href="#ref-HTML4"
|
|
title="Link to reference HTML4">[HTML4]</a></cite>, section 8.1) and the
|
|
"xml:lang" attribute in XML (<cite><a href="#ref-XML"
|
|
title="Link to reference XML">[XML]</a></cite>, section 2.12).</dd>
|
|
|
|
<dt class="glossary"><a id="def-nav-mechanism" name="def-nav-mechanism"><dfn>
|
|
<b>Navigation Mechanism</b></dfn></a></dt>
|
|
|
|
<dd class="GLOSSARY">A navigation mechanism is any means by which a user can
|
|
navigate a page or site. Some typical mechanisms include:<br />
|
|
|
|
|
|
<dl>
|
|
<dt><a id="def-navbar" name="def-navbar"><dfn><b><em>navigation
|
|
bars</em></b></dfn></a></dt>
|
|
|
|
<dd>A navigation bar is a collection of links to the most important parts of a
|
|
document or site.</dd>
|
|
|
|
<dt><a id="def-sitemap" name="def-sitemap"><dfn><b><em>site
|
|
maps</em></b></dfn></a></dt>
|
|
|
|
<dd>A site map provides a global view of the organization of a page or
|
|
site.</dd>
|
|
|
|
<dt><a id="def-table-of-contents" name="def-table-of-contents"><dfn><b><em>
|
|
tables of contents</em></b></dfn></a></dt>
|
|
|
|
<dd>A table of contents generally lists (and links to) the most important
|
|
sections of a document.</dd>
|
|
</dl>
|
|
</dd>
|
|
|
|
<dt class="glossary"><a id="def-pda" name="def-pda"><dfn><b>Personal Digital
|
|
Assistant (PDA)</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A <acronym title="Personal Digital Assistant">
|
|
PDA</acronym> is a small, portable computing device. Most PDAs are used to
|
|
track personal data such as calendars, contacts, and electronic mail. A PDA is
|
|
generally a handheld device with a small screen that allows input from various
|
|
sources.</dd>
|
|
|
|
<dt class="glossary"><a id="def-screen-magnifier" name="def-screen-magnifier">
|
|
<dfn><b>Screen magnifier</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A software program that magnifies a portion of the screen,
|
|
so that it can be more easily viewed. Screen magnifiers are used primarily by
|
|
individuals with low vision.</dd>
|
|
|
|
<dt class="glossary"><a id="def-screen-reader" name="def-screen-reader"><dfn>
|
|
<b>Screen reader</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A software program that reads the contents of the screen
|
|
aloud to a user. Screen readers are used primarily by individuals who are
|
|
blind. Screen readers can usually only read text that is printed, not painted,
|
|
to the screen.</dd>
|
|
|
|
<dt class="glossary"><a id="def-style-sheet" name="def-style-sheet"><dfn><b>
|
|
Style sheets</b></dfn></a></dt>
|
|
|
|
<dd class="glossary">A style sheet is a set of statements that specify
|
|
presentation of a document. Style sheets may have three different origins: they
|
|
may be written by content providers, created by users, or built into user
|
|
agents. In CSS (<cite><a href="#ref-CSS2"
|
|
title="Link to reference CSS2">[CSS2]</a></cite>), the interaction of content
|
|
provider, user, and user agent style sheets is called the <dfn>
|
|
cascade</dfn>.</dd>
|
|
|
|
<dd class="GLOSSARY"><a id="def-presentation-markup"
|
|
name="def-presentation-markup"><dfn><b>Presentation markup</b></dfn></a> is
|
|
markup that achieves a stylistic (rather than structuring) effect such as the B
|
|
or I elements in HTML. Note that the STRONG and EM elements are not considered
|
|
presentation markup since they convey information that is independent of a
|
|
particular font style.</dd>
|
|
|
|
<dt class="GLOSSARY"><a id="def-tabular-information"
|
|
name="def-tabular-information"><dfn><b>Tabular information</b></dfn></a></dt>
|
|
|
|
<dd>When tables are used to represent logical relationships among data -- text,
|
|
numbers, images, etc., that information is called "tabular information" and the
|
|
tables are called "data tables". The relationships expressed by a table may be
|
|
rendered visually (usually on a two-dimensional grid), aurally (often preceding
|
|
cells with header information), or in other formats.</dd>
|
|
|
|
<dt class="glossary"><a id="def-until-user-agents"
|
|
name="def-until-user-agents"><dfn><b>Until user agents ...</b></dfn></a></dt>
|
|
|
|
<dd class="GLOSSARY">In most of the checkpoints, content developers are asked
|
|
to ensure the accessibility of their pages and sites. However, there are
|
|
accessibility needs that would be more appropriately met by <a
|
|
href="#def-user-agent" rel="glossary" title="Definition of User agent"><span
|
|
class="dfn-instance">user agents</span></a> (including <a
|
|
href="#def-assistive-tech" rel="glossary"
|
|
title="Definition of Assistive technology"><span class="dfn-instance">assistive
|
|
technologies</span></a>). As of the publication of this document, not all user
|
|
agents or assistive technologies provide the accessibility control users
|
|
require (e.g., some user agents may not allow users to turn off blinking
|
|
content, or some screen readers may not handle tables well). Checkpoints that
|
|
contain the phrase "until user agents ..." require content developers to
|
|
provide additional support for accessibility until most user agents readily
|
|
available to their audience include the necessary accessibility features.</dd>
|
|
|
|
<dd class="GLOSSARY"><strong>Note.</strong> The <acronym>WAI</acronym> Web site
|
|
(refer to <cite><a href="#ref-WAI-UA-SUPPORT"
|
|
title="Link to reference WAI-UA-SUPPORT">[WAI-UA-SUPPORT]</a></cite>) provides
|
|
information about user agent support for accessibility features. Content
|
|
developers are encouraged to consult this page regularly for updated
|
|
information.</dd>
|
|
|
|
<dt class="glossary"><a id="def-user-agent" name="def-user-agent"><dfn><b>User
|
|
agent</b></dfn></a></dt>
|
|
|
|
<dd class="GLOSSARY">Software to access Web content, including desktop
|
|
graphical browsers, text browsers, voice browsers, mobile phones, multimedia
|
|
players, plug-ins, and some software assistive technologies used in conjunction
|
|
with browsers such as screen readers, screen magnifiers, and voice recognition
|
|
software. Refer to the "User Agent Accessibility Guidelines 1.0" (<cite><a
|
|
href="#ref-UAAG10" title="Link to reference UAAG10">[UAAG10]</a></cite>) for
|
|
information about developing accessible tools.</dd>
|
|
</dl>
|
|
|
|
<hr />
|
|
<!--NewPage--><!-- this is for html2ps -->
|
|
<h2>4 <a id="References" name="References">References</a></h2>
|
|
|
|
<p>For the latest version of any <acronym
|
|
title="the World Wide Web Consortium">W3C</acronym> specification please
|
|
consult the list of <a href="http://www.w3.org/TR/"><acronym
|
|
title="the World Wide Web Consortium">W3C</acronym> Technical Reports</a>.</p>
|
|
|
|
<dl>
|
|
<dt><a id="ref-ATAG10" name="ref-ATAG10"><b>[ATAG10]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/2000/REC-ATAG10-20000203/">"Authoring Tool
|
|
Accessibility Guidelines 1.0"</a>, J. Treviranus, C. McCathieNevile, I. Jacobs,
|
|
and J. Richards, eds., 3 February 2000. This <acronym>ATAG</acronym> 1.0
|
|
Recommendation is http://www.w3.org/TR/2000/REC-ATAG10-20000203/.</dd>
|
|
|
|
<dt><a id="ref-CSS2" name="ref-CSS2"><b>[CSS2]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512/">"CSS, level 2
|
|
Recommendation"</a>, B. Bos, H. Wium Lie, C. Lilley, and I. Jacobs, eds., 12
|
|
May 1998. This CSS2 Recommendation is
|
|
http://www.w3.org/TR/1998/REC-CSS2-19980512/. The <a
|
|
href="http://www.w3.org/TR/REC-CSS2/">latest version of CSS2</a> is available
|
|
at http://www.w3.org/TR/REC-CSS2.</dd>
|
|
|
|
<dt><a id="ref-DOM1" name="ref-DOM1"><b>[DOM1]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/">"Document
|
|
Object Model (DOM) Level 1 Specification"</a>, V. Apparao, S. Byrne, M.
|
|
Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, R. Sutor, C.
|
|
Wilson, and L. Wood, eds., 1 October 1998. This DOM Level 1 Recommendation is
|
|
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001. The <a
|
|
href="http://www.w3.org/TR/REC-DOM-Level-1/">latest version of DOM Level 1</a>
|
|
is available at http://www.w3.org/TR/REC-DOM-Level-1.</dd>
|
|
|
|
<dt><a id="ref-HTML4" name="ref-HTML4"><b>[HTML4]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1999/REC-html401-19991224/">"HTML 4.01
|
|
Recommendation"</a>, D. Raggett, A. Le Hors, and I. Jacobs, eds., 24 December
|
|
1999. This <acronym>HTML</acronym> 4.01 Recommendation is
|
|
http://www.w3.org/TR/1999/REC-html401-19991224/.</dd>
|
|
|
|
<dt><a id="ref-SMIL" name="ref-SMIL"><b>[SMIL]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1998/REC-smil-19980615/">"Synchronized
|
|
Multimedia Integration Language (SMIL) 1.0 Specification"</a>, P. Hoschka, ed.,
|
|
15 June 1998. This SMIL 1.0 Recommendation is
|
|
http://www.w3.org/TR/1998/REC-smil-19980615/. The <a
|
|
href="http://www.w3.org/TR/REC-smil/">latest version of SMIL 1.0</a> is
|
|
available at http://www.w3.org/TR/REC-smil.</dd>
|
|
|
|
<dt><a id="ref-SMIL-ACCESS" name="ref-SMIL-ACCESS"><b>
|
|
[SMIL-ACCESS]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1999/NOTE-SMIL-access-19990921/">
|
|
"Accessibility Features of SMIL"</a>, M. Koivunen and I. Jacobs, eds., 21
|
|
September 1999. This W3C Note is
|
|
http://www.w3.org/TR/1999/NOTE-SMIL-access-19990921/.</dd>
|
|
|
|
<dt><a id="ref-SVG" name="ref-SVG"><b>[SVG]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/2000/CR-SVG-20000802/">"Scalable Vector
|
|
Graphics (SVG) 1.0 Specification"</a>, J. Ferraiolo, ed., 2 August 2000. This
|
|
W3C Candidate Recommendation is
|
|
http://www.w3.org/TR/2000/CR-SVG-20000802/.</dd>
|
|
|
|
<dt><a id="ref-SVG-ACCESS" name="ref-SVG-ACCESS"><b>[SVG-ACCESS]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/2000/NOTE-SVG-access-20000807/">
|
|
"Accessibility Features of SVG"</a>, C. McCathieNevile and M. Koivunen, eds., 7
|
|
August 2000. This W3C Note is
|
|
http://www.w3.org/TR/2000/NOTE-SVG-access-20000807.</dd>
|
|
|
|
<dt><a id="ref-UAAG10" name="ref-UAAG10"><b>[UAAG10]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/UAAG10/">"User Agent Accessibility
|
|
Guidelines"</a>, J. Gunderson and I. Jacobs, eds. The <a
|
|
href="http://www.w3.org/TR/UAAG10/">latest version of the User Agent
|
|
Accessibility Guidelines</a> is available at http://www.w3.org/TR/UAAG10/.</dd>
|
|
|
|
<dt><a id="ref-WCAG10" name="ref-WCAG10"><b>[WCAG10]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/">"Web Content
|
|
Accessibility Guidelines 1.0"</a>, W. Chisholm, G. Vanderheiden, and I. Jacobs,
|
|
eds., 5 May 1999. This <acronym>WCAG</acronym> 1.0 Recommendation is
|
|
http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/.</dd>
|
|
|
|
<dt><a id="ref-WCAG10-CORE-TECHNIQUES" name="ref-WCAG10-CORE-TECHNIQUES"><b>
|
|
[WCAG10-CORE-TECHNIQUES]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/WCAG10-CORE-TECHS/">"Core Techniques for Web
|
|
Content Accessibility Guidelines 1.0"</a>, W. Chisholm, G. Vanderheiden, and I.
|
|
Jacobs, eds. The latest version of this document is available at
|
|
http://www.w3.org/TR/WCAG10-CORE-TECHS/.</dd>
|
|
|
|
<dt><a id="ref-WCAG10-CSS-TECHNIQUES" name="ref-WCAG10-CSS-TECHNIQUES"><b>
|
|
[WCAG10-CSS-TECHNIQUES]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/WCAG10-CSS-TECHS/">"CSS Techniques for Web
|
|
Content Accessibility Guidelines 1.0"</a>, W. Chisholm, G. Vanderheiden, and I.
|
|
Jacobs, eds. The latest version of this document is available at
|
|
http://www.w3.org/TR/WCAG10-CSS-TECHS/.</dd>
|
|
|
|
<dt><a id="ref-WCAG10-HTML-TECHNIQUES" name="ref-WCAG10-HTML-TECHNIQUES"><b>
|
|
[WCAG10-HTML-TECHNIQUES]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/">"HTML Techniques for Web
|
|
Content Accessibility Guidelines 1.0"</a>, W. Chisholm, G. Vanderheiden, and I.
|
|
Jacobs, eds. The latest version of this document is available at
|
|
http://www.w3.org/TR/WCAG10-HTML-TECHS/.</dd>
|
|
|
|
<dt><a id="ref-XML" name="ref-XML"><b>[XML]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/TR/1998/REC-xml-19980210">"Extensible Markup
|
|
Language (XML) 1.0."</a>, T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds., 10
|
|
February 1998. This XML 1.0 Recommendation is:
|
|
http://www.w3.org/TR/1998/REC-xml-19980210. The <a
|
|
href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</a> is available
|
|
at http://www.w3.org/TR/REC-xml.</dd>
|
|
</dl>
|
|
|
|
<h2>5 <a id="Resources" name="Resources">Resources</a></h2>
|
|
|
|
<p><strong>Note:</strong> <em>W3C does not guarantee the stability of any of
|
|
the following references outside of its control. These references are included
|
|
for convenience. References to products are not endorsements of those
|
|
products.</em></p>
|
|
|
|
<h3>5.1 <a id="OtherGuidelines" name="OtherGuidelines">Other
|
|
Guidelines</a></h3>
|
|
|
|
<dl>
|
|
<dt><a id="ref-UWSAG" name="ref-UWSAG"><b>[UWSAG]</b></a></dt>
|
|
|
|
<dd><a href="http://trace.wisc.edu/redirects/htmlgide/version8.htm">"The
|
|
Unified Web Site Accessibility Guidelines"</a>, G. Vanderheiden, W. Chisholm,
|
|
eds. The Unified Web Site Guidelines were compiled by the <a
|
|
href="http://www.tracecenter.org/">Trace R & D Center</a> at the University
|
|
of Wisconsin under funding from the National Institute on Disability and
|
|
Rehabilitation Research (NIDRR), U.S. Dept. of Education.</dd>
|
|
</dl>
|
|
|
|
<h3>5.2 <a id="ToolResources" name="ToolResources">User agents and other
|
|
tools</a></h3>
|
|
|
|
<p>A list of <a href="http://www.w3.org/WAI/References/Browsing">alternative
|
|
Web browsers</a> (assistive technologies and other user agents designed for
|
|
accessibility) is maintained at the WAI Web site.</p>
|
|
|
|
<dl>
|
|
<dt><a id="ref-WAI-UA-SUPPORT" name="ref-WAI-UA-SUPPORT"><b>
|
|
[WAI-UA-SUPPORT]</b></a></dt>
|
|
|
|
<dd><a href="http://www.w3.org/WAI/Resources/WAI-UA-Support">User Agent Support
|
|
for Accessibility</a></dd>
|
|
</dl>
|
|
|
|
<!--NewPage--><!-- this is for html2ps -->
|
|
<h2>6 <a id="Acknowledgments" name="Acknowledgments">Acknowledgments</a></h2>
|
|
|
|
<dl>
|
|
<dt>Web Content Guidelines Working Group Co-Chairs:</dt>
|
|
|
|
<dd><a href="mailto:jasonw@ariel.ucs.unimelb.edu.au">Jason White</a>,
|
|
University of Melbourne</dd>
|
|
|
|
<dd><a href="mailto:gv@tracecenter.org">Gregg Vanderheiden</a>, Trace Research
|
|
and Development</dd>
|
|
|
|
<dt>W3C Team contact:</dt>
|
|
|
|
<dd><a href="mailto:wendy@w3.org">Wendy Chisholm</a></dd>
|
|
|
|
<dt>We wish to thank the following people who have contributed their time and
|
|
valuable comments to shaping these guidelines:</dt>
|
|
|
|
<dd>Harvey Bingham, Kevin Carey, Chetz Colwell, Neal Ewers, Geoff Freed, Al
|
|
Gilman, Larry Goldberg, Jon Gunderson, Eric Hansen, Phill Jenkins, Leonard
|
|
Kasday, George Kerscher, Marja-Riitta Koivunen, Josh Krieger, Chuck Letourneau,
|
|
Scott Luebking, William Loughborough, Murray Maloney, Charles McCathieNevile,
|
|
MegaZone (Livingston Enterprises), Masafumi Nakane, Mark Novak, Charles
|
|
Oppermann, Mike Paciello, David Pawson, Michael Pieper, Greg Rosmaita, Liam
|
|
Quinn, Dave Raggett, T.V. Raman, Robert Savellis, Jutta Treviranus, Steve
|
|
Tyler, and Jaap van Lelieveld</dd>
|
|
</dl>
|
|
|
|
<p><a href="http://www.w3.org/WAI/WCAG1AAA-Conformance"
|
|
title="Explanation of Level Triple-A Conformance"><img class="conform"
|
|
height="32" width="88" src="http://www.w3.org/WAI/wcag1AAA"
|
|
alt="Level Triple-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0" />
|
|
</a></p>
|
|
|
|
<div class="navbar"><map id="navbar-bottom" name="navbar-bottom"
|
|
title="Navigation Bar">
|
|
<hr class="navbar" title="Navigation area separator" />
|
|
<p>[<a href="#toc">contents</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-CORE-TECHS/">Core Techniques</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-HTML-TECHS/">HTML Techniques</a>] [<a
|
|
href="http://www.w3.org/TR/WCAG10-CSS-TECHS/">CSS Techniques</a>] </p>
|
|
</map></div>
|
|
</body>
|
|
</html>
|
|
|