Joey Ciechanowicz

This would be useful, and would allow users to configure the runners outside of the realm of what pa11y supports. The two runners we have (HTML_CS and aXe) are both...

Well, al the runners are now part of `pa11y` in the [`lib/runners`](https://github.com/pa11y/pa11y/tree/master/lib/runners) folder. So that's much easier. So steps (in my mind) would be something like: - Add support for...

The reporters all follow the same format (they have to so that they work with pa11y automatically). But yes, this could do with better documentation about. Thanks for raising.

I personally use the `buildkite/puppeteer` Docker image for running pa11y, which I've had no problems with. It was a tad complicated getting the `node` image to install all the other...

Thanks. This sounds really useful in theory. Couple of questions: - Can heroku sites block all traffic except for whitelisted IPs? As pa11y-dashboard is not meant as a tool that's...

> Propose updating cycleReporters with error handling to cover all events and return false on reporter failure Good idea. Definitely want to log to `stderr` when a reporter method fails...

These are some lovely rewrites @ptmkenny . > wary of linking to 3rd party packages in our documentation @hollsk totally agree. Though if the docs make it clear that this...

> - Change the behavior approach: Update the results aggregation to look for the URL in the existing results and add the new results under a distinct URL appending some...

The debug flag (`-d`) should print out the actions as they're ran.

I think if we were to support passing the `--debug` flag to `pa11y` from `pa11y-ci` then we could avoid adding a new action?