HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
59779437apply wg decision2011-04-08 20:17
@@ -45,35 +45,40 @@
   and the occasional informative paragraph or example has been removed
   for technical or editorial reasons. For all intents and purposes,
   however, the W3C HTML specifications and this specification are
   equivalent (and they are in fact all generated from the same source
   document). The minor differences are:</p>
   <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>
    <li>Examples that use features from HTML5 are not present in the
    W3C version since the W3C version is published as HTML4 due to <a
    publication policies</a>.</li>
    <li>The W3C version omits a paragraph of implementation advice
    because of <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="">a
+   working group decision from March 2011</a>.</li>
   <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>
   <ul class="brief">
    <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--DEVICE-->
    <li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li> <!--PING-->
    <li>The <span>WebVTT</span> format and some <span>text track</span> API features.</li> <!--TT--> <!--TTVTT-->
@@ -9857,23 +9862,23 @@ interface <dfn>HTMLUnknownElement</dfn> : <span>HTMLElement</span> { };</pre>
   preserve whitespace. <a href="#refsXML">[XML]</a></p>
   <p class="note">There is no way to serialize the <code
   title="attr-xml-space">xml:space</code> attribute on <span>HTML
   elements</span> in the <code>text/html</code> syntax.</p>
   <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>
   <h5>The <dfn title="attr-id"><code>id</code></dfn> attribute</h5>
   <p>The <code title="attr-id">id</code> attribute specifies its
   element's <dfn title="concept-id">unique identifier (ID)</dfn>. The
   value must be unique amongst all the IDs in the element's <span>home
   subtree</span> and must contain at least one character. The value
   must not contain any <span title="space character">space
@@ -11644,21 +11649,21 @@ plaintext     = *( %x0000-2029 / %x202F-10FFFF )
                 ; any string with no bidirectional-algorithm formatting characters</pre>
   <p class="note">For convenience, where possible authors will likely
   prefer to use the <code title="attr-dir">dir</code> attribute, the
   <code>bdo</code> element, and the <code>bdi</code> element, rather
   than maintaining the bidirectional-algorithm formatting characters
-  <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
   elements</span>, in accordance with the requirements described in
   the ARIA specifications, except where these conflict with the
   <span>strong native semantics</span> described below. These
   exceptions are intended to prevent authors from making assistive
   technology products report nonsensical states that do not represent
   the actual state of the document. <a href="#refsARIA">[ARIA]</a></p>
@@ -12118,20 +12123,31 @@ plaintext     = *( %x0000-2029 / %x202F-10FFFF )
      <td><span>The body element</span>
      <td><code title="attr-aria-role-document">document</code> role
      <td>Role must be either <code title="attr-aria-role-document">document</code> or <code title="attr-aria-role-application">application</code>
   <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>
   element is marked as having the <code
   title="attr-aria-role-button">button</code> role, a conformance
   checker could say "Use a more appropriate element to represent a
   button, for example a <code>button</code> element or an
   <code>input</code> element" rather than "The <code
   title="attr-aria-role-button">button</code> role cannot be used with
   <code>a</code> elements".</p>