Accessibility/Plugins: Difference between revisions

Jump to navigation Jump to search
Line 24: Line 24:
Every plugin having UI should embed its accessible tree into existing accessible objects hierarchy of Mozilla.
Every plugin having UI should embed its accessible tree into existing accessible objects hierarchy of Mozilla.


First of all plugin should obtain accessible object created for plugin host element (like html:object) by the following method
Plugin SDK is extended with the helper method used to get accessible object created for plugin host element (like html:object).


<code>
<pre>
NPError NPN_GetPluginAccessible(NPP aInstance, nsIAccessibleTreeNode **aNode);
NPError NPN_GetPluginAccessible(NPP aInstance, nsIAccessibleTreeNode **aNode);
</code>
</pre>


where
The returned accessible object implements <code>nsIAccessibleTreeNode</code> interface used to set up the first child of obtained accessible object.


<pre>
<pre>
Line 39: Line 39:
</pre>
</pre>


and then set up the first child for the obtained accessible object.
The proposed first child accessible must implement <code>nsIAccessible</code> interface.


=Crossplatfrom accessibility code=
=Crossplatfrom accessibility code=
Confirmed users
1,396

edits

Navigation menu