A scan is a snapshot. The value comes from scanning again after you have changed something.
Running another scan
Open the website and choose Rescan. You choose pages again, so you can either repeat the same selection to compare like with like, or pick a different set to widen your coverage.
Compare like with like
If your aim is to prove an improvement, scan the same pages you scanned before. Changing the selection at the same time as changing the site makes the two scores impossible to compare, and a rise that came from picking easier pages is worse than no measurement at all.
The wait on the Free plan
On Free, there is a three day wait between scans of the same website. Every paid plan removes it.
In practice it is less restrictive than it sounds. Accessibility fixes usually involve a developer, a change, a deploy, and often a release cycle. Three days is frequently shorter than the fix.
When a rescan is worth it
- After you have fixed things, to confirm they are actually fixed.
- After a redesign or a template change, which is when regressions appear.
- After adding a major new section.
- Periodically, even when nothing obvious has changed. Sites drift as content is added.
Do it automatically
On any paid plan you can schedule scans so you do not have to remember. See Scheduling recurring scans.