-
Notifications
You must be signed in to change notification settings - Fork 21
document issues
Anika Henke edited this page Jun 15, 2022
·
2 revisions
There is no consistent and unified way to document WCAG issues. How you do this will depend on personal preference or however best works for the team. Some helpful resources include:
- W3C's Website Accessibility Evaluation Report Generator
- Anika Henke's WCAG audit template (Google Sheet)
- a checklist based on what the UK monitoring team use (Google Sheet) - this is partially based on Anika Henke's version
- Richard Morton's WCAG 2.0 accessibility testing template (XLSx) - note this is based on an older version of WCAG
- the US government's Accessibility Conformance Reporting Tool (ACRT) tool which creates reports for Section 508 checks which is the equivalent to WCAG 2.0 AA
- Accessibility Insights has different evaluation methods but creates a report
- putting issues straight into GitHub, Trello, Google Doc, or other tracking tools