This report was prepared for kitsuvo.com. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
No change since the scan on Nov 14, 2026.
Clean bill of health since Oct 9, 2026, serial WO-2026-1310. 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="lp-key lp-key-ai lp-end"><span class="lp-sr">Score </span>78</span>
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.
What these findings expose you to
For scale: 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.
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.
AI design tells
3 patterns on this page read as AI-generated: Hairline border with wide shadow, Nested cards. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

Hairline border with wide shadow2×
A hairline border paired with a wide, diffuse shadow is a recurring generated-UI signature. Commit to one — a defined edge or a soft elevation — rather than both at once.
Example: 1px border + 90px shadow blur
Nested cards1×
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
Line length too long · quality17×
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: ~108 chars/line (aim for <80)
Undersized functional text · quality4×
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 "Browser" (below 11px floor)
Cramped padding · quality3×
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.0px for 12px text)
Tiny body text · quality2×
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
Tight line height · quality2×
Line height below 1.3x the font size makes multi-line text hard to read. Use 1.5 to 1.7 for body text so lines have room to breathe.
Example: line-height 1.25x (need >=1.3)
Cream Palette · quality1×
Example: cream/beige page background rgb(255, 253, 248)
Organic contour drawn as clip-path · quality1×
A clip-path polygon with many arbitrary vertices, or a curved clip-path path(), is CSS approximating a torn edge, blob, or silhouette. It reads as the cheap version of the effect and is usually a produced or photographic material replaced with code. Derive an alpha matte from the real image, or ship the shape as a cut-out raster; keep clip-path for geometry (cut corners, diagonals, hexagons).
Example: clip-path: polygon() with 12 vertices approximating an organic contour
Full annotated page (33 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 kitsuvo.com 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 kitsuvo.comTrust page draftPassed audits
(12)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy covers the expected disclosures
5647 words; 14 disclosure checks passed; last updated November 20, 2026.
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.
4 security headers set
Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options
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.
security.txt published
Researchers know where to report a vulnerability.
Served over HTTPS
The final URL uses TLS.
33 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.
kitsuvo.com holds Clean Bill of Health WO-2026-1310, 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/kitsuvo.com)