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 class="pf-c-button pf-m-plain co-toggle-play fa co-sysevent-stream__timeline__btn co-toggle-play--active" type="button"></button>" } ] } ] In approximately 9 locations: http://localhost:9000/k8s/ns/kube-node-lease/events http://localhost:9000/k8s/ns/kube-public/events http://localhost:9000/k8s/ns/openshift/events http://localhost:9000/k8s/ns/openshift-apiserver/events http://localhost:9000/k8s/ns/openshift-apiserver-operator/events http://localhost:9000/k8s/ns/openshift-authentication-operator/events http://localhost:9000/k8s/ns/openshift-cloud-credential-operator/events http://localhost:9000/k8s/ns/openshift-cluster-machine-approver/events http://localhost:9000/k8s/ns/openshift-cluster-samples-operator/events Version-Release number of selected component (if applicable): How reproducible: Easily reproducible with the axe browser extension. Steps to Reproduce: 1. Go to any page with event streaming, such as http://localhost:9000/k8s/ns/default/events 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 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 "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:
The code in pr 5123 is not contained in payload 4.5.0-0.nightly-2020-04-21-103613. Will check when there is new available payload.
Checked on 4.5 cluster with payload 4.5.0-0.ci-2020-04-22-212726。 Now there is aria-label for event stream button, aria-label="Pause event streaming", aria-label="Start streaming events"。
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