W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2011

html5/html-api-map overview.html,1.52,1.53

From: Steven Faulkners via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 14 Oct 2011 13:08:30 +0000
To: public-html-commits@w3.org
Message-Id: <E1REhV0-0003IW-KF@lionel-hutz.w3.org>
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv12662

Modified Files:
	overview.html 
Log Message:
added table algorithm notes, fixed up TOC and added akcnowledgements

Index: overview.html
===================================================================
RCS file: /sources/public/html5/html-api-map/overview.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -d -r1.52 -r1.53
--- overview.html	10 Jun 2011 12:35:06 -0000	1.52
+++ overview.html	14 Oct 2011 13:08:28 -0000	1.53
@@ -1,7 +1,8 @@
-<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
-<html lang="en-x-not-hixie" dir="ltr">
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
 <head>
 	<title>HTML to Platform Accessibility APIs Implementation Guide</title>
+    <meta charset="utf-8">
 	<style type="text/css">
 caption {
     text-align:left;
@@ -398,13 +399,13 @@
 }
 
 .note {
-    margin: 1em 0em 0em;
-    padding:    1em;
-    border: 2px solid #cff6d9;
-    background: #e2fff0;
+    margin: 0.5em 0em 0em;
+    padding:    0.5em;
+    border: 1px dashed #FF0000;
+    background: #f5f5f5;
 }
 
