Building Accessible Banking for Everyone: U.S. Bank's Native Design System Launch

Overview

U.S. Bank serves over 70 million customers, many of whom rely on mobile banking for daily financial tasks. When the bank decided to launch a unified native design system across iOS and Android platforms, accessibility wasn't an afterthought—it was foundational to the entire strategy.

As the accessibility lead for this initiative, I worked alongside product teams, designers, and engineers to ensure that every component, pattern, and interaction would work seamlessly for customers using assistive technologies. The goal was ambitious: create a design system that would not only meet WCAG 2.2 AA standards but exceed them, setting a new benchmark for accessible banking experiences.

The Challenge

The existing mobile apps had grown organically over years, resulting in inconsistent accessibility implementations across different features. Customer feedback revealed frustrating experiences for users with disabilities—screen readers couldn't properly announce account balances, focus management was unpredictable during transactions, and color contrast varied wildly between different sections of the app.

The challenges were complex:

  • Regulatory Requirements: U.S. Bank's internal accessibility policy required WCAG 2.2 AA compliance, incorporating requirements from various geographic regulations where the bank operates
  • Legacy Technical Debt: Existing accessibility implementations were scattered and inconsistent across teams
  • Scale: The design system would impact dozens of product teams and millions of daily banking interactions
  • Platform Differences: iOS and Android handle accessibility differently, requiring platform-specific solutions within a unified design language
  • High-Stakes Interactions: Banking transactions require precise communication—any accessibility gaps could lead to financial errors or security concerns

The executive team made it clear: we couldn't just bolt accessibility onto existing patterns. It needed to be built in from the ground up.

The Vision

The vision was straightforward but technically demanding: every customer should be able to complete any banking task independently, regardless of their abilities or the assistive technology they use.

This meant:

  • Universal Design: Components that work better for everyone, not just users with disabilities
  • Seamless Navigation: Logical focus flow and clear information hierarchy throughout complex banking workflows
  • Clear Communication: Every piece of financial information announced clearly and completely
  • Platform Consistency: Similar accessibility behavior across iOS and Android, respecting each platform's conventions
  • Future-Proof Foundation: Accessibility patterns that could scale as the design system evolved

The Work

Discovery and Audit

I started by conducting comprehensive accessibility audits of existing mobile patterns, working directly with customers who use assistive technologies. These sessions revealed pain points that internal testing had missed—like how VoiceOver users struggled to distinguish between multiple account balances on the same screen.

Component-Level Accessibility Architecture

Working closely with the design system team, I established accessibility requirements for every component before any visual design began. Each component specification included:

  • Semantic structure and native accessibility API requirements (translating web ARIA concepts to Swift UIAccessibility and Android accessibility APIs)
  • Focus management behavior following Material Design and Human Interface Guidelines
  • Screen reader announcements optimized for each platform's assistive technologies
  • Touch target specifications meeting both iOS HIG (44pt minimum) and Material Design (48dp minimum) requirements
  • Color contrast requirements exceeding WCAG 2.2 AA standards
  • Dynamic type and zoom support integrated with platform accessibility features

Cross-Platform Implementation Strategy

iOS and Android have different accessibility APIs and user expectations, requiring thoughtful translation of web accessibility concepts to native implementations. For example, while web development uses ARIA labels and roles, native mobile development requires mapping these concepts to Swift's UIAccessibility framework and Android's accessibility APIs. I developed platform-specific guidance that respected each system's conventions—iOS components leveraged UIAccessibilityTraits for semantic meaning, while Android implementations used ContentDescription and AccessibilityNodeInfo to achieve equivalent functionality within Material Design patterns.

Enterprise Collaboration and Risk Management

One of the biggest challenges was bridging the gaps between product strategy, design, development, and risk management teams. Each group had different priorities and concerns about accessibility implementation. I facilitated cross-functional workshops where risk teams could understand how accessibility features actually reduced compliance risk, while product teams learned how accessible design patterns improved usability for all customers. This collaboration was crucial for getting buy-in on the additional development time needed for proper accessibility implementation.

Testing and Validation Framework

I established automated testing protocols integrated into the development pipeline, catching accessibility issues before they reached production. More importantly, I set up regular testing sessions with actual assistive technology users, ensuring our theoretical implementations worked in real-world scenarios.

Team Education and Documentation

Accessibility knowledge had to be distributed across dozens of product teams. I created comprehensive documentation, ran training workshops, and established "accessibility office hours" where teams could get real-time guidance on implementation questions.

The Results

The native design system launched successfully, with strong accessibility outcomes across all core banking workflows:

  • Full WCAG 2.2 AA compliance achieved across the component library
  • Consistent accessibility implementation across all product teams using the system
  • Streamlined development process as accessibility requirements were built into every component
  • Positive adoption from development teams who no longer needed to implement accessibility from scratch

Long-Term Impact

Beyond the immediate technical wins, the project established accessibility as a core competency within U.S. Bank's product organization. The design system became a model for other digital initiatives, and the accessibility framework was adopted by the bank's web properties as well.

The work also influenced industry standards—several patterns we developed for accessible financial interactions were later incorporated into platform-level accessibility guidelines from Apple and Google.

Team Feedback

"Having accessibility built into every component saved us weeks of development time. We went from struggling with accessibility implementations to having them just work out of the box." — iOS Development Lead

"The clear documentation and platform-specific guidance made it possible for our team to implement accessible features correctly the first time, instead of having to retrofit them later." — Product Manager, Digital Banking

The design system team also noted significant impact beyond individual projects. Accessibility reviews became faster and more consistent, and teams reported increased confidence in their accessibility implementations.

Final Thoughts

This wasn't just about compliance or checking boxes—it was about recognizing that accessible design is better design for everyone. The clarity and consistency required for assistive technology users made the entire banking experience more intuitive and reliable.

The U.S. Bank design system proved that accessibility and business goals aren't competing priorities. By building accessibility into the foundation, we created a more robust, maintainable, and user-friendly system that serves all customers better.

When accessibility is embedded in the design process from day one, it doesn't slow things down—it makes everything stronger.

Made with 🫀 | © Dromena 2025