This report was prepared for esigna.app. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Score 86 since Nov 15, 2026 (86 → 86). New: Elements must meet minimum color contrast ratio thresholds.
Clean bill of health since Oct 2, 2026, serial WO-2026-0277. View the certificate
Opportunities
These are the issues most likely to matter to a regulator, an app store, or an attacker. Fix them first.
Elements must meet minimum color contrast ratio thresholds~20 min
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <span class="inline-flex items-center rounded-full bg-lv-mono/[0.08] px-1.5 py-[3px] font-sans text-[11px] leading-none font-medium tracking-normal text-lv-mono
WCAG wcag2aa, wcag143. Web accessibility is enforced under the ADA (US, thousands of private suits a year), Section 508, the European Accessibility Act, the UK Equality Act, and AODA (Ontario).
Diagnostics
Worth fixing. Not an emergency.
Privacy policy is missing 2 expected disclosures~30 min
Not found in the policy text: states a legal basis (eea/uk users); mentions the right to complain to a regulator. Last updated November 20, 2026.
GDPR Art. 13(1)(c)-(d) · GDPR Art. 13(2)(d)
<!-- Sections your privacy policy at https://esigna.app/privacy does not have.
Paste each under a heading of its own, in the order shown, and update the
date at the top of the policy. -->
## Legal bases (EEA/UK users)
Where the GDPR/UK GDPR applies, we rely on: performance of a contract with you
(providing the Service), your consent (marketing email; you may withdraw it at any time), our legitimate interests in
operating and securing the Service, and compliance with legal obligations.
## Complaints
If you are unhappy with how we handle your information, tell us first at [[email protected]]. You may also lodge a complaint with your data-protection authority (in the UK, the ICO; in the EEA, the supervisory authority of your country).
---
_Generated from what the scanner observed on esigna.app on November 22, 2026. Confirm each section matches what you actually do; not legal advice._Missing 3 security headers~15 min
Not set: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. These defend against clickjacking, MIME sniffing, and protocol downgrade.
// next.config.js — Missing on your site: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. The Content-Security-Policy below already allows Clerk, Calendly; add the domain of anything else you load to script-src or connect-src, then re-scan.
/** @type {import('next').NextConfig} */
const securityHeaders = [
{ key: 'Strict-Transport-Security', value: "max-age=63072000; includeSubDomains; preload" },
{ key: 'X-Content-Type-Options', value: "nosniff" },
{ key: 'X-Frame-Options', value: "SAMEORIGIN" },
{ key: 'Referrer-Policy', value: "strict-origin-when-cross-origin" },
{ key: 'Permissions-Policy', value: "camera=(), microphone=(), geolocation=()" },
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' https://*.clerk.accounts.dev https://*.clerk.com https://assets.calendly.com 'unsafe-inline'; connect-src 'self' https://*.clerk.accounts.dev https://*.clerk.com; img-src 'self' data: https: https://img.clerk.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src https://calendly.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" },
];
module.exports = {
async headers() {
return [{ source: '/:path*', headers: securityHeaders }];
},
};No security.txt for vulnerability reports~5 min
A /.well-known/security.txt file tells researchers how to report a problem before it becomes a breach. Two lines: Contact and Expires.
RFC 9116; expected by many bug-bounty and disclosure norms.
What these findings expose you to
For scale: the privacy items fall under GDPR's top tier (up to 4% of turnover; small-business fines for missing notices and cookie consent have run from the low thousands of euros upward) and, for California users, CalOPPA at up to $2,500 per violation and CCPA at roughly $2,500 to $7,500 per violation once you pass its thresholds; the security items sit under GDPR Art. 32 (up to 2% of turnover) and the FTC's security enforcement, where the real cost arrives with a breach and its mandatory notifications; the accessibility violations are the kind that draw private ADA suits, thousands a year, usually settled for $5,000 to $25,000 plus the plaintiff's fees. In practice the first step is almost always a complaint and a notice with a deadline; the cost comes from ignoring it. These are published maximums and reported ranges, not a prediction.
GDPR / UK GDPR, transparency and consent · EU, EEA, UK1 finding
Maximum. Up to €20 million or 4% of worldwide annual turnover, whichever is higher (Art. 83(5)); UK: up to £17.5 million or 4%.
Usually. A complaint to a data-protection authority, then a notice with a deadline to fix. Published fines against small businesses for missing notices and cookie consent have run from the low thousands of euros upward; the largest cookie-consent fines have been in the tens of millions.
Applies: Any site with users in the EU or UK, regardless of where the company is. Enforced by regulators.
GDPR / UK GDPR, security of processing · EU, EEA, UK1 finding
Maximum. Up to €10 million or 2% of worldwide annual turnover (Art. 83(4)); UK: up to £8.7 million or 2%.
Usually. Fines follow a breach, not a scan. If exposed data reaches users, breach notification to the regulator within 72 hours is mandatory and the fine considers whether the weakness was known.
Applies: Any site processing personal data of people in the EU or UK. Enforced by regulators.
CCPA / CPRA (California) · United States, California1 finding
Maximum. About $2,500 per violation and about $7,500 per intentional violation or one involving a minor, inflation-adjusted each year; each affected consumer can count as a violation.
Usually. A notice from the California Privacy Protection Agency or Attorney General; the 30-day cure period was removed in 2023. Enforcement has focused on larger companies, but the thresholds catch many startups once they pass roughly $26 million in revenue or 100,000 consumers.
Applies: Businesses over the CCPA thresholds with California users. Many early-stage sites are below them; the privacy-policy duty under CalOPPA applies to all. Enforced by regulators.
CalOPPA (California Online Privacy Protection Act) · United States, California1 finding
Maximum. Up to $2,500 per violation, enforced through California's unfair-competition law after a 30-day notice.
Usually. A notice to post a compliant policy within 30 days. Applies to any commercial site reaching Californians, with no size threshold.
Applies: Any commercial site or app collecting personal information from California residents. Enforced by regulators.
PIPEDA / Quebec Law 25 · Canada1 finding
Maximum. Quebec Law 25: administrative penalties up to CA$10 million or 2% of worldwide turnover, and penal fines up to CA$25 million or 4%. PIPEDA itself currently relies on findings and court orders.
Usually. A complaint to the Privacy Commissioner or Quebec's CAI, an investigation, and a public finding; Quebec has begun issuing monetary penalties.
Applies: Any organisation collecting personal information from people in Canada; Law 25 for Quebec residents. Enforced by regulators.
ADA Title III and California's Unruh Act (web accessibility) · United States1 finding
Maximum. The ADA carries no fixed fine for private suits, but the defendant typically pays the plaintiff's attorney fees; California's Unruh Act adds statutory damages of $4,000 per violation. DOJ actions can carry civil penalties up to $75,000 for a first violation.
Usually. Thousands of private lawsuits a year, most against small and mid-sized sites, usually settled for roughly $5,000 to $25,000 plus fees. Fixing the automated violations is the cheapest defence.
Applies: Any business website in the US; California residents can sue under Unruh. Enforced by regulators and private plaintiffs.
European Accessibility Act / UK Equality Act / AODA · EU, UK, Ontario1 finding
Maximum. Set by each EU member state since June 2025; AODA penalties up to CA$100,000 per day for corporations; UK Equality Act claims are private.
Usually. Complaints and compliance orders first; fines are reserved for refusal to fix.
Applies: Consumer-facing digital services in the EU; Ontario organisations; UK service providers. Enforced by regulators and private plaintiffs.
FTC Act §5 (unfair or deceptive practices) and state breach laws · United States1 finding
Maximum. No fixed fine for a first violation; the FTC obtains consent orders with 20-year audit obligations, and violating an order costs over $53,000 per day. State breach-notification laws add per-resident notification costs and, in some states, per-record penalties.
Usually. Enforcement follows an incident. An exposed live key or open database is the incident waiting to happen; the practical cost is fraud on the account plus mandatory notification.
Applies: Any US company holding consumer data. Enforced by regulators.
AI design tells
30 patterns on this page read as AI-generated: Nested cards, Overused font, AI color palette. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.
Nested cards27×
Cards inside cards create visual noise and excessive depth. Flatten the hierarchy — use spacing, typography, and dividers instead of nesting containers.
Example: Card inside card
Overused font1×
Inter, Roboto, Fraunces, Geist, Plus Jakarta Sans, and Space Grotesk are used on so many sites they no longer feel distinctive. Each new wave of AI-generated UIs converges on the same handful of faces. Choose a face that gives your interface personality.
Example: Primary font: arial (45% of text)
AI color palette1×
Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.
Example: Purple/violet accent colors detected
Auto-scrolling marquee1×
Continuously auto-scrolling content demands attention it has not earned and hides half its content at any moment. Reserve motion for content that changes; let readers move at their own pace.
Example: .lv-marquee-track — infinite horizontal loop animation "lv-marquee"
Undersized functional text · quality37×
Interactive and content-bearing UI text (links, buttons, nav items, labels, table cells, meta rows, timecodes) below 11px is a legibility failure, not a style choice. WCAG sets no absolute pixel floor, but functional text under 11px is a defensible quality bar: it fails on high-DPI and small viewports and it degrades tap and read targets. The 11px floor holds even inside a footer; only non-interactive legal smallprint gets the softer 10px floor. Being ON the DESIGN.md size ramp does not exempt a value here: adding 8px to the ramp launders the token but not the legibility problem, and that is exactly the escape hatch this rule closes. Exempts sup/sub, visually-hidden (sr-only) text, and code/terminal contexts. Decorative letterspaced micro-labels are still functional and stay in scope.
Example: 10px functional text "North & Co." (below 11px floor)
Cramped padding · quality13×
Text is too close to the edge of its container. Two shapes: (1) an element with its own text where the padding is too low for the font size, and (2) a wrapper with text-bearing children and near-zero padding against a visible boundary (border, outline, or non-transparent background) — children land flush against the boundary line. Add at least 8px (ideally 12–16px) of padding inside bordered, outlined, or colored containers.
Example: 0px vertical padding (need ≥4.2px for 14px text)
Line length too long · quality9×
Text lines wider than ~80 characters are hard to read. The eye loses its place tracking back to the start of the next line. Add a max-width (65ch to 75ch) to text containers.
Example: ~85 chars/line (aim for <80)
Raster buried under a wash or opacity · quality7×
A background image under a near-opaque gradient wash, or a raster on an element at near-zero opacity, never reaches the screen: the page shows the wash, and the produced texture or photo ships as a compliance token. Let the material show (a tint under 0.9 alpha, a blend mode, an opacity you can see) or remove the file.
Example: <img> at opacity 0
Tiny body text · quality1×
Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.
Example: 11px body text
Layout property animation · quality1×
Animating width, height, padding, or margin causes layout thrash and janky performance. Use transform and opacity instead, or grid-template-rows for height animations.
Example: transition: height
Full annotated page (98 labels)

