--- a/longdesc1/longdesc.html Tue Jun 03 22:07:53 2014 -0400
+++ b/longdesc1/longdesc.html Tue Jun 03 23:20:10 2014 -0400
@@ -638,7 +638,7 @@
element represents. </p>
<p>The linked description <em class="rfc2119">should</em> be in a
broadly accessible format.</p>
- <div class="note" role="region" aria-label="informative">>
+ <div class="note" role="region" aria-label="informative">
<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.
@@ -669,7 +669,7 @@
</div>
<p>Authors <em class="rfc2119">should</em> not rely solely on longdesc where standards
exist to provide direct, structured access.</p>
- <div class="note" role="region" aria-label="informative">>
+ <div class="note" role="region" aria-label="informative">
<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
@@ -685,7 +685,7 @@
APIs. </p>
<p>User agents <em class="rfc2119">should</em> enable users to discover
when images in a page contain a long description.</p>
- <div class="note" role="region" aria-label="informative">>
+ <div class="note" role="region" aria-label="informative">
<p><em>This section is informative</em></p>
<p><code>longdesc</code> can be present on an image within a
hyperlink. This does not change the requirements on user agents,