SSRF Protection
Scanning engines strictly prohibit private RFC1918 addresses, cloud metadata IPs, and internal hostnames.
Systematic accessibility progress
No specialist vocabulary is required to get started. The AccessPulse workflow guides teams step-by-step through ownership verification, automated scanning, issue tracking, human review, and progress reporting.
How AccessPulse works
Accessibility is ongoing work, not a one-time check. Here’s how teams move from setup to continuous improvement with clear visibility at every step.
Enter your public website URL and give it a name in your workspace. We store only the origin and display name—never credentials or sensitive data.
Add a unique, time-limited meta tag to your website’s HTML head to prove you own the domain. This prevents unauthorized scanning and ensures only your team can initiate checks.
Our scanner safely crawls same-origin public pages, respects SSRF protection and crawl limits, runs axe-core tests, and captures screenshot evidence—never submitting forms or using credentials.
Issues are automatically ranked by impact and frequency so you see what matters most first. Each issue includes clear explanations, fix guidance, and reproducible evidence.
Implement fixes using our guidance, then mark issues as fixed. AccessPulse tracks whether issues stay fixed or regress in future scans—helping you distinguish real progress from temporary changes.
Automation finds issues; humans judge usability. Document checks for keyboard navigation, screen-reader experience, focus order, and task completion—all in the same workflow.
Schedule regular rescans to verify fixes, detect regressions, and measure improvement over time. Clear dashboards show what’s improved, what’s unchanged, and what needs attention.
Create executive summaries that show issue trends, fix rates, and next steps for stakeholders. Perfect for demonstrating compliance efforts and planning future work.
This cycle repeats as part of your ongoing accessibility practice. Each scan builds on the last, creating a clear record of your team’s dedication to inclusive design.
Controlled boundaries
Scanning engines strictly prohibit private RFC1918 addresses, cloud metadata IPs, and internal hostnames.
Rate limits and crawl boundaries respect host resources without hammering production servers.
Screenshots are kept in private object storage and accessed through short-lived signed URLs.
Clear audit trails ensure non-automatable criteria (focus order, alt-text quality) receive human sign-off.
Ready to scan your first site?
Follow the guided setup from website ownership to your first bounded scan.