This report was prepared for velork.com. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Score 92 since Nov 15, 2026 (92 → 92). Fixed: Elements must meet minimum color contrast ratio thresholds.
Clean bill of health since Nov 8, 2026, serial WO-2026-4171. View the certificate
Opportunities
No critical or high-severity issues. That's the bar most sites miss.
Diagnostics
Worth fixing. Not an emergency.
Privacy policy is missing 1 expected disclosure~15 min
Not found in the policy text: mentions the right to complain to a regulator. Last updated November 22, 2026.
GDPR Art. 13(2)(d)
<!-- Sections your privacy policy at https://velork.com/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. -->
## 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 velork.com on November 22, 2026. Confirm each section matches what you actually do; not legal advice._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. 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.
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.
AI design tells
18 patterns on this page read as AI-generated: Kicker / eyebrow label above heading, Bounce or elastic easing, Nested cards. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

Kicker / eyebrow label above heading11×
A tiny tracked uppercase or small-caps label sitting as its own block directly above a heading is banned outright, repeated or not. Generated kickers never earn their place: the heading carries its own weight. Delete the label and let the heading speak; if the words matter, work them into the heading or the body.
Example: kicker "Your AI" above h2 "Bring the AI you already pay for"
Bounce or elastic easing2×
Bounce and elastic easing feel dated and tacky. Real objects decelerate smoothly — use exponential easing (ease-out-quart/quint/expo) instead.
Example: cubic-bezier(0.34, 1.56, 0.64, 1)
Nested cards2×
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
Hairline border with wide shadow1×
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 + 50px shadow blur
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
Decorative grid-line background1×
A decorative grid or line-field background drawn with hairline linear-gradient layers tiled by a fixed pixel cell is a recurring generated-UI signature. Reserve grid overlays for actual canvas, map, blueprint, or measurement surfaces; elsewhere use product structure or a plain surface.
Example: two-axis grid-line gradient background
Low contrast text · quality64×
Text does not meet WCAG AA contrast requirements (4.5:1 for body, 3:1 for large text). Increase the contrast between text and background.
Example: 3.5:1 (need 4.5:1) — text #8a8578 on #fbf9f4
Organic contour drawn as clip-path · quality26×
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 18 vertices approximating an organic contour
Raster buried under a wash or opacity · quality12×
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
Tight line height · quality7×
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.08x (need >=1.3)
Positioned child clipped by overflow container · quality5×
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.overflow-hidden.mx-auto clips a positioned child
Cramped padding · quality4×
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: <span> "agentsDemo_modeTabs__15jEK": children flush against bg on top/bottom (no inset)
Tiny body text · quality4×
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
Content overflowing its container · quality3×
Content renders wider than its container, spilling out or forcing a horizontal scrollbar. Let text wrap, constrain widths, or give the region a deliberate scroll affordance.
Example: span.agentsDemo_sessionTabLabel__YCy8L.agentsDemo_sessionTabLabelCut__dA6T7 overflows its box by 30px
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: width
One column stretches the first viewport · quality1×
A multi-column opening section lets one column run far past the fold while its sibling fits in a single viewport, so the short column floats in dead space and the fold falls deep inside one section. Balance the columns, cap the tall one, or let the long content flow below the opening row.
Example: div.agentsDemo_content__ddfcv opens the page with one column running 334% of the viewport tall while a sibling fits in 86% — the fold falls deep inside the section
Full annotated page (145 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 velork.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 velork.comTrust 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.
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.
Served over HTTPS
The final URL uses TLS.
No WCAG A/AA violations found (30 rules passed)
axe-core found no violations of the WCAG 2.2 A/AA rules it can test automatically. Automated checks cover roughly a third of WCAG; manual review is still needed for the rest.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
velork.com holds Clean Bill of Health WO-2026-4171, 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/velork.com)