+++ This bug was initially created as a clone of Bug #2320043 +++ When I activate the screen reader with Meta+Alt+S, Orca starts up but does not read the Plasma Welcome window. Reproducible: Always Steps to Reproduce: 1. Download the Fedora 41 KDE RC ISO 2. Boot it 3. Activate screen reader with Meta+Alt+S Actual Results: After "Screen reader on" is said, nothing is read. Expected Results: After "Screen reader on" is said, Plasma Welcome should be read to you saying "Welcome to Fedora" and some such.
Proposed as a Blocker for 41-final by Fedora user ngompa using the blocker tracking app because: This is conditional violation of all desktop related criteria for KDE for all people who need a screen reader.
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.
> * 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? That is the same Qt bug as https://bugzilla.redhat.com/show_bug.cgi?id=2320043 > * 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) That is a different bug; up to you how you want to track it
Let's keep this bug to track the "not getting red unless I press magic keys" issue.
Discussed during the 2024-10-21 blocker review meeting: [1] The decision to classify this bug as RejectedBlocker (Final), AcceptedFreezeException (Final) was made: "This is rejected as a blocker as the problem is not too critical: screen reading works, and all critical content can be read, it just seems necessary to prompt the reader to get body content read (using the normal key for this purpose) at points where it seems like that shouldn't be necessary. we also note that this is not new behaviour (previous releases behaved the same)." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-10-21/f41-blocker-review.2024-10-21-16.00.log.html
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '41'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15. Fedora Linux 41 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.