--- a/longdesc1/longdesc.html Thu Jan 09 10:13:38 2014 -0500
+++ b/longdesc1/longdesc.html Tue Jun 03 09:48:21 2014 -0400
@@ -14,9 +14,9 @@
color: #404;
padding: 2px;
content: "Example: (Informative)"}
-
+
.example:first-child {padding-top:1em}
-
+
/* Make these stand-out more... */
.externalDFN {
font-style: italic;
@@ -74,7 +74,7 @@
*****************************************************************/
/* --- INLINES --- */
-em.rfc2119 {
+em.rfc2119 {
text-transform: lowercase;
font-variant: small-caps;
font-style: normal;
@@ -434,8 +434,8 @@
<section id="intro" class="introductory">
<h1>Introduction</h1>
- <p>The <code>longdesc</code> attribute gives authors a mechanism for referencing a long text
- description for images which cannot be adequately described using shorter description
+ <p>The <code>longdesc</code> attribute gives authors a mechanism for referencing a long text
+ description for images which cannot be adequately described using shorter description
mechanisms, such as the <code>alt</code> attribute.</p>
<p>HTML 4 provided a <code>longdesc</code> attribute for the <code>img</code>
@@ -463,10 +463,10 @@
</section>
<section id="conformance">
<h2><span class="secno">1. </span>Conformance</h2>
- <p>All authoring guidelines, diagrams, examples, notes, and sections marked
- "<a href="http://www.w3.org/TR/qaframe-spec/#informative-def">informative</a>"
- in this specification are informational. Everything else in this specification is
- "<a href="http://www.w3.org/TR/qaframe-spec/#normative-def">normative</a>" as described in
+ <p>All authoring guidelines, diagrams, examples, notes, and sections marked
+ "<a href="http://www.w3.org/TR/qaframe-spec/#informative-def">informative</a>"
+ in this specification are informational. Everything else in this specification is
+ "<a href="http://www.w3.org/TR/qaframe-spec/#normative-def">normative</a>" as described in
[<a href="#bib-QAFRAME">QAFRAME</a>]. </p>
<p>The key words <em title="must" class="rfc2119">"must"</em>, <em title="should"
class="rfc2119">"should"</em>,
@@ -492,19 +492,19 @@
</section>
<section id="UCnR">
<h2><span class="secno">2. </span>Use Cases and Requirements</h2>
- <p>There are many ways users can successfully interact with images even if
- they cannot see, or see well. The <code>alt</code> attribute is
- designed to ensure that for everyday work, a user has enough information
- to replace an image, and often this is more helpful than a detailed
- description of every image. The <code>longdesc</code> attribute is
- designed to complement this functionality, to meet the following use
- cases. </p>
+ <p>Text alternatives are used to make visual information accessible by describing
+ the information or function represented in the image. The <code>alt</code>
+ attribute is designed to provide a concise description or functional equivalent
+ for the image, based on context. For some images and contexts, more detail
+ is required to convey all the information contained in an image. The
+ <code>longdesc</code> attribute is designed as a means to provide this
+ level of detail, such as in the following use cases.</p>
<h3 id="use-cases">Use Cases</h3>
<dl>
<dt>Identifying a well-known image</dt>
<dd>Identifying an image is often important context for a discussion.
There are many well-known images which are widely reproduced and well
- known. In some cases, such as "Mona Lisa", "Guernica", "A Starry Night",
+ known. In some cases, such as "Mona Lisa", "Guernica", "A Starry Night",
or "The Scream", the most effective way to identify an
image is to use its title, creator, and similar information that would
be found in a catalog. But different people know images by different
@@ -515,7 +515,7 @@
do all the paddling", or "the Da Vinci picture of the man in a square and
a circle".</dd>
<dd><em>Requires</em>: <a href="#discoverability">Discoverability</a></dd>
- <dd><em>Helped by</em>: <a href="#inline">Inline</a>,
+ <dd><em>Helped by</em>: <a href="#inline">Inline</a>,
<a href="#reuse">Reuse</a></dd>
<dt>Describing a complex diagram</dt>
<dd>In many environments diagrams are used to explain a concept or
@@ -523,30 +523,30 @@
see the image (poor contrast vision and other conditions are as
relevant here as a complete lack of vision), a description can enable
that user to understand the information being presented.</dd>
- <dd><em>Requires</em>: <a href="#structured-markup">Structured Markup</a>,
- <a href="#inline">Inline</a>, <a href="#reuse">Reuse</a>,
+ <dd><em>Requires</em>: <a href="#structured-markup">Structured Markup</a>,
+ <a href="#inline">Inline</a>, <a href="#reuse">Reuse</a>,
<a href="#simple-return">Simple Return</a></dd>
<dt>Teaching accessible development</dt>
<dd>In many environments producing content that is accessible to users
regardless of disability is a legal and/or market requirement. </dd>
- <dd><em>Requires</em>: <a href="#maintenance">Maintenance</a>,
+ <dd><em>Requires</em>: <a href="#maintenance">Maintenance</a>,
<a href="#backwards-compatibility">Backwards Compatibility</a></dd>
<dt>A self-describing artistic work</dt>
<dd>The visual design of many pages is an important part of the message
the author intends to convey to a fully-sighted user. Many authors
would like to convey as much of that design as possible to a user with
low or no vision. </dd>
- <dd><em>Requires</em>: <a href="#no-visual-encumbrance">No Visual Encumbrance</a>,
+ <dd><em>Requires</em>: <a href="#no-visual-encumbrance">No Visual Encumbrance</a>,
<a href="#structured-markup">Structured Markup</a></dd>
- <dd><em>Helped by</em>: <a href="#reuse">Reuse</a>,
+ <dd><em>Helped by</em>: <a href="#reuse">Reuse</a>,
<a href="#simple-return">Simple Return</a></dd>
<dt>Referring to an existing description</dt>
<dd>Many well-known images are already described by other sources. The
copyright on those sources may not be compatible with re-publishing
the description, but there is little value in making a new one. </dd>
- <dd><em>Requires</em>: <a href="#reuse">Reuse</a>,
- <a href="#structured-markup">Structured Markup</a>,
- <a href="#simple-return">Simple Return</a>,
+ <dd><em>Requires</em>: <a href="#reuse">Reuse</a>,
+ <a href="#structured-markup">Structured Markup</a>,
+ <a href="#simple-return">Simple Return</a>,
<a href="#optional-consumption">Optional Consumption</a></dd>
<dd><em>Helped by</em>: <a href="#no-visual-encumbrance">No Visual Encumbrance</a></dd>
<dt>Linking to a description included within a page</dt>
@@ -559,25 +559,25 @@
<dd>This practice also enables description to be provided for all users.</dd>
<dd>By keeping the association clear the content maintainer can more
easily check that the description and link are actually correct.</dd>
- <dd><em>Requires</em>: <a href="#inline">Inline</a>,
- <a href="#simple-return">Simple Return</a>,
+ <dd><em>Requires</em>: <a href="#inline">Inline</a>,
+ <a href="#simple-return">Simple Return</a>,
<a href="#structured-markup">Structured Markup</a>,
<a href="#optional-consumption">Optional Consumption</a></dd>
<dt>Localizing descriptions</dt>
<dd>When content is translated to multiple languages, it is important
that metadata intended for humans, such as image
descriptions, can be readily localized.</dd>
- <dd><em>Helped by</em>: <a href="#structured-markup">Structured Markup</a>,
+ <dd><em>Helped by</em>: <a href="#structured-markup">Structured Markup</a>,
<a href="#reuse">Reuse</a>, <a href="#maintenance">Maintenance</a>.</dd>
<dt>Image search</dt>
- <dd>Many search engines provide an option to search for images and present
- the results out of context. The ability to discover and process identified
- descriptions allows search engines to improve the source material they use
+ <dd>Many search engines provide an option to search for images and present
+ the results out of context. The ability to discover and process identified
+ descriptions allows search engines to improve the source material they use
to support text-based queries for images.</dd>
<dd><em>Requires</em>: <a href="#discoverability">Discoverability</a></dd>
<dt>Describing images</dt>
- <dd>Image search tools identify multiple copies of the same image. Where a
- search tool can identify a description of an image, this can be provided
+ <dd>Image search tools identify multiple copies of the same image. Where a
+ search tool can identify a description of an image, this can be provided
to the user as a description for any copies of that image.</dd>
<dd><em>Requires</em>: <a href="#discoverability">Discoverability</a></dd>
<dd><em>Helped by</em>: <a href="#reuse">Reuse</a></dd>
@@ -641,38 +641,38 @@
<p><em>This section is informative</em></p>
<p>Best practices for checking descriptions of images are beyond the
scope of this document, but there are many resources available.
- For further guidance authoring tool developers can consult e.g.
- <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#prompt-long-description">Appendix A-3: Long text descriptions</a>
+ For further guidance authoring tool developers can consult e.g.
+ <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#prompt-long-description">Appendix A-3: Long text descriptions</a>
of [<a href="#bib-ATAG">ATAG</a>].</p>
<p>High quality implementation in authoring and content management
tools is likely to include checking for common errors, such as
including a description instead of a URL in the attribute, or
pointing to a resource that is an image or plain text, which are
- often poor choices for a high-quality description. Additional
- examples of error checking and repair options can be found in
- <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#checking-types">Appendix B: Levels of Checking Automation</a>
- and <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#repair-types">Appendix C: Levels of Repair Automation</a>
+ often poor choices for a high-quality description. Additional
+ examples of error checking and repair options can be found in
+ <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#checking-types">Appendix B: Levels of Checking Automation</a>
+ and <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#repair-types">Appendix C: Levels of Repair Automation</a>
of [<a href="#bib-ATAG">ATAG</a>]</p>
<p>This document does not define the term "accessible", nor
accessibility. For further guidance on making an accessible
document, authors can consult e.g. [<a href="#bib-WCAG2">WCAG</a>].</p>
</div>
<h4 id="authors">3.0.2 Authors</h4>
- <p>When a description is only part of the target document, authors
- <em class="rfc2119">should</em> link to a fragment link in the target document
+ <p>When a description is only part of the target document, authors
+ <em class="rfc2119">should</em> link to a fragment link in the target document
(e.g. <code>longdesc="example.html#description"</code>).</p>
<div class="note">
<p><em>This section is informative</em></p>
<p>Best practices for full descriptions of images are beyond the scope
of this document, but there are many resources available.</p>
</div>
- <p>Authors <em class="rfc2119">should</em> not rely solely on longdesc where standards
- exist to provide direct, structured access.</p>
+ <p>Authors <em class="rfc2119">should</em> not rely solely on longdesc where standards
+ exist to provide direct, structured access.</p>
<div class="note">
<p><em>This section is informative</em></p>
- <p>For example a MathML version of mathematical content, or an SVG image that
- uses the accessibility features of SVG, can provide better accessibility to
- users with appropriate technology. In such cases, it is appropriate to use
+ <p>For example a MathML version of mathematical content, or an SVG image that
+ uses the accessibility features of SVG, can provide better accessibility to
+ users with appropriate technology. In such cases, it is appropriate to use
longdesc as a fallback strategy, in combination with more modern techniques.</p>
</div>
<h4 id="user-agents">3.0.3 User Agents</h4>
@@ -827,11 +827,11 @@
<dl class="bibliography">
<dt id="bib-QAFRAME">[QAFRAME]</dt>
<dd>Karl Dubost et. al., eds. <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">
- <cite>QA Framework: Specification Guidelines.</cite></a>, August 2005. W3C Recommendation.
+ <cite>QA Framework: Specification Guidelines.</cite></a>, August 2005. W3C Recommendation.
URL: <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/</a></dd>
<dt id="bib-ATAG">[ATAG]</dt>
- <dd>Jutta Treviranus et. al., eds. <cite><a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/">Implementing ATAG 2.0</cite></a>,
- October 2011. W3C Working Draft.
+ <dd>Jutta Treviranus et. al., eds. <cite><a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/">Implementing ATAG 2.0</cite></a>,
+ October 2011. W3C Working Draft.
URL: <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/">http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/</a></dd>
<dt id="bib-WCAG2">[WCAG]</dt>
<dd>Ben Caldwell et. al., eds. <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/"><cite>Web
@@ -850,18 +850,18 @@
<h3 id="change-second">Between the current draft and the <a href="http://www.w3.org/TR/2013/WD-html-longdesc-20130716/">Last Call Working Draft</a></h3>
<p>Editorial changes include:</p>
<ul>
- <li>Added text to the "Introduction" section that more clearly defines
+ <li>Added text to the "Introduction" section that more clearly defines
the <code>longdesc</code> attribute.</li>
- <li>Added more precise references to relevant sections of ATAG in
+ <li>Added more precise references to relevant sections of ATAG in
the "Implementation" section.</li>
- <li>Added text to clarify the use of longdesc in conjunction with
+ <li>Added text to clarify the use of longdesc in conjunction with
other techniques.</li>
<li>Added the "Image Search" and "Describing images" use case.</li>
- <li>Improved examples in the "Identifying a well known image" use
+ <li>Improved examples in the "Identifying a well known image" use
case</li>
- <li>Clarified the scope of normative text in the "Conformance"
+ <li>Clarified the scope of normative text in the "Conformance"
section.</li>
- <li>Hyperlinked "Use Case" references to their definitions and
+ <li>Hyperlinked "Use Case" references to their definitions and
rearranged definitions in alphabetical order.</li>
<li>Removed "title" attribute from example.</li>
<li>Added Mark Sadecki as an editor.</li>