- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 14 Apr 2011 10:32:34 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-api-map
In directory hutz:/tmp/cvs-serv4349
Modified Files:
overview.html
Log Message:
re-nest
Index: overview.html
===================================================================
RCS file: /sources/public/html5/html-api-map/overview.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- overview.html 14 Apr 2011 10:31:01 -0000 1.35
+++ overview.html 14 Apr 2011 10:32:31 -0000 1.36
@@ -92,7 +92,7 @@
<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>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>
@@ -105,7 +105,7 @@
<li>Mac OS X Accessibility Protocol</li>
</ul>
<p>If User Agent developers need to expose to other accessibility <abbr title="Application Programming Interfaces">APIs</abbr>, it is recommended that they work closely with the developer of the platform where the <abbr title="application programing interfaces">API</abbr> runs, and assistive technology developers on that platform.</p>
- </div>
+</section>
<section id="expose">
<h3>Exposing HTML features that do not directly map to accessibility <abbr title="application programing interface">API</abbr> properties</h3>
<p>HTML<abbr title="application programing interfaces"></abbr> may have features that are not supported by accessibility <abbr title="Application Programming Interfaces">APIs</abbr> at the time of publication. There is not a one to one relationship between all <abbr title="Accessible Rich Internet Application">features</abbr> and platform accessibility <abbr title="application programing interfaces">APIs</abbr>. When <abbr title="Accessible Rich Internet Application">HTML</abbr> roles, states and properties do not directly map to an accessibility <abbr title="application programing interface">API</abbr>, and there is a method in the <abbr title="application programing interface">API</abbr> to expose a text string, expose the undefined role, states and properties via that method.</p>
Received on Thursday, 14 April 2011 10:32:35 UTC