MotirBuilding in public
MOTIR · moooon
onMotir
You’re viewing a public project. Anyone can view it — no account needed. Sign in to submit, upvote, or comment on requests.View-only — you can’t edit work items
MOTIR-757

6.16 Primary Button text fails AA contrast in dark theme (app-wide)

Done
Description

Type: bug · accessibility (color-contrast) Parent: Epic 6 (Search, reporting & admin) Discovered in: 6.7.3 combined a11y sweep (tests/e2e/epic6-at-scale.spec.ts), dark theme, on the Fields / Components admin “Add” buttons.

Symptom: axe color-contrast (serious, WCAG 2.1 AA / 1.4.3). The primary Button variant renders bg-(--el-accent) text-(--el-accent-text); in dark theme --el-accent = #7b6ce5 and the text is #ffffff, giving ≈ 4.1:1 for normal-size (≈14px) label text — below the 4.5:1 AA threshold.

Scope: APP-WIDE — every primary <Button> in dark theme, not just these two. The per-story a11y closers missed it because they sweep light theme (and/or didn’t render a primary button); the populated dark sweep in 6.7.3 is the first to hit it.

Root cause / fix: darken the dark --color-primary (or lighten --el-accent-text handling) in app/globals.css [data-theme='dark'] so primary-button text reaches ≥ 4.5:1, then re-run the full a11y + at-scale sweeps. This is a design-system token change (design-gated) — belongs in its own PR, owned by the 1.0.5 design system, NOT in the 6.7.3 test PR.

Blocks: 6.7.3 (PR #1170) — its combined a11y sweep stays red until this is fixed. Resolution: (open)