Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2391291 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill
The votes have been last counted at 2025-09-01 15:54 UTC and the last processed comment was #comment-984081
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
Since the magnifier is enabled in settings, I'm willing to accept this is a violation of the cited criteria.
FinalBlocker +1
We used to consider "a basic functionality test" to be "every single option available in the settings app", which I don't think makes sense a we should re-evaluate it. At the same time, it's hard to say exactly what options should be covered - probably those which are used the most often or by most users (so possibly things like network, sound, display). So in general, I would probably vote -1 blocker (and yes, I feel sorry for whoever needs display magnification).
However, I think this should actually be accepted as a blocker on the grounds that it prevent any future login. For a general user, this is a game over without any chance to remedy the situation. We even have a very similar precedent from the past (also in accessibility) in bug 2354592.
Also, for users who need accessibility, there is no way they should be able to break their system switching on something they cannot live without.
AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.