Webopsy

This report was prepared for ai-watch-tester.vercel.app. It shows the top findings; the full report includes every issue and its fix.

84ai-watch-tester.vercel.app
94Privacy
92Security
98Legal
70Accessibility
33Design
What the scores mean
Scanned Nov 22, 2026, 9:21 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 2, 2026, serial WO-2026-0354. 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 (52 elements)~4 h

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <div class="mb-4 inline-flex items-center gap-2 rounded-full border border-gray-200 bg-gray-100 px-3 py-1 text-xs text-gray-500 backdrop-blur"><span class="h-1.

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

Diagnostics

Worth fixing. Not an emergency.

Privacy policy is missing 3 expected disclosures~45 min

Not found in the policy text: states a legal basis (eea/uk users); states whether data is sold or shared for advertising; mentions the right to complain to a regulator. Last updated February 24, 2026.

GDPR Art. 13(1)(c)-(d) · CCPA/CPRA §1798.120, §1798.135 · GDPR Art. 13(2)(d)

Open reference

Privacy Policy: missing sections privacy-policy-addendum.md
<!-- Sections your privacy policy at https://ai-watch-tester.vercel.app/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. -->

## Legal bases (EEA/UK users)

Where the GDPR/UK GDPR applies, we rely on: performance of a contract with you
(providing the Service), your consent (marketing email; you may withdraw it at any time), our legitimate interests in
operating and securing the Service, and compliance with legal obligations.

## Sale of personal information

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

## 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 ai-watch-tester.vercel.app on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 3 sections to your existing policy (https://ai-watch-tester.vercel.app/privacy), then re-scan; the audit checks for each one by name.
Missing 3 security headers~15 min

Not set: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers next.config.js
// next.config.js — Missing on your site: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. The Content-Security-Policy below already allows only your own origin; add the domain of anything else you load to script-src or connect-src, then re-scan.
/** @type {import('next').NextConfig} */
const securityHeaders = [
  { key: 'Strict-Transport-Security', value: "max-age=63072000; includeSubDomains; preload" },
  { key: 'X-Content-Type-Options', value: "nosniff" },
  { key: 'X-Frame-Options', value: "SAMEORIGIN" },
  { key: 'Referrer-Policy', value: "strict-origin-when-cross-origin" },
  { key: 'Permissions-Policy', value: "camera=(), microphone=(), geolocation=()" },
  { key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" },
];

module.exports = {
  async headers() {
    return [{ source: '/:path*', headers: securityHeaders }];
  },
};
Next.js config (works on Vercel, Netlify, or a Node server). Then re-scan. The Content-Security-Policy is written for what the scan saw (no third parties); if a script or request is blocked after deploy, the browser console names the origin to add.
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 security items sit under GDPR Art. 32 (up to 2% of turnover) and the FTC's security enforcement, where the real cost arrives with a breach and its mandatory notifications; 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.

GDPR / UK GDPR, security of processing · EU, EEA, UK1 finding

Maximum. Up to €10 million or 2% of worldwide annual turnover (Art. 83(4)); UK: up to £8.7 million or 2%.

Usually. Fines follow a breach, not a scan. If exposed data reaches users, breach notification to the regulator within 72 hours is mandatory and the fine considers whether the weakness was known.

Applies: Any site processing personal data of people in the EU or UK. 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.

FTC Act §5 (unfair or deceptive practices) and state breach laws · United States1 finding

Maximum. No fixed fine for a first violation; the FTC obtains consent orders with 20-year audit obligations, and violating an order costs over $53,000 per day. State breach-notification laws add per-resident notification costs and, in some states, per-record penalties.

Usually. Enforcement follows an incident. An exposed live key or open database is the incident waiting to happen; the practical cost is fraud on the account plus mandatory notification.

Applies: Any US company holding consumer data. Enforced by regulators.

AI design tells

15 patterns on this page read as AI-generated: Kicker Above Heading, Nested Cards, Thin Border Wide Shadow. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of ai-watch-tester.vercel.app with the most AI design tells, with each one labeled
The spot with the most tells: Nested Cards. Labels are drawn by the detector on the live page.
Kicker Above Heading8×

Example: kicker "Core Architecture" above h2 "The Self-Healing DevQA Loop"

Nested Cards3×

Example: Card inside card

Thin Border Wide Shadow2×

Example: 1px border + 50px shadow blur

Overused Font1×

Example: Primary font: geist (64% of text)

Pulsing Dot1×

Example: animate-pulse on tiny rounded-full element

Low Contrast · quality17×

Example: 4.4:1 (need 4.5:1) — text #6a7282 on #f3f4f6

Tiny Text · quality2×

Example: 11px body text

Line Length · quality1×

Example: ~128 chars/line (aim for <80)

Em Dash Overuse · quality1×

Example: 21 em-dashes in body text

Full annotated page (36 labels)
Full page of ai-watch-tester.vercel.app 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 ai-watch-tester.vercel.app 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 ai-watch-tester.vercel.appTrust page draft

Passed audits

(9)
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.

1 security header set

Strict-Transport-Security

No mixed content

All referenced resources use HTTPS.

Served over HTTPS

The final URL uses TLS.

23 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 4 URLs from sitemap.xml.
Also read/pricing /login /signup, for the third-party services on them.
StackNext.js on Vercel, from response headers and the page. The header fix is written for it.
Accessibilityaxe-core (WCAG 2.2 A/AA). 1 violation types, 23 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 36 findings in 30.5 s at 1280px.
Duration33.7 s

Or a free weekly re-scan of ai-watch-tester.vercel.app. 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.

ai-watch-tester.vercel.app holds Clean Bill of Health WO-2026-0354, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for ai-watch-tester.vercel.app

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/ai-watch-tester.vercel.app)](https://webopsy.tech/s/ai-watch-tester.vercel.app)

Webopsy badge for ai-watch-tester.vercel.app