Open 1Copenut opened 1 year ago
@dmlemeshko I opened this meta issue to capture routing issues from our A11y Testing sync on Wednesday 31 August.
Pinging @elastic/kibana-core (Team:Core)
What exactly are we looking for here? This meta issue doesn't seem to link out to anything or have concrete use cases, so it's hard to tell which team should own it.
Unassiging Core, as I don't think we're directly related to this issue
Description
Accessibility specialists and quality assurance engineers are interested in collecting metrics on routes, test runs, test skips in Kibana to better understand our product. This meta issue will gather the work streams needed to implement this request.
The long-term plan
We're looking to move products and features from low to no a11y test coverage, to reporting violations without breaking, to stable tests that break on a11y violations due to regression. This will be a longer tail process, and will help us understand the accessibility landscape better because we'll have more data to work with.