This report was prepared for muapi.ai. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Score 90 since Nov 15, 2026 (90 → 90). New: All touch targets must be 24px large, or leave sufficient space.
Clean bill of health since Oct 2, 2026, serial WO-2026-0198. 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 only use permitted ARIA attributes~20 min
Ensure ARIA attributes are not prohibited for an element's role Example: <div class="flex gap-0.5 mt-1" aria-label="5 out of 5 stars">
WCAG wcag2a, wcag412. 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).
Elements must meet minimum color contrast ratio thresholds~20 min
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <a class="inline-flex items-center gap-2 text-xs font-semibold text-green-600 dark:text-green-400" href="/status"><span class="w-2 h-2 rounded-full bg-green-500
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).
Scrollable region must have keyboard access (3 elements)~20 min
Ensure elements that have scrollable content are accessible by keyboard in Safari Example: <pre class="select-text overflow-x-auto scrollbar-thin scrollbar-thumb-neutral-800 scrollbar-track-transparent">
WCAG wcag2a, wcag211, wcag213. 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).
All touch targets must be 24px large, or leave sufficient space (8 elements)~40 min
Ensure touch targets have sufficient size and space Example: <button class="h-2 rounded-full transition-all duration-300 w-2 bg-white/20 hover:bg-white/40" aria-label="Go to slide 2"></button>
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).
Diagnostics
Worth fixing. Not an emergency.
Missing 4 security headers~15 min
Not set: Content-Security-Policy, Strict-Transport-Security, 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, Strict-Transport-Security, 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 }];
},
};No postal address for the business~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.
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, 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.
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.
ADA Title III and California's Unruh Act (web accessibility) · United States4 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, Ontario4 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.
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
94 patterns on this page read as AI-generated: Nested Cards, AI color palette, Thin Border Wide Shadow. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

Nested Cards39×
Example: Card inside card
AI color palette29×
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 (Tailwind)
Thin Border Wide Shadow15×
Example: 1px border + 50px shadow blur
Gradient text4×
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
Pulsing status dot4×
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: animate-ping on tiny rounded-full element
Side Tab1×
Example: border-left: 4px
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: inter (85% of text)
Kicker / eyebrow label above heading1×
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 "TOP MODEL ECOSYSTEMS, ONE API" above h2 "Production model providers on MuAPI"
Undersized functional text · quality87×
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 "Menu" (below 11px floor)
Line Length · quality13×
Example: ~90 chars/line (aim for <80)
Low Contrast · quality2×
Example: 3.7:1 (need 4.5:1) — text #ffffff on #3b82f6
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
Tiny Text · quality1×
Example: 10px body text
Full annotated page (198 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 muapi.ai 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 muapi.aiTrust page draftPassed audits
(9)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy is written in another language
2229 words at https://muapi.ai/api/app/pdf/privacy_policy.pdf. The disclosure checks only read English, so its completeness was not assessed.
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.
No mixed content
All referenced resources use HTTPS.
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.
muapi.ai holds Clean Bill of Health WO-2026-0198, 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/muapi.ai)