(Accessibility) Spatial references in documentation

[myasonik]

Searching our docs for common spatial references like “above,” “below”, “left,” and “right” yields a bunch of results. Though some uses might be fine, no UI controls should be labelled in such a way that relies on these characteristics.

Relevant WCAG Criteria: 1.3.3 WCAG Criterion - Level A

Originally mentioned in #11534 (comment) by @nrichers

[elasticmachine]

Pinging @elastic/kibana-docs (Team:Docs)

[myasonik]

Another way that we could improve our docs as well is removing mouse-specific verbiage (stuff like "Click on Discover" can become something like "Choose Discover").

Searching our docs for the word "click" shows about 3500 results in our docs alone so I'm not sure how to best tackle that.

More notes on writing for accessibility in Standards for Writing Accessibly

[myasonik]

Thanks for the fix @KOTungseth!

I went through the PR and only saw fixes for "above" references and it looks like "left", "right" and "below" still exist throughout the docs.

Should I make separate tickets?

[KOTungseth]

@myasonik this issue was closed by mistake. We'll be working on "left", "right" and "below" in the next few weeks. PRs to come!

[myasonik]

Should this stay open for "left" and "below" or should we open up new issues for those?

[gchaps]

Already done:

Below: #60159

Left: #60807