Build Log
Known Accessibility & Mobile Remediation
July 6, 2026
Audited Known's typography and contrast against dementia-caregiver accessibility research, then shipped three phases fixing legibility, touch targets, and theme consistency — while keeping the product's warmth intact.
Timeline
What shipped
Typography/accessibility audit of Known against WCAG and dementia-care design research, delivered as a reviewed artifact before any code changed
Phased remediation plan (4 phases) that explicitly preserves product warmth while fixing legibility — Phase 0-2 shipped this session, Phase 3 (text-size toggle, focus/keyboard) deferred
Phase 0: restored pinch-to-zoom, fixed WCAG-failing muted-foreground token (2.48:1 -> 4.62-5.24:1), removed opacity-suppressed placeholder text on the Known Card and Guide eyebrow label
Phase 1: moved the app's base body font and textarea font from Kalam (handwriting) to Inter, keeping Caveat on all headings plus two explicit keepsake exceptions (Known Card subject name, Book Portrait cover)
Phase 2: mobile-first responsive padding, Known Card banner wrap fix, keyboard-safe capture textareas, ~90 hover:/active: state pairs across ~30 files, 44px touch targets on daily-use controls, fixed the 'Known Card' preview header hierarchy outlier, computed real per-theme WCAG contrast before fixing a systemic low-opacity theme-color convention, wired portrait.colorTheme into Care Card and Takeover (previously hardcoded to the warm theme regardless of the family's actual choice)
Deployed to known.forgekits.build — verified live via manifest.json and viewport meta checks against production, not just local
“that why we used the handwriting font... bad choice I guess”