(Accessibility)(Meta) Create and track automated accessibility test coverage for all Kibana products

[1Copenut]

Description of what we're doing

The accessibility specialists and quality assurance engineers are working on a vision to bring automated accessibility testing to all products and plugins in Kibana. This will be a long-tail project and has three broad phases:

1. (We are here): Gather information about current functional and a11y testing
2. Add report-only (non-breaking) a11y tests to products and plugins
3. Remediate issues as needed and switch tests to fail on a11y regressions or new bugs

Why we're scoping this work

Automated tests are the foundation for a mature accessibility practice. By having products under test, we can detect regressions and potential bad user experiences quicker.

Tasks

The linked issues below are meta issues to capture dependent workstreams in logical buckets. Each meta issue will have tasks that will help us get to this unified goal.

• (Accessibility)(Meta) Add ability to report a11y violations without failing functional tests #139938
• (Meta) Collect metric data on routes and test runs for Kibana #139947
• (Meta) Instrument and visualize routes, test runs, failures in Kibana  #139948

[elasticmachine]

Pinging @elastic/kibana-accessibility (Project:Accessibility)

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[lukeelmers]

Heya @1Copenut - love that you are looking to bring automated accessibility tests to Kibana! This is exciting stuff and I think would be a huge win.

Looks like you've opened a flurry of issues with some very specific, prescriptive asks. I'm wondering if it might be better to step back and have a chat with someone from the Kibana platform team about your goals here so that we can recommend a path forward? As it stands, many of these issues are missing some context and it seems like an effort of this size could benefit from a proper definition and design phase. It would also help us clarify which team(s) would need to be involved, as most of these items don't sound directly related to the Core team.

Cc @alexfrancoeur @alexh97

[1Copenut]

@lukeelmers I agree a conversation with the Kibana platform team is the right first step. I gambled a little on making the issue requests, so taking a step back and reviewing is a good call.

I will find some time on the calendars of folks mentioned here to discuss. Much appreciated!

[pgayvallet]

Unassiging Core, as I don't think we're directly related to this issue

[elasticmachine]

Pinging @elastic/appex-qa (Team:QA)