This report was prepared for mesmer.co. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Score up 6 since Nov 15, 2026 (86 → 92). Fixed: Missing 3 security headers. New: Elements must meet minimum color contrast ratio thresholds.
Clean bill of health since Oct 2, 2026, serial WO-2026-0231. 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 elements)~2 h
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <div class="pscan-head" style="left:0;width:64px;color:rgba(11,10,9,0.38);font-weight:400">plan</div>
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.
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 May 21, 2025.
GDPR Art. 13(2)(d)
<!-- Sections your privacy policy at https://mesmer.co/privacy-policy 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 mesmer.co 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; 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.
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.
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
23 patterns on this page read as AI-generated: Hairline border with wide shadow, Glowing shadow accents, 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 shadow5×
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 + 60px shadow blur
Glowing shadow accents4×
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 (#2b3a67)
Nested cards4×
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
Shape-assembled illustration4×
A large inline SVG that builds a pictorial scene from a pile of primitive shapes reads as placeholder clip art, not illustration. Icons, logos, and data graphics are fine at their scale; a hero-sized visual deserves real artwork, a photograph, or a deliberately drawn graphic.
Example: inline <svg> scene: 19 primitive shapes, ~340x290px, 3 fill colors
Bounce or elastic easing3×
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)
Side-tab accent border1×
Thick colored border on one side of a card — the most recognizable tell of AI-generated UIs. Use a subtler accent or remove it entirely.
Example: border-left: 2px + border-radius: 8px
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: geist mono (55% of text)
Pulsing status dot1×
Small pulsing status dots simulate liveness decoratively. Reserve pulse animation for indicators tied to genuinely live, changing data; a static indicator with clear labeling is honest and calmer.
Example: .sh-typing span — 5x5px dot with infinite "shipTypeBob" animation
Raster buried under a wash or opacity · quality40×
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.14
Undersized functional text · quality11×
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 "01" (below 11px floor)
Wide letter spacing on body text · quality5×
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
Layout property animation · quality4×
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: margin-top
Low contrast text · quality2×
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: 2.7:1 (need 4.5:1) — text #a29b92 on #ffffff
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 60 chars of body text
Full annotated page (86 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 mesmer.co 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 mesmer.coTrust 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.
28 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.
mesmer.co holds Clean Bill of Health WO-2026-0231, 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/mesmer.co)