Define technical strategy to implement automatic a11y checks in GitLab UI
As a Product Accessibility Working Group, we want to create a strategy for including automated accessibility checks into our CI/CD process.
We have already discussed the following:
- GitLab UI already uses storybook/addon-a11y which is based on axe to report failures. But we want to make advantage of automation and shorter feedback loop anyways.
- For GitLab UI, we can use e2e tests with Cypress, which has axe-core plugin.
- We are aiming for WCAG 2.1 AA compliance.
- In GitLab UI, tests will be separated because they will run in a separate runtime (Cypress vs Jest).
In this epic we want to discuss and document the strategy for implementing the test cases, as well as the instructions on how to contribute to the efforts of the working group.
Edited by Paulina Sedlak-Jakubowska