incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r799368 [42/42] - in /websites/staging/ooo-site/trunk/content/ui/accessibility: ./ apiref/ apiref/com/ apiref/com/sun/ apiref/com/sun/star/ apiref/com/sun/star/awt/ apiref/com/sun/star/beans/ apiref/com/sun/star/lang/ apiref/com/sun/star/un...
Date Mon, 28 Nov 2011 00:46:10 GMT
Added: websites/staging/ooo-site/trunk/content/ui/accessibility/proposal-writer.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/ui/accessibility/proposal-writer.html (added)
+++ websites/staging/ooo-site/trunk/content/ui/accessibility/proposal-writer.html Mon Nov
28 00:45:46 2011
@@ -0,0 +1,253 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and
Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<H2 CLASS="western">Writer Accessibility</H2>
+<P CLASS="western">Proposal</P>
+<P CLASS="western">by Michael Brauer (<A HREF="mailto:michael.brauer@sun.com">michael.brauer@sun.com</A>)
+</P>
+<P CLASS="western">last modification on <SDFIELD TYPE=DATETIME SDVAL="37236.6217534722"
SDNUM="1033;1033;MMMM D, YYYY">December 11, 2001</SDFIELD></P>
+<H3 CLASS="western">1. Introduction</H3>
+<P CLASS="western">This paper contains a proposal how
+StarOffice/OpenOffice.org Writer (and Writer/Web) documents can be
+made accessible by using the UNO Accessibility API (UAA). 
+</P>
+<P CLASS="western">As stated in the <A HREF="http://ui.openoffice.org/accessibility/docrep-guidelines.html">guidelines
+of document representation</A>, the accessible objects tree for
+Writer documents represents the current view of the document as it
+does for any other application, too. 
+</P>
+<P CLASS="western">It is obvious that the most important accessible
+objects are the ones that contain the document's text, or to be more
+precise, support the AccessibleEditableText service. A  real
+difficulty however results from the fact that the text that is
+visible on the screen might in fact be part of very different parts
+of the document. If a document for instance contains headers and
+footers for pages, text from a footer, a header and text from the the
+body region of two different pages might be visible simultaneously.
+And things might become more complex if columns, text-boxes and
+footnotes get involved.</P>
+<P CLASS="western">Beside text that might be contained in very
+different objects, the view of a Writer document might also contain
+tables, images, drawings and OLE objects.</P>
+<P CLASS="western">This draft first gives an overview of the
+accessible object tree for Writer documents, followed by some
+explanations what reasons led to the structure. After that, a
+detailed specification follows.</P>
+<H3 CLASS="western">1. Overview</H3>
+<P CLASS="western">The root accessible object  (i.e. the one of the
+window that contains view of the Writer document) has a child object 
+for 
+</P>
+<UL>
+	<LI><P CLASS="western">the body text of the document (i.e. the text
+	that is distributed to the pages of a text document), except for the
+	very rare cases where no body text is visible at all;</P>
+	<LI><P CLASS="western">every page header and every page footer that
+	is visible;</P>
+	<LI><P CLASS="western">every footnote and endnote that is visible;
+	and</P>
+	<LI><P CLASS="western">every text-box, image, OLE object and drawing
+	that is visible;</P>
+</UL>
+<P CLASS="western">Teseobjects are called <EM>area objects</EM>
+within this proposal.</P>
+<P CLASS="western">There is neither an object for pages nor for
+columns. This especially means that there is exactly one object for
+body text that is visible currently, even if the text appears on
+different pages.</P>
+<P CLASS="western">With the exception of  text-boxes, images, OLE
+objects and drawings the only service area objects support is
+AccessibleContext. This especially means  that there is no
+AccessibleComponent service available and therefor no geometrical
+information. 
+</P>
+<P CLASS="western">Text-boxes, images, OLE objects and drawings
+however do support the AccessibleComponent service. They are children
+of the root object, regardless whether they in fact are bound to a
+page, a paragraph, etc.</P>
+<P CLASS="western">With the exception of images, OLE objects and
+drawings, area objects have children that are either paragraph
+fragment objects or table fragment object.</P>
+<P CLASS="western">A <EM>paragraph fragment object</EM> supports the
+AccessibleEditableText and AccessibleComponent services<A CLASS="sdfootnoteanc" NAME="sdfootnote1anc"
HREF="#sdfootnote1sym"><SUP>1</SUP></A>.
+It either represents the text of a paragraph or the text of a part of
+a paragraph, if the paragraph contains page or column breaks. In the
+later case it represents exactly the paragraph's text that is
+displayed at certain page or within a certain column. In other words,
+a single paragraph might be represented by more than one paragraph
+fragment object if and only if contains page or column breaks. But a
+paragraph fragment object never contains text from more than one
+paragraphs.</P>
+<P CLASS="western">A <EM>table fragment object</EM> supports the
+AccessibleTable service. It represents the fragment of a table that
+is displayed on one page or in one column. The table cell objects
+themselves have paragraph fragment objects as children again.</P>
+<P CLASS="western">All area objects contain children only for
+paragraphs and tables (or fragments of them) that are at least
+partially visible. If a page header for instance contains two
+paragraphs, but only one of them is visible, then the page header's
+area object has one child only<A CLASS="sdfootnoteanc" NAME="sdfootnote2anc" HREF="#sdfootnote2sym"><SUP>2</SUP></A>.</P>
+<P CLASS="western">Paragraph as well as table fragment objects that
+are partially visible contain their off-screen parts, too. This means
+that a paragraph fragment object contains text that is not displayed
+currently and a table fragment object contains cells that are not
+displayed currently.</P>
+<H3 CLASS="western">2. Design Influences</H3>
+<P CLASS="western">This section describes some concepts and issues
+that influenced the accessible object context tree described in the
+previous section.</P>
+<H4 CLASS="western">Text Flows</H4>
+<P CLASS="western">As said above, the text that is shown in the view
+of a Writer document might in fact be contained in different
+unrelated parts of a document. Within this proposal, these parts are
+called <EM>text flows</EM>. The following text flows exist:</P>
+<UL>
+	<LI><P CLASS="western">page headers</P>
+	<LI><P CLASS="western">page footers</P>
+	<LI><P CLASS="western">foot- and endnotes</P>
+	<LI><P CLASS="western">text boxes</P>
+	<LI><P CLASS="western">table cells</P>
+	<LI><P CLASS="western">text contained in drawings</P>
+	<LI><P CLASS="western">body text i.e. the text that is distributed
+	to the page's body regions.</P>
+</UL>
+<P CLASS="western">On the screen, the different text flows can be
+distinguished by gaps or lines between them, or by other hints like
+background colors. For the accessibility API a simple way to
+distinguish them should exist, too. This for instance enables voice
+tools to read the body text of a document without mixing it up with
+headers, footers, footnotes and so on.</P>
+<P CLASS="western">An appropriate way to get a differentiation
+between text flows seems to be the parent/child relation the 
+XAccessibleContext interface offers. This requires that</P>
+<UL>
+	<LI><P CLASS="western">a single object that supports the
+	AccessibleEditableText service must not represent text from
+	different text flows.</P>
+	<LI><P CLASS="western">A single object that supports the
+	AccessibleContext service does not have children that represent text
+	from different text flow.</P>
+</UL>
+<P CLASS="western">The area objects exactly make use of these
+parent/child relation to differ between text flows. To get a unique
+access to the text flow's text is seems to be reasonable to use area
+objects even if if they contain one child only.</P>
+<H4 CLASS="western">Pages And Columns</H4>
+<P CLASS="western">If a document is not displayed in the Online
+Layout mode,  then its body text flow is distributed to several
+pages. On the screen, the different pages are visualized by a gray
+bars between them. 
+</P>
+<P CLASS="western">There seems to be no requirement for having an
+accessible object for pages itself. But in many cases, it also seems
+not to be convenient that text that is accessible by a single
+AccessibleEditableText service contains a page break, that is,
+represents text from two different pages. This is the case if the
+page before the page break contains a footer and/or footnotes, or if
+the page behind the page break contains a header.  If the 
+AccessibleEditableText for the body text would represent the text of
+both pages, then its bounding box would overlap with the ones of the
+headers, footers or footnotes.</P>
+<P CLASS="western">Moreover it does not seem to be convenient that an
+AccessibleEditableText represents text of different columns. The
+simple reason for this is that an  AccessibleEditableText  that
+contains text of more than one column would require more than one
+bounding box.</P>
+<P CLASS="western">Like for pages, there also seems to be no
+requirement for having an accessible object for columns themselves.</P>
+<H4 CLASS="western">Paragraphs</H4>
+<P CLASS="western">The third thing that has to taken into account
+when defining the accessible object tree are paragraphs. On the one
+hand, paragraphs divide text into fragments at reasonable positions.
+On the other hand, and that's more important, they assign certain
+semantics to text, like being a heading or an item of a bullet list.
+These semantics put a structure at the document that is at least
+helpful for navigation in a document. Therefor it seems to be
+reasonable to not have text of more than one paragraph within one
+accessible object, and to include the structural information a
+paragraph carries into either the object's description or role.</P>
+<P CLASS="western">The opposite however does not hold. A paragraph's
+text has to be distributed to more than one object if the paragraph
+contains a page or column break. Therefor there will be accessible
+objects for paragraph portions in fact, the paragraph fragment
+objects.</P>
+<P CLASS="western">Though the guidelines state that text can be
+splitted into on- and off-screen parts, it seems not to be convenient
+to do that for paragraph portions. This means that text that is not
+visible on the scroll might be accessible through an
+AccessibleEditableText service, provided that also some text of the
+same service is displayed. There are two reasons for that, that both
+have to do with the fact the each paragraph fragment object  also
+supports the AccessibleComponent service that gives access to its
+screen coordinates. First of all, that's the same behavior has for
+any other accessible object that supports the AccessibleCpmponet
+service. Secondly, and more important, hiding the non visible text
+fragments would have the result that a simple scroll action might
+change the objects text. 
+</P>
+<H3 CLASS="western">3. Details</H3>
+<P CLASS="western"><EM>To be continued ...</EM></P>
+<DIV ID="sdfootnote1">
+	<P CLASS="sdfootnote-western"><A CLASS="sdfootnotesym" NAME="sdfootnote1sym" HREF="#sdfootnote1anc">1</A>Editor's
+	note: There is a open issue with read-only and generated text within
+	paragraphs, like fields and generated hyphens. Therefor it might be
+	necessary that the paragraph fragment objects do not support
+	AccessibleEditableText themselves, but have children that either
+	support AccessibleText or AcessibleEditableText.</P>
+</DIV>
+<DIV ID="sdfootnote2">
+	<P CLASS="sdfootnote-western"><A CLASS="sdfootnotesym" NAME="sdfootnote2sym" HREF="#sdfootnote2anc">2</A>That's
+	in fact the reason these objects are called header area objects
+	instead of header objects. They do not represent a header, but an
+	area on the screen there a header is displayed.</P>
+</DIV>
+</BODY>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache
CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation
(ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that
the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF
projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate
that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache
Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/ui/accessibility/quickstart.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/ui/accessibility/quickstart.html (added)
+++ websites/staging/ooo-site/trunk/content/ui/accessibility/quickstart.html Mon Nov 28 00:45:46
2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and
Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache
CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation
(ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that
the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF
projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate
that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache
Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/ui/accessibility/unoapi.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/ui/accessibility/unoapi.html (added)
+++ websites/staging/ooo-site/trunk/content/ui/accessibility/unoapi.html Mon Nov 28 00:45:46
2011
@@ -0,0 +1,339 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and
Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h2>UNO Accessibility API</h2>
+
+<p>The UNO Accessibility API (also called UAA in the following) is modeled
+closely after Java Accessibility API in version 1.4 and the the Gnome
+Accessibility API.  The UAA is part of the offapi project.  You can browse
+the CVS archive at <a
+href="http://ui.openoffice.org/source/browse/api/offapi/com/sun/star/accessibility/"
+title="Browse the IDL source files of the UNO Accessibility API"
+>com/sun/star/accessibility</a> or have a look at the documentation <a 
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/module-ix.html"
+title="Documentation: UAA reference">here</a>. </p>
+
+<h3>Representation of GUI and documents</h3>
+
+<p>The UAA represents both <em>structure</em> and <em>content</em>
of the
+  GUI.  Here GUI included the views of documents that are embedded
+  therein.</p>
+
+
+<h4>Structure</h4>
+
+<p>Each top-level window of the GUI is represented as a tree of
+  accessibility objects.  Each accessibility object stands for one GUI
+  element or one object of a document view:
+<ul><li><b>Leaves</b><br>  Some GUI elements are
+  represented by  leaves in the tree.  Such elements are for example labels and
+    buttons</li>
+<li><b>Internal nodes</b><br>
+  Other GUI elements are represented by internal nodes and thus have a
+  sub-tree of their own.  An example for this are frames, menus and
+  tool-bars.  Menu items
+  can be both depending of whether they have a sub-menu.</b></li>
+<li><b>Root</b><br>
+  The root of every tree represents a top level window.  This means that the
+  accessibility representation of a running OpenOffice.org is actually a
+  forest of accessibility trees.
+</li>
+</ul>
+
+<p>This tree structure is realized by implementing the
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleContext.html"
+   title="Documentation of the XAccessibleContext interface"><code>XAccessibleContext</code></a>
interface.  To go up
+   towards the root of a tree you can get an object's parent.  To go down
+   towards the leaves of a tree you can retrieve all the children of an
+   object.</p>
+
+<h5>Relations</h5>
+Relations introduce a secondary structure that is independent of the tree
+hierarchy created by the parent/child relationship provided by the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleContext.html"
+   title="Documentation of the XAccessibleContext interface"><code>XAccessibleContext</code></a>
interface.  Relation sets as
+returned by the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleContext.html#getAccessibleRelationSet"
+title="Documentation of the XAccessibleContext::getAccessibleRelationSet() method"><code>XAccessibleContext::getAccessibleRelationSet()</code></a>
are defined
+ by the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleRelationSet.html"
+   title="Documentation of the XAccessibleRelationSet interface"><code>XAccessibleRelationSet</code></a>
interface.
+
+<h4>Content</h4>
+
+<p>Each node of the tree that implements <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleContext.html"
+   title="Documentation of the XAccessibleContext interface"><code>XAccessibleContext</code></a>
gives access to different
+   facets of the represented GUI element or document part.  These are
+
+<dl>
+
+<dt>name</dt><dd>The name is a localized string and acts as short, one
word
+description, this is e.g. the text displayed on a button.</dd>
+
+<dt>role</dt> <dd>The kind of control or document part.  E.g. the role
of a
+button is "button".  With the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleRole.html"
+   title="Documentation of the AccessibleRole constants group"><code>AccessibleRole</code></a>
collection of
+constants there is a set of predefined roles that is suitable for the elements
+of the GUI whereas there are no (not yet) roles for the direct support of the
+document.</dd>
+
+<dt>description</dt><dd>A localized string description that is longer and
more
+specific than the name.</dd>
+
+<dt>state</dt><dd>States of GUI elements as described by the
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleStateType.html"
+   title="Documentation of the AccessibleStateType constants group"><code>AccessibleStateType</code></a>
constants collection can be for example
+"active", "hidden", or "checked".  Again there is a predefined set of states
+suitable for GUI elements but maybe not sufficient to represent states of
+document parts.</dd>
+
+<dt>actions</dt><dd>This active part of a node content can for instance
open a
+pop up window with a context sensitive menu.  Another example are additional
+navigational commands.  Actions are represented by the
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleRole.html"
+   title="Documentation of the AccessibleRole constants group"><code>AccessibleRole</code></a>
service.  In general there should be as few
+actions as possible.  It is better to offer additional functionality through
+the clasical means of the GUI.</dd>
+
+<dt>graphical representation</dt><dd>The graphical representation of an
+accessible object is exposed by the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleComponent.html"
+   title="Documentation of the XAccessibleComponent interface"><code>XAccessibleComponent</code></a>
interface.
+It can be queried for instance for its bounding-box or for the child node at a
+given point on the screen.</dd>
+
+<dt>content</dt><dd>The actual content of a node of the accessibility tree
can
+have different forms:
+<ul> 
+
+<li>Text is represented by the interfaces <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleText.html"
+   title="Documentation of the XAccessibleText interface"><code>XAccessibleText</code></a>
(read
+only) and <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleEditableText.html"
+   title="Documentation of the XAccessibleEditableText interface"><code>XAccessibleEditableText</code></a>.
 There is also the interface
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleHypertext.html"
+   title="Documentation of the XAccessibleHypertext interface"><code>XAccessibleHypertext</code></a>
for texts that contain
+hyperlinks.</li>
+
+<li>Tables are represented by the interface <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleTable.html"
+   title="Documentation of the XAccessibleTable interface"><code>XAccessibleTable</code></a>.</li>
+
+<li>Images are represented by the interface
+<a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleImage.html"
+   title="Documentation of the XAccessibleImage interface"><code>XAccessibleImage</code></a>.</li>
+
+<li>Simple numerical values, like the position of a slider or the value of a
+spin box are represented by the <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleValue.html"
+   title="Documentation of the XAccessibleValue interface"><code>XAccessibleValue</code></a>
+interface.</li>
+
+</ul>
+
+</dl>
+</p>
+
+
+
+
+<h3>Events</h3>
+
+<p>The tree modeled by the UAA is not a static data
+structure.  Because of scrolling the document window, changing its content, or
+modifying the contents of GUI controls, the structure and content of single
+nodes and sub-trees is constantly changing.  These changes are notified to the
+AT by sending events to registered listeners (among them the AT).  The kind of
+event that is sent for a specific change depends on the UAA interfaces that
+the node that represents the modified object does support and on the actual
+implementation of these interfaces.  Listeners to accessibility events
+implement the <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleEventListener.html"
+   title="Documentation of the XAccessibleEventListener interface"><code>XAccessibleEventListener</code></a>
interface while broadcasters
+implement the 
+<a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleEventBroadcaster.html"
+   title="Documentation of the XAccessibleEventBroadcaster interface"><code>XAccessibleEventBroadcaster</code></a>
interface.
+Events are <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleEventObject.html"
+   title="Documentation of the AccessibleEventObject structure"><code>AccessibleEventObject</code></a>
structures, their types
+   are described in the <a
+   href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleEventId.html"
+   title="Documentation of the AccessibleEventId constants group"><code>AccessibleEventId</code></a>
constants group.</p>
+
+
+
+
+<h3>Independent implementation of the UAA</h3>
+
+<p>The <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessible.html"
+   title="Documentation of the XAccessible interface"><code>XAccessible</code></a>
interface allows the decoupling
+   of the implementation of the UAA from the implementation of the rest of
+   the UNO API.  Its only method, <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessible.html#getAccessibleContext"
+   title="Documentation of the XAccessible::getAccessibleContext() method"><code>getAccessibleContext()</code></a>,
+   returns
+   an object that implements the <code>AccessibleContext</code> service.
+   This may or may not be done by a class other than the one that implements the
+   <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessible.html"
+   title="Documentation of the XAccessible interface"><code>XAccessible</code></a>
interface.  This has the big advantage, that the
+   existing API implementation needs only minimal modifications.</p>
+
+
+
+
+
+<h3>Differences between the Accessibility APIs of UNO and Java</h3>
+
+Here is a list of major differences between the UNO and the Java Accessibility APIs:
+
+<ul>
+
+<li><p>Java interfaces <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleComponent.html"
+title="Documentation of the JAA AccessibleComponent interface"><code>AccessibleComponent</code></a>
and <a href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleExtendedComponent.html"
+title="Documentation of the JAA AccessibleExtendedComponent interface"
+><code>AccessibleExtendedComponent</code></a> have been rearranged into
the UAA interfaces <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleComponent.html"
+title="Documentation of the XAccessibleComponent interface"><code>XAccessibleComponent</code></a>
and <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleExtendedComponent.html"
+title="Documentation of the XAccessibleExtendedComponent interface"><code>XAccessibleExtendedComponent</code></a>.</p></li>
+
+<li><p>Java interfaces <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleTable.html"
+title="Documentation of the JAA AccessibleTable interface"><code>AccessibleTable</code></a>
and
+<a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleExtendedTable.html"
+title="Documentation of the JAA AccessibleExtendedTable interface"><code>AccessibleExtendedTable</code></a>
have been merged into the single
+UNO interface <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleTable.html"
+title="Documentation of the XAccessibleTable interface"><code>XAccessibleTable</code></a>.</p></li>
+
+<li><p>Java interfaces <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleText.html"
+title="Documentation of the JAA AccessibleText interface"><code>AccessibleText</code></a>
and
+<a href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleEditableText.html"
+title="Documentation of the JAA AccessibleEditableText interface"
+><code>AccessibleEditableText</code></a> have been rearranged into the
UAA interfaces <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleText.html"
+title="Documentation of the XAccessibleText interface"><code>XAccessibleText</code></a>
and <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleEditableText.html"
+title="Documentation of the XAccessibleEditableText interface"><code>XAccessibleEditableText</code></a>
to better reflect the read only and
+  read/write access to text.</p></li>
+
+
+<li><p>The Java class <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleBundle.html"
+title="Documentation of the JAA AccessibleBundle interface"><code>AccessibleBundle</code></a>
is not supported, because it is
+  not necessary in the UNO environment.</p></li> 
+
+<li><p>The Java class <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleResourceBundle.html"
+title="Documentation of the JAA AccessibleResourceBundle interface"><code>AccessibleResourceBundle</code></a>
is not supported, because it
+  is deprecated in the Java API.</p></li>
+
+<li><p>The Java <em>classes</em> <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleRelation.html"
+title="Documentation of the JAA AccessibleRelation interface"><code>AccessibleRelation</code></a>,
+<a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleRole.html"
+title="Documentation of the JAA AccessibleRole interface"><code>AccessibleRole</code></a>,
and <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleState.html"
+title="Documentation of the JAA AccessibleState interface"><code>AccessibleState</code></a>
are realized
+  by UNO <em>constants collections</em> 
+<a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleRelationType.html"
+title="Documentation of the AccessibleRelationType constants collection"><code>AccessibleRelationType</code></a>,
<a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleRole.html"
+title="Documentation of the AccessibleRole constants collection"><code>AccessibleRole</code></a>,
and <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/AccessibleStateType.html"
+title="Documentation of the AccessibleStateType constants collection"><code>AccessibleStateType</code></a>
+due to different API designs.</p></li>
+
+<li><p>The Java interface <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleIcon.html"
+title="Documentation of the JAA AccessibleIcon interface"><code>AccessibleIcon</code></a>
has been renamed into
+  the UNO interface <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleImage.html"
+title="Documentation of the XAccessibleImage interface"><code>XAccessibleImage</code></a>
to represent its more general approach.</p></li>
+
+<li><p>The methods of the Java class <a
+href="http://java.sun.com/j2se/1.4.1/docs/api/javax/accessibility/AccessibleHyperlink.html"
+title="Documentation of the JAA AccessibleHyperlink interface"><code>AccessibleHyperlink</code></a>
regarding actions have been
+  removed.  Instead the UNO service <code>AccessibleHyperlink</code> supports
+  in addition to the interface <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleHyperlink.html"
+title="Documentation of the XAccessibleHyperlink interface"><code>XAccessibleHyperlink</code></a>
also the
+  <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/XAccessibleAction.html"
+title="Documentation of the XAccessibleAction interface"><code>XAccessibleAction</code></a>
interface.</p></li>
+
+</ul>
+
+
+
+<h3>Documentation of the UNO Accessibility API</h3>
+
+<p>More details of the UAA can be found in the <a 
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/accessibility/module-ix.html"
+title="Documentation: UAA reference">API reference</a>.
+
+<p>The services that expose application specific details of the UAA can be
+  found here for the  <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/awt/module-ix.html" 
+title="Services of the UAA implementation used by the GUI">GUI</a>, <a
+href="http://api.openoffice.org/docs/common/ref/com/sun/star/text/module-ix.html" 
+title="Services of theUAA implementation used by the Writer">Writer</a>, 
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/sheet/module-ix.html"

+title="Services of the UAA implementation used by the Calc">Calc</a>, 
+<a href="http://api.openoffice.org/docs/common/ref/com/sun/star/drawing/module-ix.html"

+title="Services of the UAA implementation used by Draw/Impress">Draw/Impress</a>,
+and <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/chart/module-ix.html"

+title="Services of the UAA implementation used by Chart">Chart</a>.</p>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache
CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation
(ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that
the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF
projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate
that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache
Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/ui/accessibility/whitepaper.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/ui/accessibility/whitepaper.html (added)
+++ websites/staging/ooo-site/trunk/content/ui/accessibility/whitepaper.html Mon Nov 28 00:45:46
2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and
Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache
CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation
(ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that
the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF
projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate
that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache
Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>



Mime
View raw message