- From: Steven Faulkners via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 14 Feb 2011 17:01:32 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-api-map In directory hutz:/tmp/cvs-serv13958 Modified Files: overview.html Log Message: added loads Index: overview.html =================================================================== RCS file: /sources/public/html5/html-api-map/overview.html,v retrieving revision 1.24 retrieving revision 1.25 diff -u -d -r1.24 -r1.25 --- overview.html 11 Feb 2011 16:27:30 -0000 1.24 +++ overview.html 14 Feb 2011 17:01:30 -0000 1.25 @@ -50,27 +50,50 @@ <LINK href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css"></HEAD> <BODY> - <H1>HTML to Platform Accessibility APIs Implementation Guide</H1> - <h2 id="subhead">A user agent developer's guide to understanding and implementing accessibility support in HTML</h2> - <H2>Editor's Draft, 11 February 2011</H2> + <div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">HTML to Platform Accessibility APIs Implementation Guide</h1> + <h2 id="subhead">A user agent developer's guide to understanding and implementing accessibility support in HTML</h2> +<h2 id="w3c-editors-draft"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft, 14 February 2011</h2> + + [...2780 lines suppressed...] + <h2>Interactive elements</h2> + <h3><code>summary</code> and <code>details</code> elements</h3> <p><span class="note">to do</span></p> - <H2> </H2> - <H2> </H2></BODY></HTML> \ No newline at end of file + <h3>Accessible Description calculation</h3> + <p><span class="note">to do</span></p> + <H2 id="examples">Accessible feature implementation examples:</H2> + <h3 id="examples-sum"><code>summary</code> and <code>details</code> elements</h3> + <h4>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>summmary</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> + <h4>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> +</BODY></HTML> \ No newline at end of file
Received on Monday, 14 February 2011 17:01:34 UTC