Bug 1859279

Summary: OperatorHub: Accessibility warning when clicking on tile to open modal
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, jokerman, yanpzhan
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.6.0-0.ci-2020-07-21-054552 Cluster ID: 187e580c-f67e-49ee-b8ef-5b76cbf8e85b Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:79.0) Gecko/20100101 Firefox/79.0
Last Closed: 2020-10-27 16:16:41 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:

Description Samuel Padgett 2020-07-21 15:47:41 UTC
Steps to reproduce:

1. Go to Operators -> OperatorHub
2. Click on one of the tiles.

You see this warning in dev tools:

Modal: When using hasNoBodyWrapper or setting a custom header, ensure you assign an accessible name to the the modal container with aria-label or aria-labelledby. 

Opening as medium severity since this likely indicates an accessibility issue.

Comment 3 Yanping Zhang 2020-07-29 09:04:00 UTC
Checked on OCP 4.6 cluster with payload 4.6.0-0.nightly-2020-07-25-091217
Go to operator hub page, click open one catalog tile, check the modal element, there is 'aria-labelledby="catalog-item-header"' for modal, and there is 'id="catalog-item-header"' for modal header.
The bug is fixed.

Comment 5 errata-xmlrpc 2020-10-27 16:16:41 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

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