No "Coming Soon" buttons without backing implementation
Why it matters
A <button disabled>Coming Soon</button> announces unfinished work on every page view. Prospects see the placeholder before they see the working feature set, pricing tables look padded with vaporware, and competitors screenshot the dead CTA for comparison pages. The pattern also breaks keyboard and screen-reader flows because the button focuses but does nothing, which maps to WCAG 2.2 SC 2.4.3 (Focus Order) and SC 3.2.2 (On Input) complaints.
Severity rationale
Info because the defect is cosmetic and accessibility-adjacent rather than data- or security-impacting.
Remediation
Either hide the feature behind a flag until implementation lands, or wire the CTA to a real waitlist action that captures email and sets expectations. Never ship a disabled button with placeholder text. Fix at src/components/Pricing.tsx:
{FEATURE_ENABLED ? (
<button onClick={handleClick}>Sign up</button>
) : (
<button onClick={() => addToWaitlist(email)}>Join waitlist</button>
)}
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the WIP-in-Production Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 2.4.3 — Focus Order
Taxons
History
- 2026-04-18·v1.0.0·Initial import from ai-slop-half-finished·automated