Issue Register
One register for every issue — from the scanner, your own review or a visitor — with priority, an owner, a due date and a retest when you say it is fixed.
How it works
- Findings become issues that persist across runs, so the same problem is tracked rather than re-reported as new.
- Each issue can be open, resolved, ignored or accepted as a risk — with notes and a full history of who changed what.
- Occurrences show exactly where on which pages the issue appears.
- Issues come from the scanner, from your own manual review and from visitor reports, each marked with its source. Priority is worked out from the impact, with the reason shown; you can change it if you say why.
- When you have fixed something, request a retest: the affected pages are scanned again and the result is recorded on the issue.
Details
- Each issue links to guidance on the WCAG criterion it relates to and how it is usually fixed.
- Export the register as CSV or JSON, or create a GitHub or Jira ticket from any issue.
What it does not do
- It does not change your website’s code. Fixes are made by you or your developers; a re-assessment confirms them.
- An owner is a name you record, not a team seat.