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
pa11y-ci adds some really nice functionality for aggregating test runs across multiple sites. We should add it to the container as this kind of approach is essential.
pa11y-ci is not yet ported to pa11y v5, and uses pa11y itself as a dependency. Do we have duplicate code in the image? Do we have multiple images? Do we find a way to use whatever pa11y version pa11y-ci pulls in? I'm partial to the middle answer:
Replacing the existing versioning with something more like this:
pa11y-ci added here #7 . keeps pa11y as well, which gives users the option to pass either pa11y or pa11y-ci as the command to the service using the image.
then docker-compose run --rm report will generate a report.json in test/pa11y that can be used by another service (say, something hosting the parsed dashboard report)
pa11y-ci adds some really nice functionality for aggregating test runs across multiple sites. We should add it to the container as this kind of approach is essential.
pa11y-ci is not yet ported to pa11y v5, and uses pa11y itself as a dependency. Do we have duplicate code in the image? Do we have multiple images? Do we find a way to use whatever pa11y version pa11y-ci pulls in? I'm partial to the middle answer:
Replacing the existing versioning with something more like this:
Once this is in, we can follow-up by adding a custom reporter, such as https://github.com/tjheffner/vue-pa11y.
The text was updated successfully, but these errors were encountered: