Scan history, with context.
Return to past accessibility results, revisit findings, and compare similar scans to see what changed after you updated your site.
A record of checks over time, not a compliance certificate.
See the story behind each scan
Open saved results, inspect details, and compare like-for-like scans when available.
01
Saved records
Return to available previous scan summaries and findings.
02
Finding details
Revisit affected elements and their available guidance.
03
Scan comparison
Review differences between scans with similar scope.
04
Progress review
Use updated scans to see what automated checks report.
Scan history is not a certificate
History tracks the supported automated checks recorded by ScrollAccess. A smaller finding count does not confirm that every issue or visitor barrier is resolved.
Keyboard and focus
Test navigation and visible focus manually.
Screen readers
Check names, instructions, and reading order.
Dynamic content
Test updates, dialogs, and interactive states.
Whole user journeys
Try key tasks from start to finish.
Use manual review alongside automated scan history.
Keep progress connected to real updates
01
Run a scan
Choose a supported page or site scope.
02
Open scan history
Return to an earlier saved result.
03
Check the scan scope
Confirm pages and scan mode.
04
Review findings
Inspect categories and affected elements.
05
Compare when available
Choose a newer scan with similar scope.
06
Investigate changes
Verify individual findings in context.
07
Update and publish
Make appropriate changes in Webflow.
08
Scan again and test
Review updated results and manual checks.
Webflow note: Publish your Webflow updates before rescanning to review the live version.
Use a consistent comparison checklist
- Compare the same pages and site scope
- Check that scan modes match
- Review score and finding categories
- Open changed findings individually
- Confirm the current page still needs attention
- Add manual checks for behavior and access
Frequently asked questions
Scan history is a record of previous scans, including available summaries and findings, so you can revisit results over time.
If comparison is available for your saved scan records, you can select scans to review how their results differ. Compare scans with similar scope for the most meaningful view.
Review the scan scope, score, number and categories of findings, and individual issues. Confirm that both scans cover the same pages or elements before interpreting changes.
Results can change because the website content changed, the scan covered a different scope, or the checks returned different findings. Review scan details and individual results to understand the difference.
No. It tracks results from supported automated checks. It is not an accessibility certification or a guarantee that every issue has been found or resolved.
Rescan after meaningful content or design changes, and when you want to review the effect of updates. The right schedule depends on how often your site changes and your review process.
Yes. An earlier finding can help you revisit an issue or understand what a past scan reported. Check the current page and run a new scan before assuming the issue is still present.
It may indicate that the scan found fewer issues within its scope, but it does not establish that the full visitor experience improved. Review the changed findings and perform manual testing as needed.
Scan history contains the data recorded by the scan workflow. Manual testing results should be recorded separately unless your ScrollAccess account provides a specific way to add them.
Scan retention and deletion options depend on the features available in your account. Check the scan history controls and your account’s data settings for available options.
No matching FAQs found.