Created attachment 1685246 [details]
Operator Hub input error
Description of problem:
On the operator hub and catalog pages, the input field does not have an aria-label which can create issues for screen readers. While placeholder text provides valuable guidance for many users, placeholder text is not a replacement for labels. Assistive technologies, such as screen readers, do not treat placeholder text as labels. Placeholder text is also not broadly supported across assistive technologies.
This issue gives the following axe error:
"message": "aria-label attribute does not exist or is empty",
"html": "<input placeholder="Filter by keyword..." type="text" class="co-catalog-page__input pf-c-form-control" value="">"
Version-Release number of selected component (if applicable):
You can see this error by using the Axe Chrome Extension.
Steps to Reproduce:
1. Go to http://localhost:9000/operatorhub or http://localhost:9000/catalog
2. Inspect the page and go to the axe tab.
3. Click "Analyze" - this issue is the one that says, "Form elements must have labels"
Input fields that are inaccessible for screen readers.
Input fields that are properly labeled for assistive technology.
Checked on ocp 4.5 cluster with payload 4.5.0-0.nightly-2020-05-10-231314.
Check filter input box on OperatorHub page and Catalog page, there is lable: aria-label="Filter by keyword...", and axe analyzing have not label error now.
The bug is fixed, so move it to Verified.
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.