y it.
You and the whole accessibility community are extremely nice to work
with. Thanks!
--
Luca Saiu
HYPRA -- Progressons ensemble : http://hypra.fr
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
ure that even GTK+ has no specific knowledge about Orca
keybindings. What am I missing? Is there a way for an application to
notify the accessibility subsystem that an appropriate but unspecified
set of keyboard (or mouse?) events is to be trapped?
Thanks,
--
Luca Saiu
HYPRA -- Progressons ensemble
ding
g_signal_emit_by_name (main_accessible, "state-change", "focused", 1);
does indeed improve the situation a lot. There are still a few
behaviors I don't understand, but now Orca can see my program state
independently from when it starts.
> https://wiki.gnome.org/Accessi
Hello Alejandro.
On 2015-07-01 at 15:11, Alejandro Piñeiro wrote:
> After re-reading my email, it is not exactly really well-structured.
Don't worry, it was perfectly clear. I appreciate you taking the time
to write such a thorough response.
Regards,
--
Luca Saiu
HYPRA -- Pro
y be, to your expert eye. What I am missing? Shall I
emit some ATK signals I'm currently forgetting at some point?
Thank you very much for your help, and for your work.
[1] http://osdir.com/ml/debian-accessibility/2015-07/msg0.html
--
Luca Saiu
HYPRA -- Progressons ensemble : http://
, I am supposed to always just call set_
methods, and not emit signals; when implemented correctly those methods
would emit signals as needed.
This I deduced from the source code. Would you please confirm that my
understanding is correct?
Thanks in advance,
--
Luca Saiu
HYPRA -- Progressons e
le. But of course, if that is currently needed
because of temporary hacks, we can work on that.
Anyway my idea, possibly not yet correctly implemented, consists in
having a main ATK widget implementing AtkText. Do I need to generate
(or handle) any particular event, for example at focus?
Thanks
ng doesn't appear in the Marco source code. Which criterion
should I satisfy, exactly, for the screen reader not to give up?
Thanks in advance,
[1] http://osdir.com/ml/debian-accessibility/2015-06/msg00033.html
--
Luca Saiu
HYPRA -- Progressons ensemble : http://hypra.fr
--
To UNSUBSCRI
be called
or for my application to be recognized as "accessible" when I switch to
its window. For that I'm still trying to explicitly emit signals via
g_signal_emit_by_name. Do you think that's the wrong way ?
Thanks,
--
Luca Saiu
HYPRA -- Progressons ensemble : http://hypra.
isting) interface with an application containing a window
containing a label, just to show the label? I can if needed, but I'd
prefer not to have to implement a different set of interface for the
window and the label. Am I completely free in this or shall I follow
some fixed schema?
Thanking
t-spi2-atk/tests. They are still unit tests, but they set all the
> stack. Take a look to see if it is what you need.
Will do. Thanks again.
--
Luca Saiu
HYPRA -- Progressons ensemble : http://hypra.fr
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subje
On 2015-06-22 at 03:21, Luca Saiu wrote:
> I've played with ATK but I'm sure there's something I don't get. The
> most comprehensible examples I've found are in the atk testsuite, but
> those are obviously intended as unit tests, and running them has no
> inf
suggestion for my case? Thanks,
[1]
https://developer.gnome.org/accessibility-devel-guide/stable/dev-start-5.html.en
[2] https://accessibility.kde.org/developer/atk.php
[3] https://bugs.openjdk.java.net/browse/JDK-8067481
--
Luca Saiu
HYPRA -- Progressons ensemble : http://hypra.fr
--
To UNSUB
On 2015-04-23 at 10:26, Samuel Thibault wrote:
> Luca Saiu, le Thu 23 Apr 2015 09:31:55 +0200, a écrit :
>> I guess it's harder than just cat'ting a string to the Braille terminal
>> device file; if not, how do I find the device, querying brltty?
>
> Wha
solution would be
widely considered unorthodox and ugly, but I'd be surprised if nobody
ever thought of it before me.
I guess it's harder than just cat'ting a string to the Braille terminal
device file; if not, how do I find the device, querying brltty?
Thanking you in advance,
--
L
Thanks,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87iocp5zpj@hypra.fr
anks a lot for the information,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87mw215zxw@hypra.fr
e
device.
Would you happen to have any tips for further investigation?
Thanks,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
respect to accessibility. The only nontrivial point would be
ensuring that no more than one dialog is active at a single time; I'd
handle SIGCHLD for that.
If you agree with this idea I'll send a patch.
Thanks and best regards,
--
Luca Saiu
Hypra team (Accessible website in co
to do it, sure. I'm asking to the Orca people
as well.
Thanks,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/874mok9dqc@hypra.fr
Hello Samuel.
On 2015-04-13 at 15:44, Samuel Thibault wrote:
> The screen-reader side of the discussion would then
> probably be the orca devel mailing list.
Thanks. I'll write to the Orca list.
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIB
if disabled.
Thanks,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87d2389g86@hypra.fr
be much simpler if it could be done
that way. Worth investigating.
Thanks,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
On 2015-04-13 at 15:05, Luca Saiu wrote:
> I was initially surprised after discovering that the window title is not
> drawn with GTK
Just to make this clear, the window title is vocalized *after* switching
window, but that's too late. A blind user will want to cycle among the
open
g ATK without making a
GTK label just for the purpose, or should I try some other route?
Thanks in advance,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
's possible as soon as
posisble, so I'll take care not to step on your toes.
Best regards,
--
Luca Saiu
Hypra team (Accessible website in construction)
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
On 2014-11-28 at 19:21, Luca Saiu wrote:
> wouldn't be unacceptable, even if in this case the issue is not moot, as
^^^
Of course I meant to write "now".
--
Luca Saiu http://ageinghacker.net
* GNU epsilon:
he same when AT-SPI connects to dbus. Is
there some fundamental reason why my idea is wrong or unfeasible (for
example, permissions)? Do you happen to have some pointers for me to
look at to better understand the issue? Is this worth the trouble?
Thanks for your time,
--
Luca Saiu http://a
(and should) we "skip" versions and proceed to
package a software which is possibly several versions more recent than
the one in debian sid?
Best regards,
--
Luca Saiu http://ageinghacker.net
* GNU epsilon: http://www.gnu.org/software/epsilon
* Vaucanson: http://vaucanson-projec
29 matches
Mail list logo
