(Accessibility) Management heading structure

[rayafratkina]

Per #37539, we'll want to audit all of the Management screens and ensure we're using headers appropriately.

Currently known issues from Security and Spaces audit

• Main landmark must not be contained in another landmark (must be fixed by Management app)
• Document must have 1 main landmark (must be fixed by Management app)
• Ensure landmarks are unique (must be fixed by Management app)

Relevant WCAG Criteria: [#.#.# WCAG Criterion - Level A/AA/AAA](link to https://www.w3.org/WAI/WCAG21/quickref/)

Relevant ARIA spec: [](link to https://www.w3.org/TR/wai-aria-practices/)

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[myasonik]

Looks like the landmarks and headings were largely fine. The one Management specific issue I noticed was a duplication of navigation landmarks.

Adding a (screen reader only) heading (probably an h2) and a mapping aria-labelledby to the management specific navigation would make that UI a little easier to navigate.