UNO Accessibility API

The UNO Accessibility API (also called UAA in the に引き続いて) is modeled closely after Java Accessibility API in 見解／翻訳／版 1.4 and the the Gnome Accessibility API. The UAA is part of the offapi 事業／計画（する）. You can browse the CVS 古記録 at com/sun/星／主役にする/accessibility or have a look at the documentation here.

代表 of GUI and 文書s

The UAA 代表するs both structure and content of the GUI. Here GUI 含むd the 見解（をとる）s of 文書s that are embedded therein.

Structure

Each 最高の，を越す-level window of the GUI is 代表するd as a tree of accessibility 反対するs. Each accessibility 反対する stands for one GUI element or one 反対する of a 文書見解（をとる）:

Leaves
Some GUI elements are 代表するd by leaves in the tree. Such elements are for example labels and buttons
内部の nodes
Other GUI elements are 代表するd by 内部の nodes and thus have a sub-tree of their own. An example for this are でっちあげる，人を罪に陥れるs, menus and 道具-妨げる／法廷，弁護士業s. Menu items can be both depending of whether they have a sub-menu.
Root
The root of every tree 代表するs a 最高の，を越す level window. This means that the accessibility 代表 of a running OpenOffice.org is 現実に a forest of accessibility trees.

This tree structure is realized by 器具／実施するing the XAccessibleContext interface. To go up に向かって the root of a tree you can get an 反対する's parent. To go 負かす／撃墜するに向かって the leaves of a tree you can retrieve all the children of an 反対する.

Relations

Relations introduce a 第２位 structure that is 独立した・無所属 of the tree 階層制度 created by the parent/child 関係供給するd by the XAccessibleContext interface. Relation 始める，決めるs as returned by the XAccessibleContext::getAccessibleRelationSet() are defined by the XAccessibleRelationSet interface.

Content

Each node of the tree that 器具／実施するs XAccessibleContext gives 接近 to different facets of the 代表するd GUI element or 文書 part. These are

指名する

The 指名する is a localized string and 行為／法令／行動するs as short, one word description, this is e.g. the text 陳列する，発揮するd on a button.

役割

The 肉親，親類d of 支配（する）／統制する or 文書 part. E.g. the 役割 of a button is "button". With the AccessibleRole collection of constants there is a 始める，決める of predefined 役割s that is suitable for the elements of the GUI 反して there are no (not yet) 役割s for the direct support of the 文書.

description

A localized string description that is longer and more 明確な／細部 than the 指名する.

明言する／公表する

明言する／公表するs of GUI elements as 述べるd by the AccessibleStateType constants collection can be for example "active", "hidden", or "checked". Again there is a predefined 始める，決める of 明言する／公表するs suitable for GUI elements but maybe not 十分な to 代表する明言する／公表するs of 文書 parts.

活動／戦闘s

This active part of a node content can for instance open a pop up window with a 状況極度の慎重さを要する menu. Another example are 付加 navigational 命令（する）s. 活動／戦闘s are 代表するd by the AccessibleRole service. In general there should be as few 活動／戦闘s as possible. It is better to 申し込む／申し出付加 functionality through the clasical means of the GUI.

graphical 代表

The graphical 代表 of an accessible 反対する is exposed by the XAccessibleComponent interface. It can be queried for instance for its bounding-box or for the child node at a given point on the 審査する.

content

The actual content of a node of the accessibility tree can have different forms:

Text is 代表するd by the interfaces XAccessibleText (read only) and XAccessibleEditableText. There is also the interface XAccessibleHypertext for texts that 含む／封じ込める hyperlinks.
（米）棚上げする／（英）提議するs are 代表するd by the interface XAccessibleTable.
Images are 代表するd by the interface XAccessibleImage.
Simple 数値／数字による values, like the position of a slider or the value of a spin box are 代表するd by the XAccessibleValue interface.

Events

The tree modeled by the UAA is not a static data structure. Because of scrolling the 文書 window, changing its content, or 修正するing the contents of GUI 支配（する）／統制するs, the structure and content of 選び出す／独身 nodes and sub-trees is 絶えず changing. These changes are 通知するd to the AT by sending events to 登録（する）d listeners (の中で them the AT). The 肉親，親類d of event that is sent for a 明確な／細部 change depends on the UAA interfaces that the node that 代表するs the 修正するd 反対する does support and on the actual 実施 of these interfaces. Listeners to accessibility events 器具／実施する the XAccessibleEventListener interface while 放送者s 器具／実施する the XAccessibleEventBroadcaster interface. Events are AccessibleEventObject structures, their types are 述べるd in the AccessibleEventId constants group.

独立した・無所属実施 of the UAA

The XAccessible interface 許すs the decoupling of the 実施 of the UAA from the 実施 of the 残り／休憩（する） of the UNO API. Its only method, getAccessibleContext(), returns an 反対する that 器具／実施するs the AccessibleContext service. This may or may not be done by a class other than the one that 器具／実施するs the XAccessible interface. This has the big advantage, that the 存在するing API 実施 needs only 極小の modifications.

Differences between the Accessibility APIs of UNO and Java

Here is a 名簿（に載せる）／表（にあげる） of major differences between the UNO and the Java Accessibility APIs:

Java interfaces AccessibleComponent and AccessibleExtendedComponent have been 配列し直すd into the UAA interfaces XAccessibleComponent and XAccessibleExtendedComponent.
Java interfaces AccessibleTable and AccessibleExtendedTable have been 合併するd into the 選び出す／独身 UNO interface XAccessibleTable.
Java interfaces AccessibleText and AccessibleEditableText have been 配列し直すd into the UAA interfaces XAccessibleText and XAccessibleEditableText to better 反映する the read only and read/令状接近 to text.
The Java class AccessibleBundle is not supported, because it is not necessary in the UNO 環境.
The Java class AccessibleResourceBundle is not supported, because it is deprecated in the Java API.
The Java classes AccessibleRelation, AccessibleRole, and AccessibleState are realized by UNO constants collections AccessibleRelationType, AccessibleRole, and AccessibleStateType 予定 to different API designs.
The Java interface AccessibleIcon has been 改名するd into the UNO interface XAccessibleImage to 代表する its more general approach.
The methods of the Java class AccessibleHyperlink regarding 活動／戦闘s have been 除去するd. Instead the UNO service AccessibleHyperlink supports in 新規加入 to the interface XAccessibleHyperlink also the XAccessibleAction interface.

Documentation of the UNO Accessibility API

More 詳細（に述べる）s of the UAA can be 設立する in the API 言及／関連.

The services that expose 使用／適用明確な／細部詳細（に述べる）s of the UAA can be 設立する here for the GUI, Writer, Calc, Draw/Impress, and Chart.