See what changed. Track scan history.
Open saved scans to inspect findings and compare runs after Webflow updates.
Review issue details and affected content before deciding what to investigate next.
Run. Review. Update. Compare.
Keep each result connected to a clear next step.
01
Run a scan
Choose a supported page or site.
02
Review findings
Group results by category or severity.
03
Inspect details
Check issue details and affected content.
04
Publish updates
Make suitable changes in Webflow
05
Compare again
Use a similar scope to see what changed.
Run scans after publishing, then compare similar pages and site scope.
A change is a clue, not a verdict.
A result may appear, disappear, or remain after an update. Differences also depend on scan scope and what the scanner could access.
Disappeared
No longer detected
Verify the page and its behavior. A missing result alone does not confirm the concern is resolved.
Still present
Detected again
Review the element in context. Check what changed and decide what to investigate next.
New result
Newly detected
Compare similar pages and scope. A difference may reflect content or access changes between scans.
Compare like-for-like scans where possible.
A scan is a snapshot, not a full assessment.
Results reflect supported automated checks at the time the scan ran. Keyboard access, focus visibility, screen readers, dynamic interactions, and complete visitor journeys may need manual testing.
Scan history and scores are not accessibility certification or proof of legal compliance.
Frequently asked questions
Get answers about ScrollAccess, website accessibility scanning, AI powered guidance, accessibility tools, WCAG insights, and supported platforms.
Saved scans you can reopen to inspect findings and compare runs.
Available issue details, affected content, and category or severity.
Yes. Similar pages and site scope make changes easier to interpret.
Site updates, different scope, or scanner access can affect results.
Not by itself. Verify the page and behavior, then rescan comparably.
Retention follows current ScrollAccess practices; see the Privacy Policy.
No. Scores summarize supported checks, not accessibility as a whole.
Investigate, update in Webflow, publish, then run a comparable scan.
Not fully. Test keyboard, focus, screen-reader output, and interactions.
No. Scanning saves results; it does not edit or publish your site.
No matching FAQs found.