-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pa11y-ci error output not as descriptive as pa11y error output #64
Comments
I'm having the same issue. Is it possible to have a more verbose fail messages option for pa11y-ci like those in pa11y? |
@dominicfraser where did you learn that the rule name had the I'm trying to find an equivalent for the |
It was pure chance unfortunately, searching around issues and finding someone who mentioned using |
For the cases where warnings or notices are included, the |
…a11y#64) Replace chalk with kleur as a lighter alternative, and consistent with pa11y-reporter-cli. To remove duplication, and get console output consistent with pa11y, leverage pa11y-reporter-cli for detailed results.
As first noted as a comment in issue 60:
pally-ci
does not output the specific guides that fail in the same waypa11y
does, instead just a suggestion of how to fix. This means if you want to ignore one rather than fix it then it takes additional research to find out what it is.Specifically, this was painful when having to search through pa11y issues to discover that
WCAG2AA.Principle1.Guideline1_4.1_4_3.G18
is actually added as an ignored rules ofWCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
- whereas inpa11y
main it lists the exact code that fails.Would it be possible to output the ones that fail, as they are not always exactly the same (as proven) in the list of CodeSniffer Rules?
An example ignore list:
The text was updated successfully, but these errors were encountered: