Quick Start

Get from signup to your first scan results in under five minutes. This guide walks through the normal path a new Agency or Enterprise account takes; Starter and Free behave the same, with lower quotas.

Create your account

Sign up at /signup with email and password, Google, or GitHub. Accept the Terms and Privacy Policy on the same form — the Continue buttons won't enable until you do.

A personal organization is created automatically — named after your display name (“Alex's Team”). You can rename it any time at Settings → Organization.

If you land on the pricing page and pick a paid plan, the chosen tier and billing period are threaded through signup — as soon as your email is confirmed, the Paddle checkout overlay opens automatically.

Add a site

Open Sites in the sidebar and click Add Site. Enter a name (for your reference) and the URL you want to monitor. The dialog accepts any public site.

If the platform requires ownership verification (set by your admin), the dialog also asks which verification method you prefer (DNS TXT record or HTML meta tag). If verification is optional, no method picker appears — you can scan right away and set up verification later when it matters (for the Accessibility Seal, for example).

Verify ownership (if required)

On the site detail page, an amber banner at the top spells out exactly what to add to your site. Two methods are supported:

  • HTML meta tag — paste a <meta name="allyproof-verify" content="…"> into the <head> of your homepage.
  • DNS TXT record — add a _allyproof-verify TXT record on your domain with the token value.

Deploy the change, then click Verify. If the check passes, the banner disappears and scanning unlocks. If it fails, double-check that the tag is in <head> (not body) or give DNS a few minutes to propagate.

Run your first scan

Click Rescanin the site detail hero (the button reads “Run first scan” on never-scanned sites). The scan:

  1. Discovers pages from your sitemap, or crawls from the homepage if none is declared.
  2. Opens each page in a headless Chromium and runs axe-core, HTML_CodeSniffer, and APCA in parallel.
  3. Deduplicates findings across engines and groups them by rule × page.
  4. On Starter and up, generates AI fix suggestions in the background.
  5. On Agency and up, runs Layer 4 AI pattern checks for partially-automatable WCAG criteria.

A live progress panel shows pages as they're processed. Manual scans typically complete in a minute or two for small sites; the maximum page count scales with your plan (25 on Free up to 10 000 on Enterprise).

Review the results

The site detail page now shows three tabs:

  • Overview — score, severity breakdown, new-vs-resolved diff, litigation-risk card, and publish actions (share report, accessibility statement, seal).
  • Scans — scan history, violation trend, and per-page result table with links back into the page.
  • Settings — ownership details, page-limit override, and the danger zone.

Click the large Review N issues →action at the top to jump into the per-site issue list. Each row carries severity, rule ID, WCAG criterion tags, page count, and a “new” badge if the finding first appeared in the most recent scan.

Opening an issue shows how to fix it (scanner guidance up-front, an AI-generated before/after code suggestion on paid plans), every affected element with its screenshot, and a comment thread for your team. Workflow states move from open → in progress → resolved, or sideways to suppressed (with a reason code) or accepted exception. Bulk actions on the list page let you resolve many at once.

Share the report

From the site detail Overview tab:

  • Share report creates a public, read-only link anyone can open — no login required. Expires in 30 days by default; revocable from the same screen.
  • Publish statement generates an accessibility statement at a permanent URL (/statement/<slug>).
  • Generate VPAT (from the Reports page in the sidebar) produces a draft Voluntary Product Accessibility Template across all 56 WCAG 2.2 AA criteria.

Next steps