Webopsy

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

92mosadd.com
94Privacy
100Security
98Legal
60Accessibility
69Design
What the scores mean
Scanned Nov 22, 2026, 5:52 AM

Score 92 since Nov 14, 2026 (92 → 92). New: Elements must meet minimum color contrast ratio thresholds; All touch targets must be 24px large, or leave sufficient space.

Clean bill of health since Nov 14, 2026, serial WO-2026-4814. 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 (2 elements)~20 min

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <span class="s-00__lab" data-t="lp.ops.hero.live.humans">humans</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 (19 elements)~2 h

Ensure touch targets have sufficient size and space Example: <a href="/mdm">mDM</a>

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.

Privacy policy is missing 1 expected disclosure~15 min

Not found in the policy text: carries a last-updated or effective date. Last updated 16 November 2026.

CCPA §1798.130(a)(5) (annual update); good practice everywhere

Open reference

Privacy Policy: missing sections privacy-policy-addendum.md
<!-- Sections your privacy policy at https://mosadd.com/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. -->

_Last updated: November 22, 2026_

---
_Generated from what the scanner observed on mosadd.com on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 1 section to your existing policy (https://mosadd.com/privacy-policy), then re-scan; the audit checks for each one by name.

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

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 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.

AI design tells

2 patterns on this page read as AI-generated: AI color palette, Pulsing status dot. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

AI color palette1×

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

Example: Cyan neon text on dark background

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: .lp-menu:not(.is-ready)::after — 8x8px dot with infinite "lp-menu-wait" animation

Undersized functional text · quality8×

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: 8.47px functional text "· c/o FONGIT, Route de la Galaise 34, 12" (below 10px floor)

Layout property animation · quality2×

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

Tiny body text · quality2×

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

Wide letter spacing on body text · quality2×

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.08em on body text

Line length too long · quality1×

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

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

Passed 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.

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.

24 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 129 URLs from sitemap.xml.
Also read/pricing /contact, for the third-party services on them.
StackCaddy, from response headers and the page. The header fix is written for it.
Accessibilityaxe-core (WCAG 2.2 A/AA). 2 violation types, 24 rules passed, 3 need manual review.
Design auditImpeccable browser detector. 17 findings in 6.2 s at 1280px.
Duration9.6 s

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

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

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

Webopsy badge for mosadd.com