-.note::before {
+/*.note::before {
     content:    "Note";
     display:    block;
     width:  150px;
@@ -413,7 +414,7 @@
     border: 1px solid #cff6d9;
     background: #fff;
     padding:    3px 1em;
-}
+} */
 
 /* --- Best Practices --- */
 div.practice {
@@ -516,7 +517,7 @@
 pre.sh_sourceCode .sh_attribute { color: #006400; }
 
 </style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-ED"></head><body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" width="72" height="48"></a></p><h1 class="title" id="title">HTML to Platform Accessibility APIs Implementation Guide</h1><h2 id="subtitle">A user agent developer's guide to understanding and implementing accessibility support in HTML</h2>
-<h2 id="w3c-editor-s-draft-26-may-2011">W3C Editor's Draft 10 June 2011</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/html-api-map/">http://dev.w3.org/html5/html-api-map/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-aapi/">http://www.w3.org/TR/html-aapi/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/html-api-map/">http://dev.w3.org/html5/html-api-map/</a></dd><dt>Previous version:</dt><dd>none</dd><dt>Editors:</dt><dd><span>Steve Faulkner</span>, The Paciello Group <span class="ed_mailto"><a href="mailto:sfaulkner@paciellogroup.com">sfaulkner@paciellogroup.com</a></span> </dd>
+<h2 id="w3c-editor-s-draft-26-may-2011">W3C Editor's Draft 14 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://dev.w3.org/html5/html-api-map/">http://dev.w3.org/html5/html-api-map/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-aapi/">http://www.w3.org/TR/html-aapi/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/html-api-map/">http://dev.w3.org/html5/html-api-map/</a></dd><dt>Previous version:</dt><dd>none</dd><dt>Editors:</dt><dd><span>Steve Faulkner</span>, The Paciello Group <span class="ed_mailto"><a href="mailto:sfaulkner@paciellogroup.com">sfaulkner@paciellogroup.com</a></span> </dd>
 <dd><span>Cynthia Shelly</span>, Microsoft <span class="ed_mailto"><a href="mailto:cyns@microsoft.com">cyns@microsoft.com</a></span> </dd>
 </dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
 
@@ -528,7 +529,21 @@
   accessible feature implementation examples.</p>
 </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
   <p class="warning"><strong>This document is subject to change without notice.</strong></p>
-<p>This document was published by the <a href="http://www.w3.org/html/wg/">HTML Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-html@w3.org">public-html@w3.org</a> (<a href="mailto:public-html-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-html/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#intro_aapi"><span class="secno">1. </span>Introduction: Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a></li><li class="tocline"><a class="tocxref" href="#expose"><span class="secno">2. </span>Exposing HTML features that do not directly map to accessibility <abbr title="application programing interface">API</abbr> properties</a></li><li class="tocline"><a class="tocxref" href="#api-role"><span class="secno">3. </span>HTML element to Accessibility API Role Mapping Matrix</a></li><li class="tocline"><a class="tocxref" href="#api-att"><span class="secno">4. </span>HTML attribute to Accessibility API State and Property Mapping Matrix </a></li><li class="tocline"><a class="tocxref" href="#calc"><span class="secno">5. </span>Accessible Name and Description calculation</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#inputs"><span class="secno">5.1 </span>input type="button" , input type="submit",  input type="reset" and input type="password"</a></li><li class="tocline"><a class="tocxref" href="#input-image"><span class="secno">5.2 </span>input type="image"</a></li><li class="tocline"><a class="tocxref" href="#control-other"><span class="secno">5.3 </span>Other form elements</a></li><li class="tocline"><a class="tocxref" href="#figure-caption"><span class="secno">5.4 </span>Figure and figcaption elements </a></li><li class="tocline"><a class="tocxref" href="#img"><span class="secno">5.5 </span>img element</a></li></ul></li><li class="tocline"><a class="tocxref" href="#interactive"><span class="secno">6. </span>Interactive elements</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#summary-details"><span class="secno">6.1 </span><code>summary</code> and <code>details</code> elements</a></li></ul></li><li class="tocline"><a class="tocxref" href="#accessible-description"><span class="secno">7. </span>Accessible Description calculation</a></li><li class="tocline"><a class="tocxref" href="#examples"><span class="secno">8. </span>Accessible feature implementation examples:</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#examples-sum"><span class="secno">8.1 </span><code>summary</code> and <code>details</code> elements</a></li></ul></li><li class="tocline"><a class="tocxref" href="#focus-keyboard"><span class="secno">9. </span>focus and keyboard interaction</a></li><li class="tocline"><a class="tocxref" href="#rol-name-state"><span class="secno">10. </span>Role, name, state and property mapping</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">A.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">A.2 </span>Informative references</a></li></ul></li></ul></div>
+<p>This document was published by the <a href="http://www.w3.org/html/wg/">HTML Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-html@w3.org">public-html@w3.org</a> (<a href="mailto:public-html-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-html/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#intro_aapi"><span class="secno">1. </span>Introduction: Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a></li><li class="tocline"><a class="tocxref" href="#expose"><span class="secno">2. </span>Exposing HTML features that do not directly map to accessibility <abbr title="application programing interface">API</abbr> properties</a></li><li class="tocline"><a class="tocxref" href="#api-role"><span class="secno">3. </span>HTML element to Accessibility API Role Mapping Matrix</a></li><li class="tocline"><a class="tocxref" href="#api-att"><span class="secno">4. </span>HTML attribute to Accessibility API State and Property Mapping Matrix </a></li><li class="tocline"><a class="tocxref" href="#calc"><span class="secno">5. </span>Accessible Name and Description calculation</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#inputs"><span class="secno">5.1 </span>input type="button" , input type="submit",  input type="reset" and input type="password"</a></li><li class="tocline"><a class="tocxref" href="#input-image"><span class="secno">5.2 </span>input type="image"</a></li><li class="tocline"><a class="tocxref" href="#control-other"><span class="secno">5.3 </span>Other form elements</a></li><li class="tocline"><a class="tocxref" href="#figure-caption"><span class="secno">5.4 </span>Figure and figcaption elements </a></li><li class="tocline"><a class="tocxref" href="#img"><span class="secno">5.5 </span>img element</a></li></ul></li><li class="tocline"><a class="tocxref" href="#interactive"><span class="secno">6. </span>Interactive elements</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#summary-details"><span class="secno">6.1 </span><code>summary</code> and <code>details</code> elements</a></li></ul></li><li class="tocline"><a class="tocxref" href="#accessible-description"><span class="secno">7. </span>Accessible Description calculation</a></li><li class="tocline"><a class="tocxref" href="#examples"><span class="secno">8. </span>Accessible feature implementation examples:</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#examples-sum"><span class="secno">8.1 </span><code>summary</code> and <code>details</code> elements</a>
+          <ul>
+            <li><a class="tocxref" href="#focus-keyboard"><span class="secno">8.1.1. </span>focus and keyboard interaction</a></li>
+            <li><a class="tocxref" href="#rol-name-state"><span class="secno">8.1.2. </span>Role, name, state and property mapping</a></li>
+          </ul>
+</li>
+        </ul>
+</li>
+    <li>9. <a href="#ta">Table algorithm</a></li>
+    <li class="tocline"><a class="tocxref" href="#references"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">A.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">A.2 </span>Informative references</a></li>
+      </ul>
+    </li>
+    <li><a href="#ack">Acknowledgements</a></li>
+</ul>
+</div>
 
 	<div class="section" id="intro_aapi">
 	  <!--OddPage--><h2><span class="secno">1. </span>Introduction: Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></h2>
@@ -3152,18 +3167,18 @@
 </div>
 <div class="section" id="figure-caption">
 	<h3><span class="secno">5.4 </span>Figure and figcaption elements </h3>
-	<p><span class="note">to do</span></p>
+	<p class="note">to do</p>
 </div>
 <div class="section" id="img">
 	<h3><span class="secno">5.5 </span>img element</h3>
-	<p><span class="note">to do</span></p>
+	<p class="note">to do</p>
 </div>
 </div>
 <div class="section" id="interactive">
 	<!--OddPage--><h2><span class="secno">6. </span>Interactive elements</h2>
 <div class="section" id="summary-details">
 	<h3><span class="secno">6.1 </span><code>summary</code> and <code>details</code> elements</h3>
-	<p><span class="note">to do</span></p>
+	<p class="note">to do</p>
 	<h2 id="other-elements">Other Elements</h2>
 	<h3 id="the-table-element">The <code>table</code> element</h3>
 	<p>If the table element has an <code><a href="http://www.w3.org/TR/wai-aria/states_and_properties#aria-label">aria-label</a></code> or an <code><a href="http://www.w3.org/TR/wai-aria/states_and_properties#aria-labelledby">aria-labelledby</a></code> attribute the accessible name is to be calculated using the algorithm defined in  section <a href="http://www.w3.org/TR/wai-aria/roles#namecalculation">5.2.7.  Accessible Name Calculation</a> of the <a href="http://www.w3.org/TR/wai-aria/">WAI-ARIA 1.0 specification</a>.    </p>
@@ -3172,7 +3187,7 @@
 </div>
 <div class="section" id="accessible-description">
 	<!--OddPage--><h2><span class="secno">7. </span>Accessible Description calculation</h2>
-	<p><span class="note">to do</span></p>
+	<p class="note">to do</p>
 </div>
 <div class="section" id="examples">
 	<!--OddPage--><h2><span class="secno">8. </span>Accessible feature implementation examples:</h2>
@@ -3181,18 +3196,34 @@
 </div>
 </div>
 <div class="section" id="focus-keyboard">
-	<!--OddPage--><h2><span class="secno">9. </span>focus and keyboard interaction</h2>
+	<!--OddPage--><h4><span class="secno">8.1.1 </span>focus and keyboard interaction</h4>
 	<p>The <code>summary</code> element should be focusable by default.</p>
 	<p>The <code>details</code> element should not focusable by default.	</p>
 	<p>Pressing the spacebar key when the <code>summary</code> element has focus will show the <code>details</code> element content if the content is hidden. If the  <code>details</code> element content is showing and the <code>summary</code> element has focus, pressing the spacebar key will hide the details element content.</p>
 </div>
 <div class="section" id="rol-name-state">
-	<!--OddPage--><h2><span class="secno">10. </span>Role, name, state and property mapping</h2>
+	<!--OddPage--><h4><span class="secno">8.1.2 </span>Role, name, state and property mapping</h4>
 	<p>The <code>summary</code> element should be mapped to a disclosure triangle role in accessibility APIs that have such a role. For example the Mac accessibility API includes the <code>AXDisclosureTriangle</code> role. In accessibility APIs that do not have such a fine grained role, the summary element should be mapped to a <code>button</code> role. The role mapping table contains <a href="#sum">recommended mappings for the summary element</a>.</p>
 	<p>The accessible name  for the summary element is the text content of the summary element. </p>
 	<p>When the details element content is hidden, the state of the content should be reflected by an accessible state or property. For example, in the Mac accessibility API on the <code>summary</code> element (<code>AXDisclosureTriangle</code>), set <code>AXValue</code> property to 0.  When the details element content is showing on the <code>summary</code> element (<code>AXDisclosureTriangle</code>), set the <code>AXValue</code> property to 1. The hidden and showing states of the details element is reflected by the absence or presence of the <a href="#att-open">open</a> attribute.</p>
+	<h2 id="ta">9. Table algorithm</h2>
+	<p>The algorithm is a heuristic to determine if table is most likely used for layout, it is currently implemented in Firefox only.</p>
+	<p class="note">to do</p>
+	<h3>Notes:</h3>
+	<ul>
+	  <li><a href="http://mxr.mozilla.org/mozilla-central/ident?i=IsProbablyForLayout">IsProbablyForLayout</a></li>
+	  <li><a href="http://www.456bereastreet.com/archive/201110/using_displaytable_has_semantic_effects_in_some_screen_readers/">Using display:table has semantic effects in some screen readers</a></li>
+	  <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=693948">Bug&nbsp;693948</a> -<span id="summary_alias_container"> <span id="short_desc_nonedit_display">expose layout-guess: true object attribute on CSS table accessible</span></span></li>
+  </ul>
+	<p>&nbsp;</p>
 </div>
 	<!--<h2>Role Categorisation</h2>
 	<p>Roles that are not explicitly defined in Accessibility APIs can still be exposed by user agents as accessibility API object properties.</p>-->
     
-<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">A. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">A.1 </span>Normative references</h3><p>No normative references.</p></div><div class="section" id="informative-references"><h3><span class="secno">A.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file
+<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">A. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">A.1 </span>Normative references</h3><p>No normative references.</p></div><div class="section" id="informative-references"><h3><span class="secno">A.2 </span>Informative references</h3><p>No informative references.</p>
+    <h2 id="ack">Acknowledgements</h2>
+    <h3> Enabling funders</h3>
+    <p>The  development of this publication is being funded in part by <a href="http://www.adobe.com">Adobe Systems</a>. The content  of this publication does not necessarily reflect the views or policies of  Adobe, nor does mention of trade names, commercial products, or organizations  imply endorsement by Adobe. </p>
+    <p>The  development of this publication is being funded in part by <a href="http://www.paciellogroup.com">The Paciello Group</a>. The content  of this publication does not necessarily reflect the views or policies of  Adobe, nor does mention of trade names, commercial products, or organizations  imply endorsement by The Paciello Group. </p>
+    <p>&nbsp;</p>
+</div></div></body></html>
\ No newline at end of file
Received on Friday, 14 October 2011 13:08:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 October 2011 13:08:34 GMT