Webopsy

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

98beginthings.com
100Privacy
100Security
98Legal
100Accessibility
0Design
What the scores mean
Scanned Nov 22, 2026, 10:40 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 9, 2026, serial WO-2026-1348. 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

70 patterns on this page read as AI-generated: Glowing shadow accents, Hairline border with wide shadow, Crushed letter spacing. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of beginthings.com with the most AI design tells, with each one labeled
The spot with the most tells: Gradient text, AI color palette. Labels are drawn by the detector on the live page.
Glowing shadow accents41×

Colored glow shadows — a zero-offset chromatic halo (box- or text-shadow) on any background, or any colored blurred shadow on a dark background — are the default "cool" look of AI-generated UIs. Use neutral elevation shadows and subtle, purposeful lighting instead.

Example: Zero-offset box-shadow glow (#9d8ee5)

Hairline border with wide shadow7×

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

Crushed letter spacing6×

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.05em — "Drop a file. Get it done."

AI color palette5×

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

Example: Purple/violet gradient background

Tiny numbered section labels3×

Small numeric index labels riding next to section headings, repeated section after section, are AI editorial scaffolding — a page numbering its own chapters instead of earning structure. Let hierarchy, content, and rhythm carry the sequence.

Example: tiny numbered label "02 / BEGINROOMS" beside h2 "Your work has depth. Give it space." (3 on page)

Gradient text2×

Gradient text is decorative rather than meaningful — a common AI tell, especially on headings and metrics. Use solid colors for text.

Example: background-clip: text + gradient

Kicker / eyebrow label above heading2×

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 "BEFORE YOU BEGIN" above h2 "A few good questions."

Decorative radial spotlight glow1×

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-scene" (#34419b a0.22 → transparent) on 593x570 surface

Icon tile stacked above heading1×

A small rounded-square icon container above a heading is the universal AI feature-card template — every generator outputs this exact shape. Try a side-by-side icon and heading, or let the icon sit in flow without its own container.

Example: 112x112px icon tile above h3 "Drop any file here"

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 (#182035 → 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

Undersized functional text · quality53×

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: 9px functional text "IDEAS" (below 11px floor)

Low contrast text · quality31×

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: 1.0:1 (need 4.5:1) — text #41484f on #41484f

Wide letter spacing on body text · quality22×

Letter spacing above 0.05em on body text disrupts natural character groupings and slows reading. Reserve wide tracking for short uppercase labels only.

Example: letter-spacing: 0.12em on body text

Tiny body text · quality15×

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

Cramped padding · quality12×

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 ≥10.0px for 33.2688px 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: ~98 chars/line (aim for <80)

Tight line height · quality1×

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.30x (need >=1.3)

All-caps body text · quality1×

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 37 chars of 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: padding

Full annotated page (215 labels)
Full page of beginthings.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 beginthings.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 beginthings.comTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

4087 words; 14 disclosure checks passed; last updated 31 May 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.

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.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 36 rules passed, 4 need manual review.
Design auditImpeccable browser detector. 215 findings in 9.3 s at 1280px.
Duration11.5 s

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

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

Seal for beginthings.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/beginthings.com)](https://webopsy.tech/s/beginthings.com)

Webopsy badge for beginthings.com