- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 14 Apr 2011 10:37:31 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv5572
Modified Files:
overview.html
Log Message:
tweaks
Index: overview.html
===================================================================
RCS file: /sources/public/html5/html-api-map/overview.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- overview.html 14 Apr 2011 10:34:20 -0000 1.37
+++ overview.html 14 Apr 2011 10:37:29 -0000 1.38
@@ -80,19 +80,18 @@
<BODY>
<section id="abstract">
- <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>
+ <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>
</section>
<section id="sotd">
<H3>Status of This document</H3>
<P class="warning"><strong>This document is subject to change without notice.</strong></P>
</section>
<section id="intro_aapi">
- <h3>Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></h3>
+ <h3>Introduction: 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>
<p>A much better technique is for the software application to provide the necessary information for interoperability with assistive technology. To meet this need, platform owners have developed specialized interfaces, called accessibility <abbr title="Application Programming Interfaces">APIs</abbr>, which can be used to communicate accessibility information about user interfaces to assistive technologies. </p>
<p>In the case of static Web pages, the Document Object Model (DOM) is used to represent the structure and state of the elements in the document being rendered by a user agent. The elements of the document are organized into a hierarchy of nodes known as the <abbr title="document object model">DOM</abbr> tree. For traditional static Web pages, assistive technologies, such as screen readers, interact with user agents using the <abbr title="Document Object Model">DOM</abbr>. For UI elements that are known to be interactive, such as HTML form elements and desktop applications, assistive technologies may use platform accessibility APIs. </p>
@@ -2715,6 +2714,7 @@
<h3><code>summary</code> and <code>details</code> elements</h3>
<p><span class="note">to do</span></p>
</section>
+</section>
<section id="accessible-description">
<h3>Accessible Description calculation</h3>
<p><span class="note">to do</span></p>
Received on Thursday, 14 April 2011 10:37:32 UTC