Bug 1827344

Summary: Alert graph timespan dropdown button needs proper label to be read by screen reader
Product: OpenShift Container Platform Reporter: Jessie <jhuff>
Component: Management ConsoleAssignee: Jessie <jhuff>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, bpeterse, jokerman, yanpzhan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:30:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Alert Graph Timespan Dropdown button none

Description Jessie 2020-04-23 17:11:47 UTC
Created attachment 1681202 [details]
Alert Graph Timespan Dropdown button

Description of problem:
When testing accessibility with axe, we get the following error:
[
  {
    "data": "",
    "id": "button-has-visible-text",
    "impact": "critical",
    "message": "Element does not have inner text that is visible to screen readers",
    "relatedNodes": [
      {
        "html": "<button aria-haspopup="true" aria-expanded="false" class="pf-c-dropdown__toggle dropdown-button--icon-only" data-test-id="dropdown-button" type="button">"
      }
    ]
  }
]

Appeared in this location: http://localhost:9000/monitoring/alerts/4212693293?alertname=KubePodNotReady&namespace=default&pod=example-0&severity=critical
However, I believe I was able to reproduce it by going to Alerting under Monitoring then selecting an alert. 


How reproducible:
Easily reproducible with the axe browser extension.

Steps to Reproduce:
1. Go to alerting under monitoring, select an alert
2. Open developer tools, go to the axe tab, press analyze
3. Click on the issue "Buttons must have discernible text" for details

Actual results:
The dropdown button is inaccessible by screen reader, the user is unable to tell what the button does at the moment. If you open up VO, it just reads it as "collapsed, pop up button" instead of explaining what the button does.


Expected results:
The button should have a label accessible by screen reader that clearly describes what the action does.Additional info:

Comment 3 Yanping Zhang 2020-04-27 12:38:35 UTC
Checked on OCP 4.5 cluster with payload 4.5.0-0.nightly-2020-04-26-203839. 
1. Go to alerting under monitoring, select an alert.
2. Open developer tools, go to the axe tab, press analyze. There is no issue "Buttons must have discernible text" now.
The bug is fixed, so move it to Verified.

Comment 4 errata-xmlrpc 2020-07-13 17:30:55 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, 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/RHBA-2020:2409