Spaces Accessible Headers

[kobelb]

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

Spaces Management

• 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)
• Heading levels should only increase by 1 (Fixable by us!)

Space Selector

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

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[legrego]

I did a brief audit of the Spaces screens today. Most of our headings findings are outside of our control — both the management screens and the spaces selector are rendered within Kibana-provided markup, which we can’t control yet.

There are a couple of other quick fixes I can put a PR up for though, to at least get this initiative started. I’ll update the PR description so we can better track this progress

[kobelb]

Thanks, Larry!

[rayafratkina]

Depends on #51493

[kobelb]

@rayafratkina all of the issues that we can fix should now be addressed.

[myasonik]

Just confirmed on master these look good