Bug 1884629 - Visusally impaired user using screen reader not able to select Admin/Developer console options in drop down menu.
Summary: Visusally impaired user using screen reader not able to select Admin/Develope...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Joe Caiani
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-02 13:59 UTC by Adrian Hammond
Modified: 2021-02-24 15:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:22:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7024 0 None closed Bug 1884629: pf update to fix dropdown accessibility bug 2021-02-08 16:20:48 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:22:55 UTC

Description Adrian Hammond 2020-10-02 13:59:52 UTC
Description of problem:

Visually impaired user is now able to select between the Admin/Developer console options in the menu drop-down. The screen reader does not pickup that the drop down is available. 


Version-Release number of selected component (if applicable):

4.5

How reproducible:

Easily assuming you have a screen reader


Steps to Reproduce:
1. 
2.
3.

The visually impaired user is a Deutsche Bank developer. I am not able to reproduce and I am sighted and do not use a screen reader. I am certain that the developer would be happy to get onto a call to explain what he does.  



Actual results:

Admin/Dev console drop down options not highlighted by screen reader


Expected results:


Additional info:

Comment 1 Samuel Padgett 2020-10-02 14:23:36 UTC
Related to Bug 1783109.

Comment 2 Joe Caiani 2020-10-02 20:35:13 UTC
Hi adhammon 

If possible, could you find out the browser and the type of screenreader that the deutchebank user is using to use openshift so that we can properly fix and test the context switcher for the customer? If you could reply in this bugzilla that would be great.

Comment 3 Adrian Hammond 2020-10-05 10:12:57 UTC
(In reply to Joe Caiani from comment #2)
> Hi adhammon 
> 
> If possible, could you find out the browser and the type of screenreader
> that the deutchebank user is using to use openshift so that we can properly
> fix and test the context switcher for the customer? If you could reply in
> this bugzilla that would be great.

Hi Joe, 

They are using:

Screen reader: JAWS 2019

Browser: Chrome


Thanks Adrian

Comment 5 Joe Caiani 2020-10-22 16:05:28 UTC
Met with the bug submitter and openshift user to validate that we are interpreting the bug correctly from our JAWS system, and also validated our fix in patternfly with the user. As this has fixed his problem, I will incorporate this fix that resides in this weeks pf release into openshift so we can close out this bug.

Comment 7 Yadan Pei 2020-11-03 08:59:56 UTC
based on comment 5 I think it's ok to move the bug to VERIFIED

Let me know if I'm wrong

Comment 10 errata-xmlrpc 2021-02-24 15:22:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633


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