| Summary: | Welcome Center isn't read by the screen reader when it is activated | ||
|---|---|---|---|
| Product: | [Applications] Welcome Center | Reporter: | Neal Gompa <ngompa13> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | adamw, ales.astone, cwo.kde, m.weghorn, nate, olib141 |
| Priority: | NOR | Keywords: | accessibility |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| URL: | https://kojipkgs.fedoraproject.org//packages/Fedora-KDE-Live/41/1.2/images/Fedora-KDE-Live-x86_64-41-1.2.iso | ||
| See Also: |
https://bugzilla.redhat.com/show_bug.cgi?id=2320044 https://bugs.kde.org/show_bug.cgi?id=495096 https://bugs.kde.org/show_bug.cgi?id=495102 |
||
| Latest Commit: | Version Fixed In: | 6.5.0 | |
| Sentry Crash Report: | |||
|
Description
Neal Gompa
2024-10-20 16:29:20 UTC
Some additional testing reveals some interesting details: * The autolaunched welcome can't be read, but if I quit it and reload it, then it can be read. This potentially suggests a race? * It seems to not get read unless I double-press + on the number pad (and this doesn't work if you don't have a number pad) Once I force Orca to read it, it does seem to do the job. But this is unexpected behavior, as it should be read as soon as the screen reader is invoked and shouldn't require a weird shortcut to make it read it. This may be partly or completely resolved by https://codereview.qt-project.org/c/qt/qtbase/+/598549 by aleasto. The mentioned Qt changeset doesn't address the "need magic keys to make orca read the application" issue. well, in https://bugs.kde.org/show_bug.cgi?id=495102 the same magic key combo worked - so maybe there are just two issues here? the one addressed by https://codereview.qt-project.org/c/qt/qtbase/+/598549 , and the 'why do i need to press a magic key combo to get some things read' issue? https://a11ysupport.io/learn/at/orca documents "Key Pad Plus" as "start reading from current position"... I wonder if changing "X-KDE-Kded-phase" in the KDED module from 1 to 2 would help. If it does, we could change it. (In reply to Oliver Beard from comment #6) > I wonder if changing "X-KDE-Kded-phase" in the KDED module from 1 to 2 would > help. If it does, we could change it. What is this? (In reply to Neal Gompa from comment #7) > (In reply to Oliver Beard from comment #6) > What is this? https://invent.kde.org/plasma/plasma-welcome/-/blob/master/src/kded/kded_plasma-welcome.json?ref_type=heads#L95 Changing it from 1 to 2 would make Welcome Center start later in Plasma's startup. I could conceive that here it might make a difference, but when initially choosing this value I thought earlier would be better. You'd have to change it in the source and recompile to test. It might be possible to alter the compiled binary (/usr/lib/qt6/plugins/kf6/kded/kded_plasma-welcome.so) but not trivial (I can use Okteta to find "X-KDE-Kded-phase", followed by the byte 0x1). I can't guarantee this would work though, as that copy of the value might not be used. > Changing it from 1 to 2 would make Welcome Center start later in Plasma's startup. I could conceive that here it might make a difference
You can reproduce plasma-welcome not reading the page contents starting it whenever, with `/usr/bin/plasma-welcome`.
The other thing is a Qt bug as said in the comments above.
Later should be fine anyway; Welcome Center's launch is not time sensitive. I just gave this a try today, and the screen reader reads everything in the app now. Looks like this has been fixed for Plasma 6.5.0 or earlier. |