Muted secondary text fails WCAG AA contrast (gray-400 on light) #114
Labels
No labels
bug
duplicate
enhancement
future
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/TeaLeaves#114
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: Low · Confidence: Medium · Effort: M · Category: ui (accessibility)
Evidence
app/src/pages/Entries/EntryCard.tsx:68,app/src/pages/Search/SearchPage.tsx:301,app/src/pages/Settings/SettingsPage.tsx:75-76,app/src/pages/Trash/TrashPage.tsx:292- pervasivetext-gray-400/text-zinc-400on light backgrounds → 2.8:1, below AA's 4.5:1 for small text.Problem
Timestamps, hints, and secondary labels throughout use a muted tone that fails AA contrast at small sizes. Reads as a deliberate style (Tailwind default gray-400) but is systemic.
Impact
Low-vision readability across the app; none is essential-path text, so Low.
Fix
Bump muted text to
gray-500/zinc-500(dark-mode-safe equivalents), verified against actual backgrounds - or verify and document the choice.Acceptance criteria
Filed from the 2026-07-15 codebase audit. Full report:
docs/.internal/report-2026-07-15.md(gitignored).Swept pervasive muted secondary text (
text-gray-400/text-zinc-400on light, ~2.8:1) to the AA-passingtext-gray-500 dark:text-gray-400pair across ~48 files, verified in both light and dark.Shipped in
59e4fdd(test fix6561f9a), part of the v7.3.0 milestone. Verified on dev (v7.2.1-3-g6561f9a): app suite 65/65 and api suite 268/268 green on the dev server; the one CI red was the known runner flake (iac#159), not this change.