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

html5/html-api-map static.html,NONE,1.1

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 14 Apr 2011 10:47:21 +0000
To: public-html-commits@w3.org
Message-Id: <E1QAK53-0001vv-JG@lionel-hutz.w3.org>
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv7402

Added Files:
	static.html 
Log Message:
new

--- NEW FILE: static.html ---
<html lang="en" dir="ltr"><head>
	<title>HTML to Platform Accessibility APIs Implementation Guide</title>
	<style type="text/css">
caption {
    text-align:left;
    font-weight:bold
}
table {
    width:100%;
    border-collapse: collapse;
    border: 1px solid #630;
    font: normal 80% arial, Verdana, helvetica, sans-serif;
}

th, td {
    text-align: left;
    vertical-align: top;
    padding: 0.3em;
    border-collapse: collapse;
[...3141 lines suppressed...]
<div id="examples-sum" class="section">
	<h3><span class="secno">8.1 </span><code>summary</code> and <code>details</code> elements</h3>
</div>
</div>
<div id="┬┐focus-keyboard&quot;" class="section">
	<!--OddPage--><h2><span class="secno">9. </span>focus and keyboard interaction</h2>
	<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 id="rol-name-state" class="section">
	<!--OddPage--><h2><span class="secno">10. </span>Role, name, state and property mapping</h2>
	<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>
</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 id="references" class="appendix section"><!--OddPage--><h2><span class="secno">A. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">A.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">A.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
Received on Thursday, 14 April 2011 10:47:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 April 2011 10:47:23 GMT