Controls in gnome-do are inaccessible

This problem is two fold.
A) Gnome-Do is highly visual. If you are using Orca, chances are you are not going to want to use Do...
B) None of the primary developers are Orca users or no anything about it. Whilst accessability is important, to us it is often an afterthought. I am not saying this is a good thing, just that this is the way it is. There is, at current, 2 active core developers. We simply do not have the resources =/ If you want to help, and have an aptitude for coding, we are always looking for assistance.

While I certainly understand and sympathize with your second point above, I have to strongly disagree with the first. Unless I'm completely misunderstanding what Do does, it sounds very similar to Quicksilver which I used quite frequently under OS X with VoiceOver. It baffles me to learn that this app is too visual, because the description of its interface sounds quite simple, no more complex than Firefox, Thunderbird, Gnotime or any of the other "visual" applications I use daily and competently.

Unfortunately I personally can't help much with this issue, other than to note that most standard GTK controls are already accessible. I'm guessing that the existing controls are custom? If so, would it be possible to use standard controls instead? Is the interface much more complicated than a text field and one or two tables or trees?

I can forward this ticket to the Orca and/or gnome-accessibility lists if you like, and perhaps someone with more knowledge might help. This really does sound like a useful program, and I hope that someday I'm able to use it.

Thanks for your time.

If you are a user who would like to use Orca with Do I stand corrected =) The next time we have a hackfest I just might try to work on Orca + Do.

This is certainly a problem that can be solved. Jason only meant to express
that the problem is hard and will likely not be solved in the current
release cycle or the next.

Just wondering if anyone has taken a look at this? I also recently found this guide, which may help developers not familiar with Orca or the accessibility infrastructure:

http://library.gnome.org/devel/accessibility-devel-guide/nightly/

I think orca users will benefit of do accessiblity because of the following points:
1. The main input method to do is the keyboard. This means there is no mouse smiulation or mouse oriented interface to deal with (at least comparing to other applications).
2. The interface is simple. The hard part is the autocomplition, it's not easy to provide that information with non visual means, unless reading the options sequencialy. Even not the best idea it works and many users find it useful in firefox for example.
3. There should be a good reason to use custom controls in do. Noone reenvents stuff for saying to friends that did it. Even that way, it is possible to give accessibility to them via ATK. I wanted to look at the code that implements the custom controls but don't really know where to start..

All that would really need to be done to get Do to work at least partially with Orcas is adding AT-SPI capabilities to Do

That's quite a big "really" :). AT-SPI is not tiny. There are at least some CLI libraries to do that, though, and Banshee has done the work to make their custom widgets work. It's not impossible, I just still estimate it to be quite a chunk of work, that I'm unlikely to do myself in the near future. Patches welcome, though :)