Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2320046 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2024-10-21 19:38 UTC and the last processed comment was #comment-939648
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
I don't see any dedicated accessibility criteria.
I'm assuming the screen reader is a "default application", and konsole certainly is, so maybe abusing the default application functionality criteria works.
FinalBlocker +1
And agreed, I think a dedicated accessibility criteria would be good.
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
Discussed during the 2024-10-21 blocker review meeting [1]:
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
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F41 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.