Shared 2.20.3: filled controls use --accent-strong / --on-accent-strong (WCAG AA contrast in every theme) (#47)

OP OpenVibers committed 10 Oct 2026 · tag v2.20. · 0 files, +0 −0

Filled controls now use the theme's readable token pair (`--accent-strong` with `--on-accent-strong`) instead of `--accent` with white text. White on the default accent `#3b82f6` is 3.68:1, under WCAG AA's 4.5:1 for normal-size text. The strong pair is 4.62:1 in the default theme, and every built-in theme defines it, using dark text on the light accents (forest, arctic, monokai…).

Changed: the primary button in `ui.js`, the toast's primary action, the account switcher's add button (its hover fallback was a stray `#a07840`), the footer's avatar initial (white on `#60a5fa` was about 2.5:1) and the navbar launcher's pressed segment.

The release UX check's axe run flagged this pairing as `color-contrast` (serious) on product sites. Those sites' own button rules are fixed in their repos; this is the shared half. `navbar.js` is 29.94 KB brotli, inside its 30 KB budget; the perf budget tests pass.

Version 2.20.3, CHANGELOG entry added.

This commit has no diff to show.