Bug 2320046

Summary:	Konsole command output isn't read by the screen reader
Product:	[Fedora] Fedora	Reporter:	Neal Gompa <ngompa13>
Component:	konsole	Assignee:	Than Ngo <than>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	41	CC:	awilliam, fzatlouk, kde-sig, rdieter, robatino, than
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:	RejectedBlocker AcceptedFreezeException
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		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:
Bug Blocks:	2247868

Description Neal Gompa 2024-10-20 16:40:55 UTC

When I have the screen reader activated, Konsole's UI and user input fields are read, but output returned from programs is not.

Reproducible: Always

Steps to Reproduce:
1. Download the Fedora 41 KDE RC ISO
2. Boot it
3. Activate screen reader with Meta+Alt+S
4. Open Konsole with Ctrl+Alt+T
5. Type "ls" and run it.

Actual Results:  
Orca reads the input "ls" but does not read what "ls" returns.

Expected Results:  
Orca reads the input "ls" and reads what "ls" returns.

Comment 1 Fedora Blocker Bugs Application 2024-10-20 16:45:26 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:08:34 UTC

Note that I can get it read everything properly if I double-press + on the number pad, but that doesn't work if I don't have a number pad, and I can't find a way to configure it to read it fully without the key press.

Comment 3 Adam Williamson 2024-10-21 06:59:04 UTC

"Note that I can get it read everything properly if I double-press + on the number pad"

Why? is that a feature of orca? Does it indicate it's in a wrong mode or something?

Comment 4 Adam Williamson 2024-10-21 08:30:06 UTC

to answer my own question, https://a11ysupport.io/learn/at/orca documents "Key Pad Plus" as "start reading from current position"...so...hmm. Does that mean it's getting confused, stopping reading "too early", but then hitting plus a couple of times causes it to pick up and keep going? Or...something else? Might help to have an experinced orca user/dev look at this...

Comment 5 František Zatloukal 2024-10-21 19:37:25 UTC

Discussed during the 2024-10-21 blocker review meeting: [1]

The decision to classify this bug as a RejectedBlocker (Final), AcceptedFreezeException (Final) was made:

"This is rejected as a blocker as the problem is not too critical: screen reading works, and all content can be read, it just seems necessary to prompt the reader to continue (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