Re: "[window title] inaccessible": where does it come from, and what does it mean?

Hello Joanmarie. On 2015-06-29 at 13:00, Joanmarie Diggs wrote: > there is a > sad hack or three in Orca due to issues in Metacity. Therefore, if you > could file a bug against Orca and attach a full debug.out, I'll look > into it. Since you think it's useful I will, but at this stage I suspect

Re: "[window title] inaccessible": where does it come from, and what does it mean?

Having given it some more thought, I just ripped out the code that says "inaccessible." If there are Marco issues (or issues in your app), let's fix them properly. In the meantime, Orca master won't say that any more. --joanie On 06/29/2015 01:00 PM, Joanmarie Diggs wrote: > That's logic in Orca.

"[window title] inaccessible": where does it come from, and what does it mean?

Hello. As you may know from my interaction [1] with Alejandro Piñeiro, who has given me some useful suggestions, I'm trying to develop a very simple accessible application using ATK but without GTK+ or any other toolkit. My current standalone program uses SDL to draw a window and manage a few eve

Re: "[window title] inaccessible": where does it come from, and what does it mean?

That's logic in Orca. The Marco "support" in Orca is simply mapping things over from the old GNOME 2.x days with Metacity. And there is a sad hack or three in Orca due to issues in Metacity. Therefore, if you could file a bug against Orca and attach a full debug.out, I'll look into it. Thanks! --j

Re: Describing an application state in ATK, without Gtk

Hello. On 2015-06-26 at 12:20, Alejandro Piñeiro wrote: > On atk/at-spi it is assumed that you would provide a root object for the > accessibility object hierarchy. On ATK you do that by providing a > implementation of AtkUtil. Yes, I had already done so after your first reply; that is in fact n