linked use case references to definitions, made case consistent and ordered definitions in alpha order per EOWG comments
authorMark Sadecki <mark@w3.org>
Fri, 13 Dec 2013 16:04:30 -0500
changeset 63 c8da8ec4a07b
parent 62 6ddbb6ab517c
child 64 fd6cee5efc3f
linked use case references to definitions, made case consistent and ordered definitions in alpha order per EOWG comments
longdesc1/longdesc.html
--- a/longdesc1/longdesc.html	Fri Dec 13 15:38:31 2013 -0500
+++ b/longdesc1/longdesc.html	Fri Dec 13 16:04:30 2013 -0500
@@ -507,33 +507,41 @@
           crossing some river, standing heroically in the boat, while soldiers
           do the hard work", or "the Da Vinci picture of the guy in a square and
           a circle".</dd>
-        <dd><em>Requires</em>: Discoverability</dd>
-        <dd><em>Helped by</em>: Inline, Reuse</dd>
+        <dd><em>Requires</em>: <a href="#discoverability">Discoverability</a></dd>
+        <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
           transmit information efficiently. For a user with a reduced ability to
           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>: Structured Markup, Inline, Reuse, Simple Return</dd>
+        <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>: Maintenance, Backwards compatibility</dd>
+        <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>: No visual encumbrance, Structured Markup</dd>
-        <dd><em>Helped by</em>: Reuse, Simple Return</dd>
+        <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>, 
+          <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>: Reuse, Structured Markup, Simple Return, Optional
-          Consumption </dd>
-        <dd><em>Helped by</em>: No Visual Encumbrance</dd>
+        <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>
         <dd>If an image already has a description included within a page, making
           the linkage explicit can provide further clarity for a user who is not
@@ -544,48 +552,51 @@
         <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>: Inline, Simple Return, Structured Markup,
-          Optional Consumption </dd>
+        <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 localized to multiple languages, it is important
           that metadata intended for human consumption, such as image
           descriptions, can be readily localized.</dd>
-        <dd><em>Helped by</em>: Structured Markup, Reuse, Maintenance.</dd>
+        <dd><em>Helped by</em>: <a href="#structured-markup">Structured Markup</a>, 
+          <a href="#reuse">Reuse</a>, <a href="#maintenance">Maintenance</a>.</dd>
       </dl>
       <h3 id="requirements">Requirements for an Image Description functionality</h3>
       <dl>
-        <dt>No visual encumbrance</dt>
+        <dt id="backwards-compatibility">Backwards Compatibility </dt>
+        <dd>It <em class="rfc2119">should</em> be possible to use existing
+          tools and techniques to associate an image with its description. </dd>
+        <dt id="discoverability">Discoverability </dt>
+        <dd class="rfc2119">It <em class="rfc2119">must</em> be simple for a
+          user agent to automatically discover a description provided for a
+          given image.</dd>
+        <dt id="inline">Inline</dt>
+        <dd>It <em class="rfc2119">must</em> be possible to associate a
+          description in the body of a page with an image in that page. </dd>
+        <dt id="maintenance">Maintenance</dt>
+        <dd>It <em class="rfc2119">must</em> be simple to maintain a library of
+          images and descriptions for dynamic assembly, or dis-assembly and
+          re-assembly, of content. </dd>
+        <dt id="no-visual-encumbrance">No Visual Encumbrance</dt>
         <dd>It <em class="rfc2119">must</em> be possible to provide a
           description for an image without forcing the description to be
           rendered on the page.</dd>
-        <dt>Structured Markup</dt>
-        <dd>It <em class="rfc2119">must</em> be possible to include rich markup
-          (e.g. HTML5) in the description of the image.</dd>
-        <dt>Inline</dt>
-        <dd>It <em class="rfc2119">must</em> be possible to associate a
-          description in the body of a page with an image in that page. </dd>
-        <dt>Reuse</dt>
+        <dt id="optional-consumption">Optional Consumption</dt>
+        <dd>A user <em class="rfc2119">must</em> be able to choose not to read
+          the long description of a given image.</dd>
+        <dt id="reuse">Reuse</dt>
         <dd>It <em class="rfc2119">must</em> be possible to re-use a single
           description for multiple occurrences of an image.</dd>
-        <dt>Maintenance</dt>
-        <dd>It <em class="rfc2119">must</em> be simple to maintain a library of
-          images and descriptions for dynamic assembly, or dis-assembly and
-          re-assembly, of content. </dd>
-        <dt>Discoverability </dt>
-        <dd class="rfc2119">It <em class="rfc2119">must</em> be simple for a
-          user agent to automatically discover a description provided for a
-          given image.</dd>
+        <dt id="simple-return">Simple Return</dt>
+        <dd>A user <em class="rfc2119">must</em> be able to return from the
+          description to the image. </dd>
+        <dt id="structured-markup">Structured Markup</dt>
+        <dd>It <em class="rfc2119">must</em> be possible to include rich markup
+          (e.g. HTML5) in the description of the image.</dd>
         <dd>A user <em class="rfc2119">should</em> be able to determine that
           there is a description available for a given image. </dd>
-        <dt>Optional consumption</dt>
-        <dd>A user <em class="rfc2119">must</em> be able to choose not to read
-          the long description of a given image.</dd>
-        <dt>Simple return</dt>
-        <dd>A user <em class="rfc2119">must</em> be able to return from the
-          description to the image. </dd>
-        <dt>Backwards Compatibility </dt>
-        <dd>It <em class="rfc2119">should</em> be possible to use existing
-          tools and techniques to associate an image with its description. </dd>
       </dl>
     </section>
     <section id="longdesc">