Bug 2320044 - Plasma Welcome isn't read by the screen reader when activated
Summary: Plasma Welcome isn't read by the screen reader when activated
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-welcome
Version: 41
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Timothée Ravier
QA Contact:
URL: https://kojipkgs.fedoraproject.org//p...
Whiteboard: AcceptedFreezeException RejectedBlocker
Depends On: 2320043
Blocks: F41FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2024-10-20 16:26 UTC by Neal Gompa
Modified: 2024-10-21 19:40 UTC (History)
10 users (show)

Fixed In Version:
Clone Of: 2320043
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 495098 0 NOR UNCONFIRMED Welcome Center isn't read by the screen reader when it is activated 2024-10-20 16:30:41 UTC

Description Neal Gompa 2024-10-20 16:26:04 UTC
+++ 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.

Comment 1 Fedora Blocker Bugs Application 2024-10-20 16:28:56 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.

Comment 2 Neal Gompa 2024-10-20 17:05:12 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.

Comment 3 Alessandro Astone 2024-10-20 22:49:05 UTC
> * 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

Comment 4 Neal Gompa 2024-10-21 00:09:35 UTC
Let's keep this bug to track the "not getting red unless I press magic keys" issue.

Comment 5 František Zatloukal 2024-10-21 19:40:42 UTC
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


Note You need to log in before you can comment on or make changes to this bug.