Is your website an
ADA lawsuit risk?
Thousands of small businesses get demand letters every year. Scan your site free, see your risk in seconds — then fix the actual code. Not an overlay.
Your website may be leaking patient data
Most practice websites run third-party tracking pixels — Meta, Google, and others — on the very pages where patients book, log in, or fill out forms. HHS has active guidance treating that as an impermissible disclosure of patient information, and one health system recently paid $6.6 million settling exactly this. Our free scan flags every tracker on your site — the same scan that checks your ADA accessibility.
What we find
Every third-party tracker on your site, and whether it fires on a patient-facing page (booking, portal, intake). That's the pattern behind the HHS Office for Civil Rights tracking guidance and the recent hospital pixel class actions.
What you do about it
We show you exactly which pixels to remove or move off your patient pages — or route through a BAA-backed path. A plain-English fix, so you're not paying legal fees just to find the problem.
Two risks, one scan
Dental and medical practices face both ADA demand letters and HIPAA tracking complaints. One free scan surfaces both, so you're not fighting on two fronts blind.
This scan flags technical exposure to help you and your privacy officer act — it is not legal advice and does not certify HIPAA compliance. No scan or vendor can make a website "compliant."
Overlays don't work — and they get you sued
The FTC fined the largest accessibility-overlay vendor $1,000,000 for claiming a widget makes any site compliant. Courts reject overlays, and roughly 1 in 4 ADA website lawsuits target sites that had one installed. We do the opposite: find the real problems, hand you the real fixes.
1 · Scan
We test your pages against WCAG 2.1 & 2.2 Level AA and flag what a plaintiff's screen-reader test would actually catch.
2 · Fix
Ready-to-paste code fixes with step-by-step instructions for your platform — Shopify, Wix, WordPress, Squarespace. No developer needed.
3 · Prove it
A plain-English report, accessibility statement, dated good-faith remediation record, and an IRS Form 8826 worksheet (up to $5,000 credit).
Real fixes. Verified before & after.
We don't hide your site behind a widget and call it done. We find the real barriers, write the actual code, and re-scan to prove it — every fix checked by a 3-model accuracy gate before it reaches you.
Case study: citedaudit.com
47 → 100/100, 14 issues → 0. Real code fixes (contrast tokens, link underlines, form labels), then a signed before/after Verification Report.
3-model accuracy gate
Every fix is independently verified by three AI models before delivery. Anything less than a majority pass is flagged for human review — you never get a fix that breaks your page.
What you actually get
Paste-ready code + platform steps, a plain-English report, an accessibility statement, a dated good-faith record, an IRS Form 8826 tax-credit worksheet, a VPAT/ACR, and a draft demand-letter response.
We catch what free scanners miss
On our published regression corpus of 15 seeded WCAG failures (plus clean controls), axe-core alone caught 33%; wcagdefender caught all 15 — 100% of that set, with zero false positives — because we add checks a rules engine structurally can't do: color-only links, keyboard-only click traps, removed focus rings, focus hidden behind sticky headers (WCAG 2.4.11), reflow at 200% zoom, and alt-text quality. The comparison is reproducible; the harness ships in our engine.
To be clear about scope: that 100% is our seeded test set, not all of WCAG. No automated tool — ours included — catches everything. Independent testing finds automated scans reliably flag only about a quarter of WCAG 2.1 AA issues; the rest need human judgment. That's the next card.
What a scan — even ours — can't catch
Automated and AI testing is fast and catches the most-litigated issues, but roughly a quarter to a third of WCAG needs a human. A tool can't reliably judge whether alt text is meaningful, whether the reading and focus order make sense, whether an error message actually helps, or whether a page works for someone driving a screen reader by keyboard. Anyone selling you "AI makes your site accessible" is the reason the FTC hands out fines.
Our answer: automate what can be automated, hand you real code fixes a human applies and verifies, and — for the issues that need a person — flag them and offer an expert manual review plus testing by people with disabilities. Honest coverage beats a false green check.
Passing yesterday doesn't mean passing today
Accessibility isn't a one-time certificate. The benchmark keeps advancing, and your site changes with every edit. WCAG 2.2 (current since 2023) added new Level-AA requirements a 2.1 check never looked for:
- Target Size (buttons/links big enough to tap)
- Dragging Movements (alternatives to drag)
- Focus Not Obscured (keyboard focus stays visible)
- Consistent Help (help in the same place)
- Redundant Entry (don't re-ask for the same info)
- Accessible Authentication (no memory-test logins)
See where you stand — then fix it
Free scan
Instant risk score + issue breakdown.
- Accessibility score
- Issue types & counts
- Overlay detection
Emergency Fix Pack
Got a demand letter? Everything you need in 48–72 hours.
- Full multi-page scan
- Real code fixes + platform steps
- Report, statement, good-faith record
- IRS 8826 worksheet + draft response
Monitoring
Stay aligned as the standard & your site change.
- Scheduled re-scans
- Regression alerts
- WCAG 2.2 AA coverage
See full pricing, the Done-For-You tier & how we compare to overlay vendors →