HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
599810900apply wg decision2011-04-12 23:49
@@ -124,20 +124,25 @@
    the ARIA specifications because of <a
    working group decision from March 2011</a>.</li>
    <li>The W3C version gives incomplete advice regarding the <code
    title="attr-img-alt">alt</code> attribute and instead references
    other documents on the matter because of <a
    working group decision from March 2011</a>.</li>
+   <li>The W3C version includes a link to an incomplete document that
+   contradict this specification because of <a
+   href="">a
+   working group decision from Februray 2011</a>.</li><!--HPAAIG-->
   <p>Features that are part of HTML (and this specification) but that
   are currently published as separate specifications as well, and are
   not included in the W3C HTML5 specification, consist of:</p>
   <ul class="brief">
    <li><a href="#2dcontext">Canvas 2D Graphics Context</a>
    <li><a href="#microdata">Microdata</a>
    <li><a href="#mdvocabs">Microdata vocabularies</a>
@@ -1522,20 +1527,32 @@ a.setAttribute('href', ''); // change the content attribute d
    that meets a well defined set of constraints is interpreted as
    compatible, regardless of whether they are processed as HTML or as
    XHTML, per the HTML5 specification. Polyglot markup uses a specific
    DOCTYPE, namespace declarations, and a specific case &mdash;
    normally lower case but occasionally camel case &mdash; for element
    and attribute names. Polyglot markup uses lower case for certain
    attribute values. Further constraints include those on empty
    elements, named entity references, and the use of scripts and
+<!--(the following is not included in the WHATWG spec for quality reasons)-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--HPAAIG-->
+   <dt><cite>HTML to Platform Accessibility APIs Implementation Guide</cite> <a href="#refsHPAAIG">[HPAAIG]</a></dt>
+   <dd><blockquote><p>This is draft documentation mapping HTML
+   elements and attributes to accessibility API Roles, States and
+   Properties on a variety of platforms. It provides recommendations
+   on deriving the accessible names and descriptions for HTML
+   elements. It also provides accessible feature implementation
+   examples.</p></blockquote></dd>
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--HPAAIG-->
   <h2 id="infrastructure">Common infrastructure</h2>
   <p>This specification refers to both HTML and XML attributes and IDL
   attributes, often in the same context. When it is not clear which is
@@ -110423,20 +110440,23 @@ interface <span>HTMLDocument</span> {
    C. Clavius. Gregory XIII Papal Bulls, February 1582.</dd>
    <dt id="refsHATOM">[HATOM]</dt>
    <dd>(Non-normative) <cite><a
    href="">hAtom</a></cite>, D
    Janes. Microformats.</dd>
    <dt id="refsHMAC">[HMAC]</dt>
    <dd><cite><a href="">The Keyed-Hash Message Authentication Code (HMAC)</a></cite>. NIST.</dd>
+   <dt id="refsHPAAIG">[HPAAIG]</dt>
+   <dd><cite><a href="">HTML to Platform Accessibility APIs Implementation Guide</a></cite>. W3C.</dd>
    <dt id="refsHTML4">[HTML4]</dt>
    <dd>(Non-normative) <cite><a
    href="">HTML 4.01
    Specification</a></cite>, D. Raggett, A. Le Hors, I. Jacobs.  W3C.</dd>
    <dt id="refsHTML">[HTML]</dt>
    I. Hickson. WHATWG.</dd>