How One Fintech Rewrote Its Design System for Low‑Vision Users—and Cut Support Calls 32%

Design · 6 min read

How One Fintech Rewrote Its Design System for Low‑Vision Users—and Cut Support Calls 32%

The design team at a regional fintech took a data‑driven approach to revamp their design system for low‑vision and cognitive accessibility. They prioritized three changes: moving to a contrast-first color palette, redesigning layout components to support dynamic type and zoom, and adding a voice‑first navigation layer for common tasks like checking balances and initiating transfers.

They introduced 'contrast' and 'typeScale' tokens, refactored inputs and tables to reflow at large sizes, and published voice intents and sample utterances as part of their component docs. Crucially, they rolled these changes into a migration path for older products: codemods updated thousands of component imports and a release pipeline provided visual diffs and accessibility smoke checks before deployment.

Results came quickly. Within six months the company saw a 32% drop in support tickets tagged 'cannot read' or 'screen reader issues,' and a measurable increase in session lengths for users who opted into larger text and high-contrast themes. Product teams also reported fewer last‑minute accessibility fixes thanks to clearer design system defaults.

The case highlights practical takeaways: treat accessibility tokens as part of the public API of a design system, automate migrations, and measure outcomes. For design professionals, it’s a reminder that accessibility efforts can be strategic investments that reduce support costs and improve retention for underserved user groups.