Bug 1607080 - system-config-users is not accessible with orca screen reader even when accessibility services are enabled
Summary: system-config-users is not accessible with orca screen reader even when acces...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-users
Version: 28
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Moez Roy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-21 15:08 UTC by majid
Modified: 2019-05-28 21:55 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 21:55:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description majid 2018-07-21 15:08:54 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build Identifier: 

when I launch system-config-users I am unable to use it due to the fact it is not accessible tabbing around produces no feedback
other applications are accessible e.g gparted

Reproducible: Always

Steps to Reproduce:
1. launch orca the screen reader alt+f2 type orca in the box to launch it
2. make sure accessibility services are enabled
3. launch system-config-users
4. try to navigate around the users and groupes program
Actual Results:  
no feedback was given as to what butten i was on,
or any element such as list of users it was un navigable


Expected Results:  
been completely accessible
I should have been able to access every button every combo box and been able to edit my memberships in groups e.g adding myself to the libvirt group
and been able to navigate with orca.


running fedora 28

Comment 1 Persona non grata 2018-07-21 16:45:30 UTC
I will add some clarifications:

1. In the Fedora-MATE-Compiz distribution, Gparted and System-config-users are not accessible for Orca if they run through the MATE menu, or through alt + f2;

2. If you run Gparted using the command

sudo -E gparted

Gparted becomes accessible for Orca.
But in the context of System-config-users, this does not work;

3. When I used the Fedora-WorkStation distribution, and on my system, next to GNOME, there were installed mate-desktop and mate-applications groups packages, I interacted with System-config-users using the Orca screen reader.

Comment 2 Ben Cotton 2019-05-02 21:16:37 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-28 21:55:25 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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