fix(web): banner contrast meets WCAG AA
All checks were successful
Deploy to Production / deploy (push) Successful in 53s

White on #6366f1 was 4.47:1 — just under the 4.5:1 minimum for small
text (Lighthouse a11y flag). Darkened the banner to #4f46e5 (6.3:1).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Marco Sadjadi 2026-05-21 19:31:34 +02:00
parent b843394d0f
commit 36a1adf4d7

View File

@ -1,14 +1,15 @@
// Temporary pre-launch notice. Remove this component and its import in // Temporary pre-launch notice. Remove this component and its import in
// app/layout.tsx once the service is open for production use. // app/layout.tsx once the service is open for production use.
// Background is set inline so it renders regardless of Tailwind theme wiring. // Background is #4f46e5 (not the #6366f1 accent) so white text clears the
// WCAG AA 4.5:1 contrast ratio for this small text — #6366f1 fell just short.
export function SiteBanner() { export function SiteBanner() {
return ( return (
<div <div
style={{ backgroundColor: '#6366f1' }} style={{ backgroundColor: '#4f46e5' }}
className="border-b border-[#4f46e5] px-4 py-2 text-center text-[12.5px] font-medium leading-snug text-white" className="border-b border-[#4338ca] px-4 py-2 text-center text-[12.5px] font-medium leading-snug text-white"
> >
<span className="font-semibold uppercase tracking-wide">Preview</span> <span className="font-semibold uppercase tracking-wide">Preview</span>
<span className="px-1.5 opacity-70">·</span> <span className="px-1.5">·</span>
BuildMyMCPServer is not yet open for production use sign-ups, server generation and billing BuildMyMCPServer is not yet open for production use sign-ups, server generation and billing
are still being finalised, and data may be reset. are still being finalised, and data may be reset.
</div> </div>