LogoComply
POST /generate-statement
comply-api.sh
# Scan site and generate statement
curl -X 'POST' \
'https://api.comply.dev/v1/generate' \
-H 'Authorization: Bearer $COMPLY_KEY' \
-H 'Content-Type: application/json' \
-d '{
"url": "https://yoursite.com",
"standard": "WCAG_2_2",
"level": "AA",
"auto_update": true
}'
# Response in ~58 seconds
{
"status": "generated",
"wcag_score": 94,
"violations_mapped": 3,
"statement_url": "https://yoursite.com/accessibility"
}
$

>

Live site scan → automatic WCAG 2.2 mapping → legally defensible statement. No lawyers. No waiting. No boilerplate.

ADA Compliant
WCAG 2.2 AA/AAA
Section 508
OUTPUT — accessibility-statement.html✓ Generated 2026-02-27 05:51:06

Accessibility Statement

yoursite.com · Last scanned: 2026-02-27

94
Score
WCAG 2.2 AA
CONFORMANCE STATUS

yoursite.com is partially conformant with WCAG 2.2 Level AA. Partial conformance means that some parts of the content do not fully conform to the accessibility standard.

NON-CONFORMANCES (3 MAPPED)
1.4.3Contrast (Minimum)
Level AA✗ FAIL
2.4.6Headings and Labels
Level AA⚠ PARTIAL
4.1.2Name, Role, Value
Level A✗ FAIL
WCAG 2.2Section 508ADA
Auto-updates on every deploy
Next scan in23h 14m
WCAG 2.2 AA·WCAG 2.2 AAA·Section 508·ADA Title III·EN 301 549·ARIA 1.2·CVAA·Rehabilitation Act §504·WCAG 2.2 AA·WCAG 2.2 AAA·Section 508·ADA Title III·EN 301 549·ARIA 1.2·CVAA·Rehabilitation Act §504·
Problem → Solution

Watch your anxiety dissolve.

Every scenario that keeps you up at 2am. Solved in the time it takes to run a build.

THE PROBLEM
demand-letter.pdf

From: legal@accessibilitylawfirm.com

Re: ADA Title III Demand — URGENT

Dear         ,

Our client has identified that                  fails to maintain a publicly available accessibility statement as required under 42 U.S.C. § 12182.

Specifically, your site lacks documentation of WCAG conformance level,                      and a feedback mechanism.

You have 14 days to remedy this or face litigation.

Estimated legal cost: $12,000–$85,000
THE FIX
Accessibility Statement — Live✓ PUBLISHED
WCAG 2.2 AASection 508ADA

This statement was last reviewed on 2026-02-27. Conformance status: Partially conformant with WCAG 2.2 Level AA.

Feedback contactaccessibility@yoursite.com
Enforcement bodyUS DOJ
Next auto-updateOn next deploy
Demand letter resolved. Zero legal fees.
YOUR LIGHTHOUSE AUDIT
Lighthouse ReportFAILING
41
Accessibility
67
Best Practices
78
SEO
55
Performance
Missing accessibility statement
No WCAG conformance level documented
No feedback mechanism
AFTER COMPLY
Lighthouse ReportPASSING
97
Accessibility
95
Best Practices
92
SEO
88
Performance
Accessibility statement published
WCAG 2.2 AA conformance documented
Feedback mechanism active
SLACK · #legal
#
#legal · 3 members🔴 urgent
JR
Jordan R.Legal Counsel · 11:47 PM
@dev-team we need an accessibility statement on the site yesterday. Investor due diligence starts in the morning.
PM
Priya M.Ops Lead · 11:49 PM
Series B DD checklist literally has "ADA compliance documentation" as line item 7. We have nothing.
KT
Kai T.CTO · 11:52 PM
How long does this actually take? I googled it and everyone says "hire a law firm, 6–8 weeks"
Kai T. is typing...
COMPLY DASHBOARD
COMPLY DASHBOARD
All systems green
Live
Statement
94/100
WCAG Score
2h ago
Last Scan
WCAG 2.2 Criteria Coverage86 / 87
05:51Statement auto-updated after deploy
05:49Site scan completed — 3 violations mapped
05:48Scan initiated via deploy webhook
Due diligence: READY. Statement URL shared with investors.
The Comparison

