Thorsten Glaser, le dim. 12 janv. 2020 19:37:03 +0000, a ecrit: > Samuel Thibault dixit: > > >I guess in your case what you expected was that at the very least > >applications started after orca got started should be accessible, even > >if orca is only started by hand. This would work if Qt was not only > >looking at org.a11y.Status ScreenReaderEnabled (the control panel > >configuration), but also at org.a11y.Status IsEnabled (set by Orca on > >startup). This would not be enough for making existing applications > >accessible when you first start Orca, Bug#874054 mentions that it's > >because Qt currently doesn't monitor the dbus IsEnabled variable. > > Ooh, interesting. From what the MuseScore people say, after start > of orca would be enough (also, AIUI, orca starts with the desktop > session or can be made to).
Starting orca only wouldn't be enough. But enabling Orca startup in the control panel would be enough. My patch is for the former case. > >Could we at least restore looking at IsEnabled in Qt, as the attached > >patch does? Actually, that is needed for proper focus tracking in Qt > >applications for zoom support in compiz when Orca is not used. The > > Would this have the effect of losing keyboard input in MuseScore > when orca is used, which is what one tester reported? That shouldn't happen, but that could be an effect indeed. > I’m under plain X11 with evilwm, no desktop environment, and did > not have that issue. Getting Orca to access the content of the application would be enough to get the same situation as the users. Samuel
