https://bugs.kde.org/show_bug.cgi?id=452132
Bug ID: 452132
Summary: Qt/KDE applications not accessible with the Orca
screen reader.
Product: Qt/KDE Flatpak Runtime
Version: unspecified
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: them...@themuso.com
CC: aa...@kde.org
Target Milestone: ---
SUMMARY
I am unable to navigate Qt and KDE apps running as a flatpak using the Orca
screen reader in a GNOME desktop session. I have not tested this when running
under a KDE desktop session. However if I run the flatpak from a terminal with
the command-line arguments --no-a11y-bus --talk-name=org.a11y.Bus, then the app
is accessible with Orca.
STEPS TO REPRODUCE
1. Log into a GNOME session (I am using GNOME 41 on Fedora 35).
2. Enable Orca. This can be done with the Alt + Super + S shortcut key. (Make
sure you have working audio to hear spoken text)
3. Install a Qt/KDE app from flathub, as above, org.kde.dolphin is a good test
candidate here.
4. Either load dolphin from the activities overview, or run "flatpak run --user
org.kde.dolphin" in a terminal.
OBSERVED RESULT
Dolphin loads, but when navigating the app with the keyboard, you do not hear
any spoken text from Orca.
EXPECTED RESULT
Orca should read the files and folders that you navigate to with the keyboard.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 5.16.18-200.fc35.x86_64, GNOME 41, latest version of
org.kde.Platform 5.15-21.08 from flathub.
KDE Plasma Version:
KDE Frameworks Version: 5.15-21.08
Qt Version: 5.15
ADDITIONAL INFORMATION
A workaround is to run "flatpak run --user --no-a11y-bus
--talk-name=org.a11y.Bus org.kde.dolphin" in a terminal. Doing this, Orca
should read the files and folders that you navigate to with the keyboard.
I suspect the problematic commit is 7800017d67f93f7e93f7294b91a1048cf933a39f
from https://invent.kde.org/qt/qt/qtbase.git.
It should also be noted that running a GTK 4 app like org.gnome.TextEditor
works fine without any tweaking. So far as I know, GTK 4 does use the
AT_SPI_BUS_ADDRESS environment variable, and all works well.
--
You are receiving this mail because:
You are watching all bug changes.
