Tasks supporting accessibility effort Q2 FY25

[barugonman]

Overview

This issue is an Epic-like document of work related to the Q2 FY25 Aerie Accessibility (which will be referred to by 'a11y') update effort. Each linked issue covers the updates for a particular page and it's sub-pages/components e.g. data loaders and editors.

[barugonman]

Questions about scope of work:

• How far do we go down the rabbit hole with 'external' tools like Gateway and GQL Playground? For example on the Gateway WAVE complains the white-on-color buttons are too low contrast (and I don't disagree..). Do we want to just document these and maybe report to the vendors?
• Similarly, what about the Documentation page? Noting WAVE isn't happy with the contrast of all the light grey text on that page. (Maybe a 'dark mode' type option could fix this up)

[duranb]

Questions about scope of work:

• How far do we go down the rabbit hole with 'external' tools like Gateway and GQL Playground? For example on the Gateway WAVE complains the white-on-color buttons are too low contrast (and I don't disagree..). Do we want to just document these and maybe report to the vendors?
• Similarly, what about the Documentation page? Noting WAVE isn't happy with the contrast of all the light grey text on that page. (Maybe a 'dark mode' type option could fix this up)

My two cents is that it should apply to anything user facing. Gateway and GQL Playground UIs are mainly for developers and I'm not too sure if we have complete control over them anyway to be able to address any accessibility issues.

The Aerie docs page would be applicable, but I'm not too sure if we initially scoped that into this effort.

[ewferg]

I think our Aerie docs already have a "dark mode" built in thanks to Docusaurus. I would focus on the app itself and not the documentation for now (agreeing with Bryan)