[e] (0) apply wg decision

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9437

git-svn-id: http://svn.whatwg.org/webapps@5977 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

       <li><a href=#paragraphs><span class=secno>3.2.5.3 </span>Paragraphs</a></ol></li>
     <li><a href=#requirements-relating-to-bidirectional-algorithm-formatting-characters><span class=secno>3.2.6 </span>Requirements relating to bidirectional-algorithm formatting
  characters</a></li>
     <li><a href=#annotations-for-assistive-technology-products-(aria)><span class=secno>3.2.7 </span>Annotations for assistive technology products (ARIA)</a></ol></li>
     <li><a href=#wai-aria><span class=secno>3.2.7 </span>WAI-ARIA</a></ol></li>
   <li><a href=#apis-in-html-documents><span class=secno>3.3 </span>APIs in HTML documents</a></li>
   <li><a href=#interactions-with-xpath-and-xslt><span class=secno>3.4 </span>Interactions with XPath and XSLT</a></li>
   <li><a href=#dynamic-markup-insertion><span class=secno>3.5 </span>Dynamic markup insertion</a>

  <hr><p>To enable assistive technology products to expose a more
  fine-grained interface than is otherwise possible with HTML elements
  and attributes, a set of <a href=#annotations-for-assistive-technology-products-(aria)>annotations for assistive technology
  products</a> can be specified (the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
  and attributes, a set of <a href=#wai-aria title=WAI-ARIA>annotations for
  assistive technology products</a> can be specified (the ARIA
  <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>


  <h5 id=the-id-attribute><span class=secno>3.2.3.1 </span>The <dfn title=attr-id><code>id</code></dfn> attribute</h5>



  <h4 id=annotations-for-assistive-technology-products-(aria)><span class=secno>3.2.7 </span><dfn>Annotations for assistive technology products</dfn> (ARIA)</h4>
  <h4 id=wai-aria><span class=secno>3.2.7 </span><dfn>WAI-ARIA</dfn></h4>

  <p>Authors may use the ARIA <code title=attr-aria-role>role</code>
  and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML

  </table><div class=impl>


  <p>Conformance checkers are encouraged to phrase errors such that
  authors are encouraged to use more appropriate elements rather than
  remove accessibility annotations. For example, if an <code><a href=#the-a-element>a</a></code>

index

       <li><a href=#paragraphs><span class=secno>3.2.5.3 </span>Paragraphs</a></ol></li>
     <li><a href=#requirements-relating-to-bidirectional-algorithm-formatting-characters><span class=secno>3.2.6 </span>Requirements relating to bidirectional-algorithm formatting
  characters</a></li>
     <li><a href=#annotations-for-assistive-technology-products-(aria)><span class=secno>3.2.7 </span>Annotations for assistive technology products (ARIA)</a></ol></li>
     <li><a href=#wai-aria><span class=secno>3.2.7 </span>WAI-ARIA</a></ol></li>
   <li><a href=#apis-in-html-documents><span class=secno>3.3 </span>APIs in HTML documents</a></li>
   <li><a href=#interactions-with-xpath-and-xslt><span class=secno>3.4 </span>Interactions with XPath and XSLT</a></li>
   <li><a href=#dynamic-markup-insertion><span class=secno>3.5 </span>Dynamic markup insertion</a>

  <ul class=brief><li>Instead of this section, the W3C version has a different
   paragraph explaining the difference between the W3C and WHATWG
   versions of HTML.</li>
   versions of HTML.</li> <!-- in the status section -->

   <li>The W3C version refers to the technology as HTML5, rather than
   just HTML.</li>
   because of <a href=http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html>a
   working group decision from June 2010</a>.</li>

   <li>The W3C version includes a paragraph of advice redundant with
   the ARIA specifications because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html>a
   working group decision from March 2011</a>.</li>

  </ul><p>Features that are considered part of the next generation of HTML
  beyond HTML5 (and that are therefore not included in the W3C version
  of HTML5) currently consist of:</p>

  <hr><p>To enable assistive technology products to expose a more
  fine-grained interface than is otherwise possible with HTML elements
  and attributes, a set of <a href=#annotations-for-assistive-technology-products-(aria)>annotations for assistive technology
  products</a> can be specified (the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>
  and attributes, a set of <a href=#wai-aria title=WAI-ARIA>annotations for
  assistive technology products</a> can be specified (the ARIA
  <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes).</p>


  <h5 id=the-id-attribute><span class=secno>3.2.3.1 </span>The <dfn title=attr-id><code>id</code></dfn> attribute</h5>



  <h4 id=annotations-for-assistive-technology-products-(aria)><span class=secno>3.2.7 </span><dfn>Annotations for assistive technology products</dfn> (ARIA)</h4>
  <h4 id=wai-aria><span class=secno>3.2.7 </span><dfn>WAI-ARIA</dfn></h4>

  <p>Authors may use the ARIA <code title=attr-aria-role>role</code>
  and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML

  </table><div class=impl>


  <p>Conformance checkers are encouraged to phrase errors such that
  authors are encouraged to use more appropriate elements rather than
  remove accessibility annotations. For example, if an <code><a href=#the-a-element>a</a></code>

source

@@ -52,7 +52,7 @@

   <li>Instead of this section, the W3C version has a different
   paragraph explaining the difference between the W3C and WHATWG
   versions of HTML.</li>
   versions of HTML.</li> <!-- in the status section -->

   <li>The W3C version refers to the technology as HTML5, rather than
   just HTML.</li>
@@ -67,6 +67,11 @@
   href="http://lists.w3.org/Archives/Public/public-html/2010Jun/0001.html">a
   working group decision from June 2010</a>.</li>

   <li>The W3C version includes a paragraph of advice redundant with
   the ARIA specifications because of <a
   href="http://lists.w3.org/Archives/Public/public-html/2011Mar/0244.html">a
   working group decision from March 2011</a>.</li>

  </ul>

  <p>Features that are considered part of the next generation of HTML
@@ -9864,9 +9869,9 @@ interface <dfn>HTMLUnknownElement</dfn> : <span>HTMLElement</span> { };</pre>

  <p>To enable assistive technology products to expose a more
  fine-grained interface than is otherwise possible with HTML elements
  and attributes, a set of <span>annotations for assistive technology
  products</span> can be specified (the ARIA <code
  title="attr-aria-role">role</code> and <code
  and attributes, a set of <span title="WAI-ARIA">annotations for
  assistive technology products</span> can be specified (the ARIA
  <code title="attr-aria-role">role</code> and <code
  title="attr-aria-*">aria-*</code> attributes).</p>


@@ -11651,7 +11656,7 @@ plaintext     = *( %x0000-2029 / %x202F-10FFFF )



  <h4><dfn>Annotations for assistive technology products</dfn> (ARIA)</h4>
  <h4><dfn>WAI-ARIA</dfn></h4>

  <p>Authors may use the ARIA <code title="attr-aria-role">role</code>
  and <code title="attr-aria-*">aria-*</code> attributes on <span>HTML

  <div class="impl">

<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!-- EDITORIAL: this paragraph is redundant with WAI-ARIA and doesn't really make any sense anyway; see bug 9437 -->
  <p>The WAI-ARIA specification neither requires or forbids user
  agents from enhancing native presentation and interaction behaviors
  on the basis of WAI- ARIA markup. Even mainstream user agents might
  choose to expose metadata or navigational features directly or via
  user-installed extensions; for example, exposing required form
  fields or landmark navigation. User agents are encouraged to
  maximize their usefulness to users, including users without
  disabilities.</p>
<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!-- EDITORIAL -->

  <p>Conformance checkers are encouraged to phrase errors such that
  authors are encouraged to use more appropriate elements rather than
  remove accessibility annotations. For example, if an <code>a</code>