-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
hi To my limited knowledge of qt accessibility, qt5 applications look for whether accessibility is turned on by looking for the gnome screenreader key /org/gnome/interface/accessibility. If true, they enable accessibility. If false, they don't. I could have that wrong, but I don't think they rely on a variable. I do know that having the qt_accessibility variable exported does not negatively affect qt5 applications in any way, including accessibility. I've got both here, vlc, which uses qt4, and calibre, which uses qt5, and both talk and don't seem to conflict with each other. So setting export QT_ACCESSIBILITY to 1 will enable accessibility of qt4 applications without affecting qt5. Thanks Kendell clark Sent from Fedora GNU/Linux version 22
Bastien Nocera wrote:
----- Original Message -----
kendell clark wrote:
It is true that you have to be somewhat advanced to know to create a script in /etc/profile.d, but this is *necessary* for qt4 accessibility to work. Without this, the plugin is installed but no program knows to use it.
I just spoke with some upstream Qt/KDE accessiblity devs, and they continue to recommend that users of Qt4 applications to do some sort of opt-in (ie, set QT_ACCESSIBILITY=1 manually). They said the support is just not good or reliable enough to justify enabling it by default for everyone.
In short, I'd be in favor of including qt-at-spi in workstation's installation set (but not set QT_ACCESSIBILITY=1 automatically).
What would this bring, besides shortening the setup instructions?
I could possibly be convinced to set QT_ACCESSIBILITY=1 conditionally somehow (based on some configuration key being set or not, for example)
-- Rex
p.s. This only applies to Qt4 applications, of course, Qt5 ones should work out of the box.
Which uses the same variable name as Qt4, which means we cannot enable it by default when we install qt-at-spi.