Created attachment 181603 [details] Long open/close + screen reader turning on on its own SUMMARY There are a few problems with the Screen Reader page I've noticed: - the Orca configuration window needs about 3 seconds to open/close, which is unusually long - launching the configuration window enables the screen reader for some reason - after closing the configuration window the screen reader is still enabled, even though the checkbox next to "Enable" isn't ticked STEPS TO REPRODUCE 1. Go to Accessibility > Screen Reader 2. Click on " Launch Orca Screen Reader Configuration..." 3. Click "Cancel" in the new window OBSERVED RESULT Screen Reader is turned on for some reason, yet "Enable" isn't marked with a tick The configuration window took a long time to open/close EXPECTED RESULT Screen Reader isn't enabled without the user asking for it The configuration window opens/closes quickly SOFTWARE/OS VERSIONS System Settings: 6.3.90 KDE Frameworks: 6.15.0 Qt: Using 6.9.0 and built against 6.9.0 KDE neon Unstable Edition (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.11.0-26-generic
(In reply to hottog from comment #0) > Created attachment 181603 [details] > Long open/close + screen reader turning on on its own > > SUMMARY > There are a few problems with the Screen Reader page I've noticed: > - the Orca configuration window needs about 3 seconds to open/close, which > is unusually long This one is an Orca issue; please report there! > - launching the configuration window enables the screen reader for some > reason This may be our bug, and I can confirm it. We'll use this bug report to track it. > - after closing the configuration window the screen reader is still enabled, > even though the checkbox next to "Enable" isn't ticked This is a symptom of of the above issue.
> launching the configuration window enables the screen reader for some reason That's just how Orca works. The setup button calls "orca -s", that starts the screen reader and opens its settings. Probably the only sensible thing we can do is to not enable the button unless the checkbox is enabled too
Yeah, that makes sense.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3017