Open
Description
Based off of this comment chain in #578, I think we have a lot of work to do to improve our use of accessible HTML (and markdown-generated HTML) in our documentation. This is useful for a couple of reasons:
- Immediately, we improve the accessibility experience for screenreader users (and SEO engines)
- Since many users use our docs as a template, we influence downstream users of our template in the sites that they create
Thus, I'd like to see us gradually improve our codebase, primarily through semantic HTML. This includes:
- convey meaning with custom styles instead of relying on defaults (most relevant for headers generated with markdown)
- one example here; skipping from
##to####
- one example here; skipping from
- better alt text and aria-labels for non-text UI elements
- one example is documented in Accessibility: Missing
alttext on dropdowns #800
- one example is documented in Accessibility: Missing
This list is incomplete; would love to have more input from the community!