Open 1Copenut opened 2 years ago
Pinging @elastic/kibana-core (Team:Core)
By "kibana routes" do you mean all routes that are created in the browser? If so, those aren't stored in a centralized way: each application is mounted independently from a base path for that app, and the app can create any number of routes which kibana's core is unaware of.
Yes, I'd like to see if there's a way to map all routes that are created in the browser for Kibana. I can appreciate this is tricky for apps that use client-side routing. The use case would be to map a11y test coverage and determine what routes do have automated a11y checks, and when new routes are added or reported.
Describe the feature: I'd like to have a visualization that shows the delta (difference) in Kibana routes vs. Kibana routes with functional tests vs. Kibana routes with a11y tests.
Describe a specific use case for the feature: Accessibility specialists and quality assurance engineers are discussing ways to visualize code coverage and establish an accessibility maturity model. Having this visualization will tell us the general level of testing and areas that would benefit from additional accessibility checks.