https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=336h&context=1&type=junit&name=pull-ci-openshift-console-master-e2e-gcp-console&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=168h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job It seems I have to wait for some time, since the 4.11 release is merged only 22 hours ago at the time of writing this comment. I will follow up the verification when more job logs are produced.
https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=168h&context=1&type=junit&name=periodic-ci-openshift-release-master-nightly-4.11-console-aws&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job This should be the link for 4.11. Sorry that I pasted the wrong link before.
https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=168h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job I think the bug can be verified now.
Reason: The failure logs stopped emerging 3 days after the PR for release 4.11
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069