1. Gnome-shell fails with an error about not being able to initialize the newly created clutter context. I'm perfectly willing to deal with that later and use gnome classic for now, but thought I'd mention it just in case it has some relation to what's happening.
afaik you are better off using the classic thing for know, and I'm not sure that that error is effecting accessibility, but it might be in any number of ways.
2. At-spi2, while it seems to be mostly working, is having some trouble. The version of at-spi2 provided with Arch, for reference, is 2.0.0. In a nutshell: any GTK applications started before Orca will speak, while those started after Orca has loaded usually won't.
It would help to know how you start orca, I assume it happens automatically on login? if so how do things go if you start it by hand?
When this happens: I see the following in my error console: GError: org.a11y.atspi.Value There is also a frequent error such as: event_manager._deque: The event queue is empty Delivery mode: 7 Curiously, Mozilla XUL-based applications (such as Firefox and Thunderbird) seem to be exempt from this problem and will always speak regardless of when they're launched (and boy, I like what I see in firefox, so I really want to get the rest of this working).
yeah, it was pretty suprising when I first got at-spi2 working.
Thanks for any help. I'd really like to get this working, since the speed improvements in at-spi2 impress me. Firefox is super-responsive as is everything else when it speaks. And no, before anyone suggests it, I'm not considering switching distros,
that's good because I'm not aware of one where this will all just work TM, personally I'm running debian with fluxbox and hand starting at-spi2 in a terminal after login.
although if anyone can recommend an accessible live GNOME 3 environment I could try out without installing it that would be great. In a Live environment I could gauge what is the correct behavior and what is not. I'll send any debug output that'd be helpful, I'm just not quite sure where to start.
There is a live cd you can try, I don't have the link but you should be able to find it if you look through the recent a11y meetings on live.gnome.org/Accessibility I'm not sure what to check first either, it seems like a lot of this has to do with how gnome starts things which is a mess I try to stay away from. Trev
Attachment:
signature.asc
Description: Digital signature