This report is complete and free, and true as of the scan time above. The next deploy, a tag added in Tag Manager or a redesigned footer can change it. Watch re-checks esigna.app every day and after every deploy, emails you the moment something regresses, keeps the dated record, and gives you a trust page your customers can check.
Watch esigna.appTrust page draftPassed audits
(10)
Privacy policy is present
A privacy policy link or page was found.
No third-party trackers detected
None of the common analytics or marketing pixels were found in the page.
Terms of service are present
A terms page or link was found.
Public contact or business identity present
A contact email, contact page, or mailto link was found.
No secret keys in the page or its scripts
No server-side keys (Stripe secret, OpenAI, Anthropic, AWS, GitHub, Slack, SendGrid, Supabase service_role, private keys) in the page or the 6 script bundles it loads.
1 security header set
Strict-Transport-Security
No mixed content
All referenced resources use HTTPS.
Legal entity and address are shown
A company name and a postal address appear on the page.
Served over HTTPS
The final URL uses TLS.
37 accessibility rules passed
Rules axe-core tested and found no violations for.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
esigna.app holds Clean Bill of Health WO-2026-0277, last checked November 22, 2026. Open it for the seal and what it verified.
Put your score on your README.
An embeddable badge that re-checks weekly. Builders use it the way they use a CI badge: proof the boring stuff is handled.
[](https://webopsy.tech/s/esigna.app)