pa11y-webservice
pa11y-webservice copied to clipboard
pa11y
Pa11y Webservice provides scheduled accessibility reports for multiple URLs
These are the tasks still missing for next release of `pa11y-webservice`: * Drop support for Node v12 (which will become unsupported in late April). * Add support for Node v16,...
The current testing suite for pa11y-webservice requires mongodb to be available and properly set up for the tests to run. This is usually not much of a problem when running...
Pa11y (not currently published) now supports multiple test runners. We need to add the ability to select runners in the webservices. Therse a couple of ways this could be done:...
Builds off https://github.com/pa11y/pa11y-webservice/pull/105 to be able to specify runners to provide support for the axe runner.
When doing a test for "WCAG2AAA" for example, every issue has the same level "AAA". https://prnt.sc/10p3p6x - In this screenshot you can see that an issue from criterion 2.4.2 which...
I'm a developer of a web accessibility testing tool that use the pa11y-webservice app. And durring the development I found a bug in tests for "WCAG2AAA". These results don't include...
Just giving a stab at adding caps for axe runners as a config - feedback welcome!
I don't think this is related to https://github.com/pa11y/pa11y-webservice/issues/115 but just wanted to link the two. Not sure why this isn't working for me. ``` $ PORT=8080 npm start (node:26780) ExperimentalWarning:...
Currently the logging is done using `console.log`/`console.error`. We should really be using a configured logger (`winston` etc) that can also label the log output so that dual dashboard/webservice deployments can...
The cron job part of the code has no testing through unit or integration tests. Integration tests don't really make sense for something that runs on a schedule, so need...