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

html5/html-api-map overview.html,1.48,1.49

From: Steven Faulkners via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 26 May 2011 15:41:31 +0000
To: public-html-commits@w3.org
Message-Id: <E1QPcgl-0004Ee-4a@lionel-hutz.w3.org>
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv16262

Modified Files:
Log Message:
updated style sheets got rid of JS error

Index: overview.html
RCS file: /sources/public/html5/html-api-map/overview.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- overview.html	25 May 2011 17:24:11 -0000	1.48
+++ overview.html	26 May 2011 15:41:28 -0000	1.49
@@ -1,7 +1,7 @@
-<!DOCTYPE html>
-	<HTML lang="en-US">
-	<HEAD>
-	<TITLE>HTML to Platform Accessibility APIs Implementation Guide</TITLE>
+<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
+<html lang="en" dir="ltr">
+	<title>HTML to Platform Accessibility APIs Implementation Guide</title>
 	<style type="text/css">
 caption {
[...3598 lines suppressed...]
 	<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>
-<section id="rol-name-state">
-	<h4>Role, name, state and property mapping</h4>
+<div class="section" id="rol-name-state">
+	<!--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>
 	<!--<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>-->
-    </BODY></HTML>
+<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
Received on Thursday, 26 May 2011 15:41:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:10:34 UTC