Hi HN — we built AuditReady because small agencies keep getting asked to hand clients "an accessibility report," and the tools that produce one are enterprise platforms with quote-only pricing.
Paste a URL and you get a free instant scan of that page: 12 deterministic checks against the raw HTML, each finding tagged with its WCAG 2.2 success criterion and a suggested fix.
If you want something to hand over, $29 buys a one-off full report with your agency's name at the top — every finding, a manual-review checklist, print-to-PDF. No account, no subscription, nothing about the visitor stored. What it deliberately doesn't do (and says so on the page):
No browser, no JavaScript execution. It fetches the HTML server-side and parses it with Cheerio, so client-rendered pages will show fewer findings than they actually have.
One page, not a crawl — it's a snapshot of the URL you give it.
Automated testing catches only a minority of WCAG issues, so the report is explicit that it is not a compliance guarantee or legal advice.
A real example — a captured report for python.org:
https://feaefe371424d0725b266468856c9101.ctonew.app/report?d...
Security notes, for the curious: the fetcher refuses loopback/private/link-local targets and re-checks every redirect hop (max 5), with a 15-second deadline, a 3 MB response cap, and a 5-scans-per-minute-per-IP rate limit.
Happy to answer anything — we'll be in the thread through the day.
After all three are in the box: add comment → done. I'm watching the thread live.
Hi HN — we built AuditReady because small agencies keep getting asked to hand clients "an accessibility report," and the tools that produce one are enterprise platforms with quote-only pricing.
Paste a URL and you get a free instant scan of that page: 12 deterministic checks against the raw HTML, each finding tagged with its WCAG 2.2 success criterion and a suggested fix.
If you want something to hand over, $29 buys a one-off full report with your agency's name at the top — every finding, a manual-review checklist, print-to-PDF. No account, no subscription, nothing about the visitor stored. What it deliberately doesn't do (and says so on the page):
No browser, no JavaScript execution. It fetches the HTML server-side and parses it with Cheerio, so client-rendered pages will show fewer findings than they actually have. One page, not a crawl — it's a snapshot of the URL you give it. Automated testing catches only a minority of WCAG issues, so the report is explicit that it is not a compliance guarantee or legal advice. A real example — a captured report for python.org:
https://feaefe371424d0725b266468856c9101.ctonew.app/report?d... Security notes, for the curious: the fetcher refuses loopback/private/link-local targets and re-checks every redirect hop (max 5), with a 15-second deadline, a 3 MB response cap, and a 5-scans-per-minute-per-IP rate limit.
Happy to answer anything — we'll be in the thread through the day.
After all three are in the box: add comment → done. I'm watching the thread live.