Created attachment 1687418 [details] Alert Manager definition list error Description of problem: The alert manager is missing a <dl> in the definition list structure under the Alert Routing section. The parent dl element ensures the list follows the proper hierarchy. This help screen reader users know what they are listening to, and what to expect as they listen to definition lists with regard to the organizational relationship of parent and child items. (https://dequeuniversity.com/rules/axe/3.5/dlitem?application=AxeChrome) It currently has the following axe error: { "data": null, "id": "dlitem", "impact": "serious", "message": "Description list item does not have a <dl> parent element", "relatedNodes": [ { "html": "<dt>Group By</dt>" } ] }, { "data": null, "id": "dlitem", "impact": "serious", "message": "Description list item does not have a <dl> parent element", "relatedNodes": [ { "html": "<dd data-test-id="group_by_value">namespace</dd>" } ] }, { "data": null, "id": "dlitem", "impact": "serious", "message": "Description list item does not have a <dl> parent element", "relatedNodes": [ { "html": "<dt>Group Wait</dt>" } ] }, { "data": null, "id": "dlitem", "impact": "serious", "message": "Description list item does not have a <dl> parent element", "relatedNodes": [ { "html": "<dd data-test-id="group_wait_value">30s</dd>" } ] } How reproducible: You can see this error by using the Axe Chrome Extension. Steps to Reproduce: 1. Go to the Alert Manager: http://localhost:9000/monitoring/alertmanagerconfig 2. Open developer tools, go to the axe tab, press analyze 3. Click on the issue "<dt> and <dd> elements must be contained by a <dl>". Actual results: Invalid definition list structure Expected results: Valid structure that helps screen readers understand context
goto monitoring/alertmanagerconfig page, analyze the page with axe, no the error: "<dt> and <dd> elements must be contained by a <dl>" and pages works well 4.5.0-0.nightly-2020-05-12-191228
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