Webopsy

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

98motionspec.dev
100Privacy
100Security
98Legal
100Accessibility
25Design
What the scores mean
Scanned Nov 22, 2026, 11:05 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 7, 2026, serial WO-2026-1109. View the certificate

Opportunities

No critical or high-severity issues. That's the bar most sites miss.

Nothing here.

Diagnostics

Worth fixing. Not an emergency.

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.

AI design tells

93 patterns on this page read as AI-generated: AI color palette, Hairline border with wide shadow, Kicker / eyebrow label above heading. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of motionspec.dev with the most AI design tells, with each one labeled
The spot with the most tells: AI color palette, Hairline border with wide shadow. Labels are drawn by the detector on the live page.
AI color palette58×

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

Hairline border with wide shadow20×

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 + 22px shadow blur

Kicker / eyebrow label above heading12×

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 "Motion control for web agencies" above h1 "Every loop needsa pausebutton."

Crushed letter spacing2×

Letter-spacing pulled tighter than the point where characters keep their own shapes costs legibility. Tighten display type optically, not destructively.

Example: letter-spacing: -0.06em — "Every loop needsa pausebutton."

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: inter (96% of text)

Line length too long · quality14×

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

Undersized functional text · quality5×

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: 10.4px functional text "The choice is yours" (below 11px floor)

All-caps body text · quality4×

Long passages in uppercase are hard to read. We recognize words by shape (ascenders and descenders), which all-caps removes. Reserve uppercase for short labels and headings.

Example: text-transform: uppercase on 31 chars of body text

Tiny body text · quality3×

Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.

Example: 10px body text

Cramped padding · quality1×

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: <div> "ms-loop-window": children flush against bg on left (no inset)

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 11 vertices approximating an organic contour

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: section.ms-hero opens the page with one column running 290% of the viewport tall while a sibling fits in 87% — the fold falls deep inside the section

Full annotated page (122 labels)
Full page of motionspec.dev 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 motionspec.dev 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 motionspec.devTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

3200 words; 14 disclosure checks passed; last updated 2026-11-02.

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.

security.txt published

Researchers know where to report a vulnerability.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (36 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.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 59 URLs from sitemap.xml.
Also read/pricing, 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). 0 violation types, 36 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 122 findings in 9.8 s at 1280px.
Duration10.6 s

Or a free weekly re-scan of motionspec.dev. 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.

motionspec.dev holds Clean Bill of Health WO-2026-1109, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for motionspec.dev

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/motionspec.dev)](https://webopsy.tech/s/motionspec.dev)

Webopsy badge for motionspec.dev