- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 14 Apr 2011 10:02:25 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv31916
Modified Files:
overview.html
Log Message:
switched over to using respec
Index: overview.html
===================================================================
RCS file: /sources/public/html5/html-api-map/overview.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- overview.html 14 Mar 2011 04:20:32 -0000 1.31
+++ overview.html 14 Apr 2011 10:02:22 -0000 1.32
@@ -1,5 +1,4 @@
-
- <!DOCTYPE html>
+<!DOCTYPE html>
<HTML lang="en-US">
<HEAD>
<TITLE>HTML to Platform Accessibility APIs Implementation Guide</TITLE>
@@ -41,54 +40,47 @@
color: #900;
}
</style>
-
- <LINK href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css"></HEAD>
+ <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script class='remove'>
+ var respecConfig = {
+ subtitle: "A user agent developer's guide to understanding and implementing accessibility support in HTML",
+ // document info
+ specStatus: "FPWD",
+ shortName: "html-aapi",
+ publishDate: "2011-04-14",
+ // previousMaturity: "WD",
+ // previousPublishDate: "2009-03-15",
+ // previousURI : "http://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
+ copyrightStart: "2011",
+ edDraftURI: "http://http://dev.w3.org/html5/html-api-map/",
+ // lcEnd: "2010-08-06",
+ // extraCSS: ["../css/respec.css"],
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors
+ editors: [
+ { name: "Steve Faulkner",
+ company: "The Paciello Group", mailto: "sfaulkner@paciellogroup.com" },
+ { name: "Cynthia Shelly",
+ company: "Microsoft", mailto: "cyns@microsoft.com" }
+ ],
+ // WG
+ wg: "HTML Working Group",
+ wgURI: "http://www.w3.org/html/wg/",
+ wgPublicList: "public-html@w3.org"
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/40318/status",
+ };
+ </script>
<BODY>
- <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 March 2011</h2>
-
-
- <H3>Editors:</H3>
- <P>
- <A href="mailto:sfaulkner@paciellogroup.com">Steve Faulkner</A>, The Paciello Group.</P>
- <P>
- <A href="mailto:cyns@microsoft.com">Cynthia Shelly</A>, Microsoft.</P>
- <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</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>
-</div>
-
- <HR>
- <H2>Abstract</H2>
- <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>
- <H3>Status of This document</H3>
+ <H2 id="abstract">Abstract</H2>
+ <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>
+ <H3 id="sotd">Status of This document</H3>
<P class="warning"><strong>This document is subject to change without notice. This document currently has no formal standing within W3C.</strong></P>
- <P>If you wish to make comments regarding this document, please send them to
- <A href="mailto:public-html-comments@w3.org">public-html-comments@w3.org</A> (<A href="mailto:public-html-comments-request@w3.org?subject=subscribe">subscribe</A>,
- <A href="http://lists.w3.org/Archives/Public/public-html-comments/">archives</A>)
-All feedback is welcome.</P>
- <h2>Table of Contents</h2>
- <ul>
- <li><a href="#aapis">Accessibility APIs</a></li>
- <li><a href="#expose">Exposing HTML features that do not directly map to accessibility API properties</a></li>
- <li><a href="#api-role">HTML element to Accessibility API Role Mapping Matrix</a></li>
- <li><a href="#api-att">HTML attribute to Accessibility API State and Property Mapping Matrix</a></li>
- <li><a href="#calc">Accessible Name and Description calculation</a>
- <ul>
- <li><a href="#calc-iput">input type="text" and textarea element</a></li>
- <li><a href="#inputs">input type="button" , input type="submit",input type="reset" and input type="password"</a> </li>
- <li><a href="#input-image">input type="image"</a></li>
- <li><a href="#control-other">Other form controls</a></li>
- </ul>
- </li>
- <li><a href="#examples">Accessible feature implementation examples</a>
- <ul>
- <li><a href="#examples-sum"><code>summary</code> and <code>details</code> elements</a></li>
- </ul>
- </li>
- </ul>
-
<div id="intro_aapi">
<h3 id="aapis"> Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></h3>
<p>To provide access to desktop GUI applications, assistive technologies originally used heuristic techniques to determine the meaning of the user interface and built an alternative off screen model. For example, a row of labels displayed horizontally near the top of an application window might be a menu. Labels with a border drawn around them might be buttons. Heuristic techniques are not always accurate, however, and require assistive technologies to be updated whenever the software application is updated.</p>
@@ -2709,4 +2701,4 @@
<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>
\ No newline at end of file
+ </BODY></HTML>
Received on Thursday, 14 April 2011 10:02:27 UTC