[ML] (Accessibility) Machine Learning - Anomaly Detection / Create Job - Landmark Accessibility Best Practice Issue

[barlowm]

Not explicitly WCAG 2.1 violations but they do violate WAI-ARIA best practices and should be addressed.

• Main landmark must not be contained in another landmark
• Page must have one main landmark
• Landmarks must have a unique role or role/label/title (i.e. accessible name) combination

Steps to reproduce

• From the Machine Leaning/Anomaly Detection/Job Management page, click the "Create new job" button.
• On the "Select index pattern or saved search" page click the "[eCommerce] Orders" item
• On the "Create a job from the saved search [eCommerce] Orders" page select the "Kibana sample data eCommerce" item
• Use deque axe to reveal the issue, or view source and search for the "main" tag

<main class="application tab-overview" >
    ... Additional Code ...
    <main class="euiPageBody">
        ... Additional Code ...
    </main>
    ... Additional Code ...
</main>

Kibana Version:
7.5.0

OS:
Windows

Browser:
Chrome

Screen reader: [if relevant]
N/A

Relevant WCAG Criteria: WCAG Quick Reference

Relevant ARIA spec: WAI-ARIA Authoring Practices 1.1
WAI-ARIA Landmark Regions

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[peteharverson]

This has been fixed in 7.6.0 by the replacement of Angular routing in #51842, so that the pages now only contain one

landmark. The top-level application class level element is now rendered in a <div> rather than a <main>.

7.5.0:

7.6.0: