Lovable's AI defaults to placeholder-only inputs (no <label> elements), low-contrast accent colors, and clickable divs that aren't keyboard-focusable. These are the three patterns plaintiff law firms most often cite in ADA demand letters in 2025. The fault isn't yours — the AI's training data taught it these patterns are normal — but the legal exposure is.

Median scan on a commercial Lovable app surfaces 5–12 findings: usually a Critical missing-label on the signup or checkout form, a High color-contrast issue on the primary CTA, 1–2 alt-text gaps on hero images, and 2–4 structural findings. Privacy: if you wired up Posthog or Mixpanel via the Lovable integrations panel, those fire pre-consent unless you specifically gated them.

Title III applies to 'places of public accommodation' — commercial entities serving the public. A Lovable landing page that captures emails for a paid product is commercial. A side-project demo with no monetisation may be 'arguable' status. Comply Code classifies your site and recalibrates findings accordingly — you won't get a panic alert on a personal site.

Yes — *.lovable.app preview URLs scan exactly like your custom domain. We run Playwright against the rendered DOM, so anything users see is what we audit. If you've deployed to a custom domain via Lovable's connect-domain feature, point us at the custom domain for the most accurate scan.

Yes — every Comply Code finding ships with a copy-paste prompt. Open your Lovable project, paste the prompt into the chat, and Lovable's agent applies the fix. Re-run the scan to verify; the finding should disappear.