--- a/longdesc1/longdesc.html	Sat Dec 14 18:41:55 2013 -0500
+++ b/longdesc1/longdesc.html	Thu Dec 19 14:46:38 2013 -0500
@@ -635,17 +635,18 @@
           <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&nbsp; further guidance tool developers can consult e.g. [<a href="#bib-ATAGB3">ATAGB3</a>].
-            <span class="issue">ISSUE: This doesn't seem a great reference - is
-              there anything better? This is tracked in <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=21501">bug
-                21501</a> and its dependent bugs. Unless a proposal for
-              improvement is made and accepted this bug will simply be closed
-              after Last Call.</span></p>
+            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.</p>
+            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>
@@ -822,11 +823,10 @@
             <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. 
               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-ATAGB3">[ATAGB3]</dt>
-            <dd>Jutta Treviranus et. al., eds. <a href="http://www.w3.org/TR/ATAG20-TECHS/#principle_b3"><cite>Implementing
-                  ATAG 2.0</cite></a>, Principle B3 "Authors must be supported
-              in improving the accessibility of existing content" October 2011.
-              W3C Working Draft. URL: <a href="http://www.w3.org/TR/ATAG20-TECHS/#principle_b3">http://www.w3.org/TR/ATAG20-TECHS/#principle_b3</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. 
+              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
                   Content Accessibility Guidelines 2.0</cite></a>, December