Re: [orca-list] OT: QT5 accessibility without qt-at-spi
- From: Samuel Thibault <sthibault hypra fr>
- To: Frederik Gladhorn <gladhorn kde org>, chrys <chrys linux-a11y org>
- Cc: orca-list gnome org
- Subject: Re: [orca-list] OT: QT5 accessibility without qt-at-spi
- Date: Fri, 10 May 2019 11:34:19 +0200
Hello,
Frederik Gladhorn, le jeu. 02 mai 2019 10:54:31 +0200, a ecrit:
Technically this is a hack (QT_LINUX_ACCESSIBILITY_ALWAYS_ON) and should not
be needed. But it seems like the settings that Qt tries to read, to detect if
Orca is running have changed.
Is there a sensible way to detect if accessibility is wanted, and to which
level? Qt can do all of this on demand and does enable some things only on
demand since they come with a slight overhead.
From what I can read in the qtbase source:
bool enabled = a11yAlwaysOn || a11yStatus->screenReaderEnabled();
Using screenReaderEnabled is not a proper way: that property only means
that the screen reader should be started on session startup. isEnabled
should be used instead, see its declaration in
./src/platformsupport/linuxaccessibility/dbusxml/Bus.xml
That one is set by Orca when it is started (either explicitly by the
user or automatically for the session), but also by other accessibility
tools (such as focus tracking for zoom support in compiz).
If i m right GNOME is getting a string from dconf.
dconf gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled true
Yes, but that is gnome-specific.
Samuel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]