You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a gcds developer, I want accessibility tests to run on our documentation website so that I can be sure it meets accessibility checks every time I update the site with a PR
β Definition of Done / Outcomes
Done when there is a github action that runs an accessibility check
Done when the github action runs on a PR
Done when the github action runs on a deployment / when the website is published
π Acceptance criteria
Test script runs for every page, both in EN and FR, in the documentation website
π User story
As a gcds developer, I want accessibility tests to run on our documentation website so that I can be sure it meets accessibility checks every time I update the site with a PR
β Definition of Done / Outcomes
π Acceptance criteria
π More info
Notify has these on their CI (from Andrew L):
Here is our workflow that tests staging every 3 hours for a11y:
https://github.com/cds-snc/notification-admin/blob/main/.github/workflows/cypress-staging.yaml
We also have a full suite of tests that run on every PR (including the same a11y checks as above):
https://github.com/cds-snc/notification-admin/blob/main/.github/workflows/test-admin-deploy.yaml#L153
We wrote a little helper to wrap axe and the html validator (and a few other things that were specific to problems we encountered, like dead links) here:
https://github.com/cds-snc/notification-admin/blob/main/tests_cypress/cypress/support/commands.js#L11
Using that helper, you could scan your component pages (or wherever) like this:
. π« Out of scope
_ If possible, give precisions on what is not part of this work_
The text was updated successfully, but these errors were encountered: