[Issue]
Recently many clients have asked to separate WCAG 2.0 and 2.1 violations.
Unfortunately, the AMP "View All Instances" page currently only can filter out 2.0 issues if the report standards included WCAG 2.0 and WCAG 2.1, but the 2.1 criteria cannot be filtered out because the WCAG 2.0 violations are also included in WCAG 2.1.
In order for us to provide WCAG 2.1 only issues to customers, we have to do that manually which is not feasible when there are hundreds of violations to sift through. Consultants have to review each violation and separate them manually in the violations export which can lead to human error.
[Suggestion]
Allow customers to filter 2.0 only issues and 2.1 only issues on the "View All Instances" page when the AMP report standards are WCAG 2.1 only (without including the additional WCAG 2.0 standards ).
This would make it more flexible for the client to prioritize their issues.
Amy Li
We'd like to have @JonAvila weigh in on this.
Attachments Open full size
I agree this is an issue. Take for instance we test for WCAG 2.1 and customer wants to to know the items that are 2.1 issues only that would not been issues for 2.0. it would be helpful to filter the items in this way or have a column with the standard allow the user to sort or filter on the column when exported to Excel.
Attachments Open full size
I have a client that wants exactly what @JonAvila is describing.
Attachments Open full size
Often too we do a 2.1 audit, but then produce a 2.0 VPAT. So it would be great to filter out the items that we don't want to see.
Kevin Murphy
Accessibility Consultant
Level Access
kevin.murphy@LevelAccess.com
415.432.6992
The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.
Attachments Open full size
Filter by 2.0 is not an issue if the report has 2.0 already mapped because we can just check 2.0. It's really 2.1 that is the challenge because 2.1 includes 2.0 standards.
Attachments Open full size