<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 26/02/15 13:51, Dhairyashil Bhosale
wrote:<br>
</div>
<blockquote
cite="mid:CANYOZpvP+Cgab_7XbYp9f62Oc_2QLXyvs1RELZtifuxp61fXQA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi all,<br>
<br>
</div>
I am new to At-SPI-1.0/2.0, I just
successfully initialized the At-spi-init() method and
just print the name of focused application running on
GNOME. I have a lot of queries like:<br>
<br>
</div>
1) Like in At-SPI-1.0 we set
accessibility setting like
"putenv("GNOME_ACCESSIBILITY=1");",<b> </b>this but in
AT-SPI-2.0 what parameters we have to set for enabling
accessibility setting, for the time being I start ORCA
screen reader and then run AT-SPI-2.0 demo example , so
What parameters we have to set for enabling all
accessibility setting in AT-SPI2.0?<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
First, it is not at-spi-1.0 vs at-spi-2.0. For example at-spi2-2.0
behaviour at the beginning was basically the same that at-spi1.0.
Enable accessibility is something somewhat more broader.<br>
<br>
Unfortunately there is not a single answer for your question. How to
enable (if needed) accessibility depends on the distro that you are
using. During all this years, there were different ways to enable
the accessibility support. One is the environment variable you
mention, and there was also the gsetting "toolkit-accessibility".
You can check this one like this:<br>
<br>
gsettings get org.gnome.desktop.interface "toolkit-accessibility"<br>
<br>
With a several recent-enough-distro, it would be enough to just set
that gsetting to true. But in any case, you should be able to enable
accessibility using the universal access settings dialog.<br>
<br>
If you want a distro-independent answer, this is how it works on
GNOME upstream:<br>
* Since 2012 accessibility is enabled on default. So for gtk3,
gnome-shell and others, accessibility (so at-spi2) is always
enabled. You don't need to do anything.<br>
* Old applications, mostly using gtk2, are still affected by
toolkit-accessibility gsetting.<br>
<br>
Rationale and some extra details on this email [1].<br>
<br>
<blockquote
cite="mid:CANYOZpvP+Cgab_7XbYp9f62Oc_2QLXyvs1RELZtifuxp61fXQA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div><br>
</div>
2) I am trying to make java
application accessible to orca screen reader using JNI for
calling At-spi's method, but in AT-SPI there are all get
method like <br>
" atspi_get_text() " like this, so in simple java ,python or
gtk application How should I implement the At-SPI-2.0 means
from application side we have to set somthing? <br>
</div>
</div>
</div>
</blockquote>
<br>
You are in the wrong side of the application. libatspi is the client
server side library, used to write AT applications like Orca. Or in
other words, libatspi is just used to get the info. Your approach
would be valid if you want to write a screen reader using Java, that
as far as I see, is not what you intend.<br>
<br>
You would need to explore the server side (more below).<br>
<br>
<blockquote
cite="mid:CANYOZpvP+Cgab_7XbYp9f62Oc_2QLXyvs1RELZtifuxp61fXQA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
3) I am trying to call AT-SPI from
java using JNI interface for making java application
accessible to Orca screen reader, but when I run the java
application, the Orca can not read the title bar or can't
access that application, even I tried the <span class="">Java
Accessibility API</span>(JAAPI).<br>
</div>
</div>
</blockquote>
<br>
Again, libatspi is the client side library. It is already
implemented, in order to get info from the accessibility APIs. So
their purpose is writing ATs, not to expose the applications<br>
<br>
<blockquote
cite="mid:CANYOZpvP+Cgab_7XbYp9f62Oc_2QLXyvs1RELZtifuxp61fXQA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div> SO HOW TO MAKE JAVA APPLICATION
ACCESSIBLE TO ORCA SCREEN READER OR OTHER ASSISTIVE TECH.<br>
</div>
</div>
</blockquote>
<br>
Take a look to java-atk-wrapper:<br>
<a class="moz-txt-link-freetext" href="https://git.gnome.org/browse/java-atk-wrapper">https://git.gnome.org/browse/java-atk-wrapper</a><br>
<br>
This library wraps Java applications (using JNI and all that stuff),
exposing it as another ATK implementation (like those available on
gtk, clutter, etc). Then it uses the server side library at-spi2-atk
to expose the information using at-spi2 APIs. So instead of starting
from scratch in order to make java applications accessible, probably
it would be better if you collaborate with an already started
module.<br>
<br>
Best regards<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://mail.gnome.org/archives/desktop-devel-list/2012-June/msg00035.html">https://mail.gnome.org/archives/desktop-devel-list/2012-June/msg00035.html</a><br>
<br>
<pre class="moz-signature" cols="72">--
Alejandro Piñeiro (<a class="moz-txt-link-abbreviated" href="mailto:apinheiro@igalia.com">apinheiro@igalia.com</a>)</pre>
</body>
</html>