Bug 2320044
| Summary: | Plasma Welcome isn't read by the screen reader when activated | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Neal Gompa <ngompa13> |
| Component: | plasma-welcome | Assignee: | Timothée Ravier <travier> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 41 | CC: | ales.astone, extras-qa, fzatlouk, jgrulich, kde-sig, rdieter, robatino, than, travier, vinicius.fedora |
| Target Milestone: | --- | Keywords: | Desktop |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://kojipkgs.fedoraproject.org//packages/Fedora-KDE-Live/41/1.2/images/Fedora-KDE-Live-x86_64-41-1.2.iso | ||
| Whiteboard: | AcceptedFreezeException RejectedBlocker | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2320043 | Environment: | |
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2320043 | ||
| Bug Blocks: | 2247868 | ||
|
Description
Neal Gompa
2024-10-20 16:26:04 UTC
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 |