Pricing

Start with complete findings. Pay for the ongoing program.

The free scanner is live today. Monitoring is the approved Release A plan, but checkout and scheduled site scans are still in development.

Current availability

Free scans are available now. The Monitoring price below is a launch commitment in the product plan—not an invitation to pay before the service is ready.

Available now

Free scanner

10 complete single-page scans per IP each UTC day.

Complete single-page findings
Plain-English remediation
WCAG references and affected elements

One public page per scan
Unsaved result held for up to 1 hour
Explicitly shared reports retained for up to 90 days

Run a free scan

In development

Monitoring

$9/month

One site with up to 25 representative pages scanned weekly.

Saved site and scan history
Weekly sampled-site scans
Regression alerts and fix verification
Shareable evidence history

12 months of subscribed history
30-day export window after cancellation
Self-serve cancellation when checkout launches

Ask about pilot access

No one-time Site Report is offered at launch. We will revisit that only if real buyers want a baseline without monitoring. See the methodology and coverage boundary.

What changes when you pay

Coverage, automation, history, and evidence.

Monitoring does not hide findings the free scanner already computed. It turns repeated assessments into a durable workflow.

Representative site coverage: Discover public pages, group similar paths, and record which templates were sampled.
Quiet regression alerts: Notify only when a finding is new or returns after being fixed.
Verification history: Preserve dated scans and the evidence that a fix was re-tested.
Honest scope: Keep automated, guided manual, and expert methods clearly separated.

Before you choose

Does a passing scan prove accessibility?

No. Automated testing reliably detects roughly a third of WCAG success criteria. Keyboard behavior, focus order, screen-reader flow, and content quality still need human review.

Why sample pages instead of scanning everything?

Repeated templates create repeated noise. Monitoring prioritizes coverage of the site’s component and path patterns, while always recording the sampled scope.