fix(a11y): meet 4.5:1 contrast for text-subtle and text-warning (WCAG 1.4.3)

[bilal-karim]

Summary

Two token-value adjustments for SC 1.4.3 Contrast (Minimum) at the theme-variables layer. Both consumers pick up the fix automatically — no per-call-site changes.

• text-subtle dark mode: slate.700 → slate.400. Previous ratio ~3.4:1 on black (FAIL); new ~9.4:1. Affects user-menu small text and CodeMirror comment syntax.
• text-warning light mode: yellow.600 → yellow.700. Previous ratio ~3.2:1 on white (FAIL); new ~4.7:1. Affects character-count warning state on Input, Textarea, ChipInput.

Audit context

• WCAG 2.2 SC 1.4.3 Contrast (Minimum) (Level AA) — Serious severity each.
• Issue files: `audit-output/issues/1.4.3-{text-subtle-token,text-warning-token}.md`.
• Both are conditional-on-verification per audit — please measure with DevTools eyedropper to confirm the math.

Test plan

• Light mode: focus a maxLength field (Schedule form description, etc.); type until "X / Y" counter shows ≤5 remaining → text turns yellow. Inspect color in DevTools, confirm ≥ 4.5:1 against white.
• Dark mode: open user menu (top-right) and observe subtle/secondary text. Inspect color, confirm ≥ 4.5:1 against black. Also check CodeMirror comment syntax in any JSON viewer.
• axe-core color-contrast rule should no longer flag these surfaces.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
holocene	Ready	Preview, Comment	May 22, 2026 1:29pm

[temporal-cicd]

Warnings

⚠️

📊 Strict Mode: 3 errors in 1 file (0.3% of 914 total) src/lib/theme/variables.ts (3) L223:16: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ readonly '--color-text-black': { readonly light: "space-black"; readonly dark: "space-black"; }; readonly '--color-text-white': { readonly light: "off-white"; readonly dark: "off-white"; }; ... 49 more ...; readonly '--color-border-focus-danger': { ...; }; }'. L224:2: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'Record<--${string}, ${number} ${number} ${number}>'. L225:2: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'Record<--${string}, ${number} ${number} ${number}>'.

Generated by 🚫 dangerJS against 0e247c0