Re: Enabling accessibility stack by default in Qt4/Qt5
On Tue, Sep 08, 2015 at 10:52:46AM AEST, Mario Lang wrote:
> If we are talking about Qt on framebuffers (how cool!), I doubt that it
> would be practical to use if it already "worked". After all, Orca would
> still need to run in a conventional X session, wouldn't it? And d-bus
> would need to be convinced to have those two talk to each other.
> And then, all of the orca keyboard based commands would likely no longer
> work, because the current console would be the wrong on. Or am I
> misunderstanding anything here?
As things currently stand, you are pretty much correct. There are plans upstream to decouple Orca from its preferences GUI, which would hopefully make it easier to further reduce Orca's dependency on specific toolkit bits in its core.
I don't think DBus will be an issue. Capturing keystrokes may be another matter, given that currently GUI toolkits like Gtk and Qt have to implement key snoopers to allow assistive technologies to get priority over keyboard commands. With the move to wayland, I am pretty sure there are plans to move this elsewhere, i.e the at-spi registry daemon would be responsible for this. As it is, that was the plan way back when, but the XEVI extension for X didn't really turn out to be as good as hoped, hense the toolkit key snoopers.
Luke
Reply to: