docs(alignment): record dark-accent ownership decision #66
No reviewers
Labels
No labels
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
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
Toilville/toilville-design!66
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/dark-accent-ownership"
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?
Records the dark-accent ownership decision (2026-07-25) in the strategy doc so no one re-attempts to force dark coupling and regresses contrast.
The finding: the DTCG and the Rituals app use opposite, incompatible dark-accent schemes — the app inverts accent lightness (light/pastel fills + dark on-accent text via
textOnAccentDark), the DTCG darkens accents for white on-accent text (wcag.py._darken_accent). Both are WCAG-AA; forcing either direction regresses the app'stextOnAccentDark/accentErrorcontrast test. Soalign_checkgoverns the light map only, and dark divergence is expected, not drift.Also updates the shipped status now that the Swift emitter (#64) and the app-side coupling (#190) have landed. Docs only.