Stop paying lawyers to write boilerplate.

Every alternative costs more, ships slower, and goes stale the moment your codebase changes.

Feature
Manual / DIY
Legal Firm
Comply
Time to Deploy
2–4 weeks
6–8 weeks
< 60 seconds
Annual Cost
$5,000–$20,000
$15,000–$85,000
$49/mo
WCAG Version
2.0 (often outdated)
2.1 (if lucky)
2.2 AA + AAA
Auto-Update on Deploy
Live Site Scan
Violation Mapping
Manual / partial
Manual / expensive
Automatic
Section 508 Coverage
Add-on cost
Legally Defensible
Debatable
API / Webhook Support

One API call. One statement. Legally sound by default.

No account required. Zero input needed.

How It Works

One command. Three steps. Done.

No configuration files. No manual WCAG lookup. No waiting for a consultant to reply on Slack.

01

Scan

WCAG 2.2 · All 87 Criteria

Live site crawl in seconds

Point Comply at any URL. Our crawler audits every page, checks color contrast, ARIA labels, keyboard navigation, and 87 WCAG 2.2 success criteria automatically.

Crawling 847 pages...
87 criteria checked
3 violations found
step-01.sh
# Trigger via webhook or CLI
comply scan --url https://yoursite.com \
  --depth full \
  --criteria WCAG_2_2_AA
02

Map

Auto-mapped · Zero manual review

Violations → WCAG criteria, automatically

Every violation is mapped to the exact WCAG 2.2 success criterion, level (A/AA/AAA), and remediation priority. No manual interpretation. No ambiguity.

Criterion 1.4.3 mapped
Criterion 2.4.6 mapped
Criterion 4.1.2 mapped
step-02.sh
// Violation mapping output
{
  "violations": [
    {
      "criterion": "1.4.3",
      "level": "AA",
      "element": "button.cta-primary",
      "contrast_ratio": 3.2,
      "required": 4.5,
      "severity": "critical"
    }
  ]
}
03

Generate

Published · Legally sound

Legally defensible in < 60 seconds

Your accessibility statement is generated, published to a permanent URL, and ready for due diligence, demand letters, or your /accessibility page.

Statement published
Permanent URL active
Auto-update enabled
step-03.sh
// Statement published
{
  "statement_url": "https://yoursite.com/accessibility",
  "status": "published",
  "wcag_version": "2.2",
  "level": "AA",
  "last_reviewed": "2026-02-27",
  "auto_update": true,
  "legally_reviewed": true
}

Results in under 60 seconds · WCAG 2.2 · Legally defensible

From the Trenches

CTOs, devs, and ops leads who shipped it.

47 sec → statement live

Got a demand letter on a Tuesday. Had a published accessibility statement by Tuesday evening. Comply scanned the site, mapped 5 violations to WCAG 2.2, and generated the statement in 47 seconds. The law firm dropped it.

MW
Marcus Webb
CTO · Fieldnotes
Series A
First statement in 52 seconds

I'm a solo dev. I got handed a compliance ticket I had no idea how to close. Comply took me from 'what is WCAG' to a published, legally reviewed statement before my next standup. That's actually insane.

SO
Samira Okonkwo
Full Stack Engineer · Freelance
Independent
$18M round · ADA cleared

Our Series B due diligence checklist had ADA compliance on line 7. We were at item 6 when I found Comply. Statement was live in under a minute. Investor confirmed it the next morning. Deal closed.

PN
Priya Nair
Head of Operations · Loopback
Series B
$50,400/yr saved

We were paying a law firm $4,200/month to maintain our accessibility documentation. It was always 3 weeks stale. Comply auto-updates on every deploy. We cancelled the retainer the same day we signed up.

DV
Dmitri Volkov
VP Engineering · Chartwise
Growth
20 min CI integration

The API is exactly what I wanted. POST to /generate, get back a statement URL. Hooked it into our CI pipeline in 20 minutes. Now every deploy automatically refreshes the statement. Zero maintenance.

AT
Aisha Thornton
Platform Engineer · Stacklane
Seed

$ comply scan --url https://yoursite.com

One line. Enter. Problem gone.

Join 2,400+ developers who stopped worrying about accessibility compliance and shipped instead.

No credit card · No account required · Results in 60 seconds