RFC: Accessibility Tooling - Sensible Defaults

[ryantownsend]

• Is aXe the right tool? (I want to say yes)
• What are the right defaults for this tool? Enable every audit? Enable some?

I've got enough experience to know there are many nuances for a11y optimisation, but I'm definitely not expert enough to know what they are, hence this RFC.

We want to support the community (and the web's users!) the best we can with our OSS effort, so the goal is to set developers off in the right direction.

FWIW to any experts: "No strong feelings" is as valuable feedback as "Turn off audit X" or "Make sure audit Y is enabled".

Related issues: #60 & #185

/cc: @sufian-cf

[matuzo]

aXe is definitely a good tool. One of the benefits of aXe is that it's open source, well-documented, and there are all kinds of implementations of it (e.g., Node, GitHub Actions, etc.). Most devs are also familiar with it.

aXe tries to avoid false positives, which usually means that the issues it reports are likely proper problems for people. That's why I wouldn't disable any of the rules. You could disable best practices by default and offer the option to enable them (or vice versa).

I hope this helps!

[ryantownsend]

Thank you @matuzo this is very helpful 🙏