Webopsy

This report was prepared for kishinotch.com. It shows the top findings; the full report includes every issue and its fix.

90kishinotch.com
100Privacy
92Security
98Legal
80Accessibility
41Design
What the scores mean
Scanned Nov 22, 2026, 9:48 AM

Score 90 since Nov 15, 2026 (90 → 90). New: Elements must meet minimum color contrast ratio thresholds.

Clean bill of health since Oct 6, 2026, serial WO-2026-0990. 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="t12" style="color: var(--indigo);">On</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).

How to fix this rule

All touch targets must be 24px large, or leave sufficient space (2 elements)~20 min

Ensure touch targets have sufficient size and space Example: <div class="gs" role="slider" tabindex="0" aria-label="Progress" aria-valuemin="0" aria-valuemax="100" data-noclick="" aria-valuenow="35" style="--gs-fill: #f23

WCAG wcag22aa, wcag258. 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).

How to fix this rule

Diagnostics

Worth fixing. Not an emergency.

Missing 1 security header~15 min

Not set: Strict-Transport-Security. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers _headers
# Missing on your site: Strict-Transport-Security. The Content-Security-Policy below already allows only your own origin; add the domain of anything else you load to script-src or connect-src, then re-scan.
/*
  Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
  X-Content-Type-Options: nosniff
  X-Frame-Options: SAMEORIGIN
  Referrer-Policy: strict-origin-when-cross-origin
  Permissions-Policy: camera=(), microphone=(), geolocation=()
  Content-Security-Policy: default-src 'self'; script-src 'self'; connect-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'
Cloudflare Pages output directory. On Cloudflare in front of another origin, use a Transform Rule (Rules → Transform Rules → Modify Response Header) with the same values. Then re-scan. The Content-Security-Policy is written for what the scan saw (no third parties); if a script or request is blocked after deploy, the browser console names the origin to add.
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.

ADA Title III and California's Unruh Act (web accessibility) · United States2 findings

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, Ontario2 findings

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

33 patterns on this page read as AI-generated: AI color palette, Decorative radial spotlight glow, Radial-gradient background halo. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of kishinotch.com with the most AI design tells, with each one labeled
The spot with the most tells: AI color palette, Decorative radial spotlight glow, Positioned child clipped by overflow container. Labels are drawn by the detector on the live page.
AI color palette19×

Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.

Example: Cyan gradient background

Decorative radial spotlight glow12×

A soft, low-opacity accent-colored radial gradient fading to transparent, dropped behind a hero or section as a "spotlight." It is a reflex AI decoration — the translucent cousin of the saturated radial halo. Let the surface stand on its own, or light the composition with a deliberate material accent rather than a floating colored haze.

Example: radial-gradient spotlight glow "hero__glow" (#35d88a a0.16 → transparent) on 1805x1108 surface

Radial-gradient background halo1×

A chromatic radial-gradient wash — saturated at the center, fading to transparent — used as a decorative background glow on a dark page. Same tell as glowing shadows, drawn with a gradient instead of a shadow. Ground the surface with a solid or subtly shifted background instead.

Example: radial-gradient halo (#ffc8de → transparent) on dark page

Repeating-gradient stripes1×

Repeating-gradient stripes used as surface decoration are a recurring generated-UI signature. Reach for a deliberate texture or leave the surface plain.

Example: repeating-gradient decorative stripes

Line length too long · quality23×

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: ~101 chars/line (aim for <80)

Positioned child clipped by overflow container · quality14×

A clipping container (overflow hidden or clip) wrapping an absolutely-positioned child cuts off tooltips, menus, and popovers that need to escape. Let the overflow be visible, or move the positioned layer out of the clip.

Example: div.stage.stage--mini clips a positioned child

Undersized functional text · quality10×

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 "1:18" (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.2px for 14px text)

Full annotated page (83 labels)
Full page of kishinotch.com with every design tell labeled

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 kishinotch.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 kishinotch.comTrust page draft

Passed audits

(10)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

3997 words; 14 disclosure checks passed; last updated 2 November 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.

3 security headers set

Content-Security-Policy, X-Content-Type-Options, X-Frame-Options

No mixed content

All referenced resources use HTTPS.

Served over HTTPS

The final URL uses TLS.

33 accessibility rules passed

Rules axe-core tested and found no violations for.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 22 URLs from sitemap.xml.
Also read/contact, for the third-party services on them.
StackCloudflare, from response headers and the page. The header fix is written for it.
Accessibilityaxe-core (WCAG 2.2 A/AA). 2 violation types, 33 rules passed, 2 need manual review.
Design auditImpeccable browser detector. 83 findings in 14.3 s at 1280px.
Duration15.9 s

Or a free weekly re-scan of kishinotch.com. An email only when a new issue appears.

Only change alerts, unsubscribe in any email. Privacy.

Share this report.

The link is public and shows the same free view you see here; nothing about the reader is recorded.

Post on XShare on LinkedIn

The certificate.

kishinotch.com holds Clean Bill of Health WO-2026-0990, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for kishinotch.com

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.

Markdown
[![Webopsy](https://webopsy.tech/badge/kishinotch.com)](https://webopsy.tech/s/kishinotch.com)

Webopsy badge for kishinotch.com