New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon-a11y: CI support #8845
Comments
@Peeja this would be amazing! You might take a look at storyshots as an example of a standalone CI process that uses storybook's story store? https://github.com/storybookjs/storybook/tree/next/addons/storyshots |
+1 |
FYI, this appears to be work in progress by @Hypnosphi here: #8934 |
It's actually ready to use with current beta, see https://github.com/storybookjs/storybook/tree/next/addons/storyshots/storyshots-puppeteer#axetest |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
We'd like our components to be accessible, so we use the
a11y-addon
. But it's easy to forget to look at that all the time. Having the result in CI (or even better, in a command that can also run locally from the command line) would help a lot to make sure we cover our bases.I see that that's on the roadmap already. Has the path to get there been thought out yet? If I were to try to make that happen, as someone not at all familiar with the code yet, is there anything I should know going in?
The text was updated successfully, but these errors were encountered: