The quickest way to prove a round of fixes worked is to compare the scan before with the scan after.
Opening it
On the website's page, in Scan History, choose Compare Scans. It appears once a website has at least two scans. Pick Scan A and Scan B and choose Compare. The results always read from the earlier scan to the later one, whichever way round you picked them.
What you see
- Scores and change, where both scans have one.
- New Issues. Kinds of issue in the later scan that were not in the earlier one.
- Resolved Issues. Kinds of issue in the earlier scan that are gone from the later one.
- Unchanged. Kinds of issue present in both.
What it compares
The comparison is by kind of issue, not by instance. If the earlier scan had fifty unlabelled fields and the later one has two, that issue is Unchanged, because it is still present. For the instance counts, open each scan and compare its Unique Issues Found.
That makes Resolved a strict measure: an issue only counts as resolved when every instance of it is gone.
Getting a fair comparison
Compare scans of the same pages. If the later scan covers different pages, a new issue may simply be on a page the first scan never looked at. The easiest way to keep pages consistent is to schedule scans, which reuse the same page list every time.
Comparing after a review
A useful routine: get an Expert Manual Review, fix what it found, scan the same pages again, and compare. Resolved Issues shows your progress on the automated findings straight away, before you decide whether to get a fresh review.