Closed pinglinh closed 11 months ago
Duplicate of #54
Had a similar issue last week, but realised it was down to how I was configuring pa11y
. I was setting threshold
inside my .pa11yci.json
file, and so when the errors were below that threshold it wouldn't output what the errors were. However, if I removed the threshold
from there and used the -T
flag in the CLI, that would still report the errors even if they fell below the threshold.
Don't know if that helps at all.
@42tte hey, I'm bumping into the same issue. It appears the -T
or --threshold
don't work at all?
hi @42tte ,
You asked if I would try this: pa11y-ci --threshold 83 --config tests/a11y/pa11yci.json
But unfortunately it doesn't work. I much prefer an option in the command line rather than the config, because that way I can use the config for CI (where I don't want it to fail for the number of existing issues, but I'd like it to fail if new ones come up) wheres I want to use that same config locally to look at all the issues (so no threshold).
Is that not possible at the moment? Thanks!
Thanks all, and for the pointer to #54 @42tte. Let's track this there.
I noticed that when errors shown are under the threshold specified, the errors no longer show. Is it possible to make an enhancement to this to add the option of showing these errors anyways? I think it will be good in terms of trying to improve and get rid of these errors before pushing the code to build in our CI pipelines.