Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Limit accessibility check to WCAG failures, not best practices #1087
When running an online scan at sonarwhal.com, the results from aXe are presented as accessibility failures, but it is not clear what is a true WCAG violation and what is a best practice as defined by the aXe team.
By default, limit the output of Sonarwhal to only present WCAG failures, or flag items that are best practices as such. I understand that the results from aXe expose whether a failure is a best practice or not. The aXe browser plug-in makes that distinction, so aligning with the aXe browser plug-in would also be a bonus.
Alternatively, an option to categorize failures (or disable/enable) by WCAG level and/or best practice might be a nice feature for those reading these reports.
If I run aXe in my browser, the report excludes the first error and says (note use of should and best-practice):
Neither of the issues listed in the online scanner is a WCAG failure, but the must language can confuse users who do not know WCAG and are using the tool to prioritize remediation efforts.
Sonarwhal.com online scanner
URLs in this report
Strongly agree here. While it's perfectly fine (and in keeping with other non-accessibility related test) that not following best practice is flagged, when it comes to accessibility there needs to be a clear distinction between faliures (hard failures against normative WCAG 2 success criteria) and not following opinionated best practice suggestions
referenced this issue
May 21, 2018
I just ran Sonarwhal against the same Delta page, and it now comes back without any errors from aXe. Since I last ran it, the Delta page has added a