html5/alt-techniques Overview.html,1.106,1.107

Update of /sources/public/html5/alt-techniques
In directory hutz:/tmp/cvs-serv31748

Modified Files:
	Overview.html 
Log Message:
added alt text decision tree hat tip @joedolson

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/alt-techniques/Overview.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- Overview.html	15 May 2012 09:20:48 -0000	1.106
+++ Overview.html	26 Jun 2012 12:46:12 -0000	1.107
@@ -733,7 +733,7 @@
 </style>
 </head>
 <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" width="72" height="48"></a></p><h1 class="title" id="title">HTML5: Techniques for providing useful text alternatives</h1>
-<h2 id="w3c-editor-s-draft-26-may-2011">W3C Editor's Draft 15 May 2012</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/alt-techniques/">http://dev.w3.org/html5/alt-techniques/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-alt-techniques/">http://www.w3.org/TR/html-alt-techniques/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/alt-techniques/">http://dev.w3.org/html5/alt-techniques/</a></dd>
+<h2 id="w3c-editor-s-draft-26-may-2011">W3C Editor's Draft 26 June 2012</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/alt-techniques/">http://dev.w3.org/html5/alt-techniques/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-alt-techniques/">http://www.w3.org/TR/html-alt-techniques/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/alt-techniques/">http://dev.w3.org/html5/alt-techniques/</a></dd>
 <dt>Developer edition:</dt>
 <dd><a href="http://dev.w3.org/html5/alt-techniques/developer.html">http://dev.w3.org/html5/alt-techniques/developer.html</a> </dd>
 <!-- <h2 id="w3c-working-draft-29-march-2012">W3C Working Draft 29 March 2012</h2>
@@ -796,10 +796,9 @@
     <ul class="toc">
       <li class="tocline"><a class="tocxref" href="#abstract"><span class="secno">1. </span>Abstract</a></li>
       <li class="tocline"><a class="tocxref" href="#intro_alt"><span class="secno">2. </span>Introduction</a>
-        <ul class="toc">
-          <li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">2.1 </span>Conformance</a></li>
-        </ul>
-      </li>
+      <ul class="toc"><li class="tocline"><a href="#tree" class="tocxref"><span class="secno">2.1 </span>A simple alt text decision tree</a></li>
+        <li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">2.2 </span>Conformance</a></li>
+      </ul>
       <li class="tocline"><a class="tocxref" href="#recommendations"><span class="secno">3. </span>Requirements and Recommendations:</a>
         <ul class="toc">
           <li class="tocline"><a class="tocxref" href="#sec1"><span class="secno">3.1 </span>A link or button containing only an image</a></li>
@@ -875,8 +874,38 @@
       <li>Write suitable alt text according to context. The same image in a different   situation may need very different alt text. </li>
       <li>Avoid redundant alt text. An example of this would be repeating the same   text in your document, as well as in the alt attribute, and is unnecessary. </li>
     </ul>
+    <h3 id="tree"><span class="secno">2.1 </span>A simple alt text decision tree</h3>
+    <p>A simple <em>informative</em> process for deciding if and what an alt text should be:</p>
+    <ul>
+      <LI>Is this image the <a href="#sec1">only content of a link or form control</a>?
+        <UL>
+          <LI><STRONG>Yes</STRONG>: Use the <code>alt</code> attribute  communicate the destination of the link or action taken</LI>
+          <LI><STRONG>No</STRONG>: Continue on!</LI>
+        </UL>
+      </LI>
+      <LI>Does this <a href="#sec3">image contain text</a> not provided near the image?
+        <UL>
+          <LI><STRONG>Yes</STRONG>: Use the <code>alt</code> attribute to include the communicative text of the image (not text included for visual effect)</LI>
+          <LI><STRONG>No</STRONG>: Continue on!</LI>
+        </UL>
+      </LI>
+      <LI>Does the image contribute meaning to the current page or context?
+        <UL>
+          <LI><strong>Yes</strong>, but a suitable alt text is unknown at the time of publication: <a href="#sec12">provide a caption for the image</a>.</LI>
+          <LI><STRONG>Yes, </STRONG>and it’s a <a href="#sec6">simple graphic</a> or <a href="#sec9">photograph</a>: the <code>alt</code> attribute should briefly describe the image in a way that conveys that meaning.</LI>
+          <LI><STRONG>Yes</STRONG>, and it’s a <a href="#sec2">graph or complex piece of information</a>: include the information contained in the image  elsewhere on the page.</LI>
+          <LI><STRONG>No</STRONG>: Use an <a href="#secm3">empty</a> <code>alt</code> attribute.      </LI>
+        </UL>
+      </LI>
+      <LI>Is the image <a href="#sec5">purely decorative</a> or <a href="#sec7">not intended</a> for the user?
+        <UL>
+          <LI>Use an <a href="#secm3">empty</a> <code>alt</code> attribute.</LI>
+        </UL>
+      </LI>
+    </ul>
+    <p><strong>Note:</strong> This decision tree <strong>does not</strong> cover all cases, for detailed information on the provision of text alternatives refer to the  <a href="#recommendations">requirements and recommendations</a> below.</p>
     <div class="section" id="conformance">
-      <h3><span class="secno">2.1 </span>Conformance</h3>
+      <h3><span class="secno">2.2 </span>Conformance</h3>
       <p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
       <p>The key words <em title="must" class="rfc2119">must</em>, <em title="must not" class="rfc2119">must not</em>, <em title="required" class="rfc2119">required</em>, <em title="should" class="rfc2119">should</em>, <em title="should not" class="rfc2119">should not</em>, <em title="recommended" class="rfc2119">recommended</em>, <em title="may" class="rfc2119">may</em>, and <em title="optional" class="rfc2119">optional</em> in this specification are to be interpreted as described in [<cite><a href="#bib-RFC2119" rel="biblioentry" class="bibref">RFC2119</a></cite>].</p>
       <H4 id="compliance-with-other-specifications">2.1.1 Compliance with other specifications</H4>
@@ -1886,7 +1915,7 @@
     <!--OddPage-->
     <h2 id="acknowledgements"><span class="secno">6. </span>Acknowledgements</h2>
     <p class="note1">In no particular order and incomplete.</p>
-    <p>Laura Carlson, Josh O Connor, Gez Lemon, Anne van Kesteren, Ian Hickson, Mike Smith,  Mike Paciello, Bim Egan, Gregory Rosmaita, Michael Cooper, Janina Sajka, Matt May, Bevi Chagnon, Jonathan Avila, Pat Rees, Charlie Pike, Andy Maseyk, Rich Clark</p>
+    <p>Laura Carlson, Josh O Connor, Gez Lemon, Anne van Kesteren, Ian Hickson, Mike Smith,  Mike Paciello, Bim Egan, Gregory Rosmaita, Michael Cooper, Janina Sajka, Matt May, Bevi Chagnon, Jonathan Avila, Pat Rees, Charlie Pike, Andy Maseyk, Rich Clark. Joe Dolson (for the <a href="#tree">alt text decison tree</a>)</p>
     <h3 id="funders"> Enabling funders</h3>
     <p>The  development of this publication is being funded in part by <a href="http://www.paciellogroup.com">The Paciello Group</a>. The content  of this publication does not necessarily reflect the views or policies of  The Paciello Group, nor does mention of trade names, commercial products, or organizations imply endorsement by The Paciello Group. </p>
   </div>

Received on Tuesday, 26 June 2012 12:46:28 UTC