This report was prepared for dokbot.app. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
No change since the scan on Nov 15, 2026.
Clean bill of health since Oct 3, 2026, serial WO-2026-0529. 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 (5 elements)~40 min
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <div class="flex-1 bg-neutral-100 rounded-lg px-3 py-2 text-xs text-neutral-400">Type your question...</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.
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.
// next.config.js — Missing on your site: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. The Content-Security-Policy below already allows Google Analytics; 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' https://www.googletagmanager.com https://www.google-analytics.com 'unsafe-inline'; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com; img-src 'self' data: https: https://www.google-analytics.com; 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 }];
},
};No cookie policy or preferences link~20 min
Trackers are in use but there is no cookie policy or a way to change cookie choices. EU and UK regulators expect both.
ePrivacy Directive Art. 5(3); PECR reg. 6; ICO and CNIL guidance.
No "Do Not Sell or Share My Personal Information" link~15 min
Advertising or analytics trackers (Google Tag Manager) can count as "sharing" under California law. Businesses over the CCPA thresholds must offer an opt-out link on the homepage. Also expected under several other US state laws.
CCPA/CPRA §1798.120 and §1798.135; Colorado, Connecticut, Virginia, Texas, Oregon privacy acts (opt-out of targeted advertising).
No legal entity name or address~5 min
Sites that take money or serve EU/German users are expected to show who runs them and where. It also unblocks Stripe and app-store reviews.
GDPR Art. 13(1)(a) (controller identity); German TMG §5 Impressum; EU e-Commerce Directive Art. 5; consumer-protection rules in most countries.
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.
ePrivacy Directive (EU) / PECR (UK), cookies and marketing · EU, UK1 finding
Maximum. Set nationally in the EU; the UK ICO can fine up to £500,000 under PECR.
Usually. Regulators run periodic sweeps of cookie banners; a warning letter is the common first step, with fines reserved for repeat or large-scale cases.
Applies: Sites setting non-essential cookies or sending marketing email to 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.
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
6 patterns on this page read as AI-generated: Nested cards, Hairline border with wide shadow, Overused font. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

Nested cards3×
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
Hairline border with wide shadow2×
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 + 50px shadow blur
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 (79% of text)
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 53 chars of body text
Low contrast text · quality1×
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.4:1 (need 4.5:1) — text #a1a1a1 on #f5f5f5
Tiny body text · quality1×
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
Full annotated page (9 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 dokbot.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 dokbot.appTrust page draftPassed audits
(11)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy is written in another language
1379 words at https://www.dokbot.app/privacy. The disclosure checks only read English, so its completeness was not assessed.
Google Consent Mode defaults to denied
Trackers detected (Google Tag Manager) and consent is handled by Google Consent Mode with storage denied until the visitor agrees. Confirm non-Google trackers also wait for consent.
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.
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.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
dokbot.app holds Clean Bill of Health WO-2026-0529, 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/dokbot.app)