WCAG 2.1 AA audit reports
Built for
one person.
Ramps
everyone.
In 1945, Kalamazoo poured a curb down to street level for wheelchair users. It ended up carrying every stroller, hand truck and delivery bike in town too. curbcut finds the ramps missing from your client's website — before the EAA fine does.
One-time purchase. Runs on your machine. No client site ever leaves it.
Beyond axe-core
The checks free scanners don't run
Lighthouse and the free tools read the page once. curbcut drives it — tabs through every control, watches where focus goes, and clears consent banners before measuring, because a banner sitting over the page means you're auditing the banner.
2.1.1
Keyboard traversal
Visible controls the Tab key never actually reaches.
2.4.7
Focus indicator
Elements that look identical focused and unfocused.
2.1.2
Keyboard trap
Focus that cycles inside a widget and can't escape.
2.4.3
Tab order
Positive tabindex values that scramble reading order.
2.4.1
Bypass blocks
No skip link on a page with heavy navigation.
1.4.10
Reflow
Sideways scroll at 320px, naming the element at fault.
Feel it, don't just read about it
Tab through both of these
Two donation forms. Same fields, same layout. Press Tab from the first input in each and watch — or listen — to what happens.
Skip this demo — jump to the sample report →
The left form has no visible focus ring and a scrambled tab order — amount, then email, then name. The right form announces exactly what it is, in the order a sighted user reads it. This is what shows up as a finding in the PDF, worded exactly this plainly.
What you hand the client
Not a technical dump. A billable deliverable.
Every scan produces a branded PDF: score, severity breakdown, legal context, and every finding written for a client to actually read — who it affects, and how to fix it.
Finding — critical
"The donation form's fields have no labels, so a screen reader announces them as just 'edit text, edit text.' Someone donating with low vision can't tell which box is the amount."WCAG 1.3.1 & 4.1.2 — Info and Relationships, Name Role Value
Written to survive being forwarded
A client doesn't read axe-core JSON. They read "someone donating with low vision can't tell which box is the amount" and forward it to their board. That sentence is the whole product.
Every report also states plainly what it didn't check — see below. Honesty here is what makes the findings that are in it hard to argue with.
Own it, don't rent it
Every competitor is a subscription. This isn't.
Pay once. Unlimited scans, unlimited clients, white-label PDF, runs entirely on your machine.
| Tool | Price | Cost at 12 months |
|---|---|---|
| curbcut — founding licence | $59 once | $59 |
| A11yProof | $29 / mo | $348 |
| Accessalyze | $99 / mo | $1,188 |
| AISO Studio | $599 / mo | $7,188 |
Free teaser scan, no card, top 5 issues.
The part competitors don't put on page one
What this can't catch
Static rule checking detects roughly a third of WCAG success criteria failures. The keyboard and reflow checks push past that, but they narrow the gap — they don't close it.
Nothing here can judge whether alt text is accurate, whether focus order matches the visual reading order, whether error messages are clear, or how a page behaves with a screen reader actually running. Content behind a login, inside a PDF, or reachable only after interaction isn't assessed at all.
A clean automated result is necessary but not sufficient for conformance — and the report says so, on its own pages. That's deliberate: it's legally safer, and it's the natural opening for the manual audit you sell on top.