Bug 1827344 - Alert graph timespan dropdown button needs proper label to be read by screen reader
Summary: Alert graph timespan dropdown button needs proper label to be read by screen ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Jessie
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-23 17:11 UTC by Jessie
Modified: 2020-07-13 17:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:30:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Alert Graph Timespan Dropdown button (295.49 KB, image/png)
2020-04-23 17:11 UTC, Jessie
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5178 0 None closed Bug 1827344:Alert graph timespan dropdown button needs proper label to be read by screen reader 2020-06-23 10:21:17 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:11 UTC

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


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