Type of Project: Real-world client project, 2024 to 2025. I worked as a Senior UX/UI Design Consultant.
Year: 2024–2025

The project itself
Accessibility audits and research with assistive-technology users
Journey mapping
Usability testing and UAT
Wireframes, interaction flows, and prototypes
Design systems and color tokens
All about the Problem
Members who use screen readers or keyboards couldn't finish basic banking tasks on their own. Focus order was broken, labels and alt text were missing, and the brand yellow failed contrast on white. Web and mobile also used different components, which confused members and drove support calls. Several critical flows didn't meet WCAG 2.1 AA, which put Golden 1 at legal risk.
The goal: bring web and mobile banking up to WCAG 2.1 AA without losing the brand.
I led the accessibility research and audits, designed the wireframes, flows, and prototypes, and pushed for accessibility to live in the design system. I worked with product, QA, engineering, and Level Access, an accessibility partner.
6 months
across 2024 and 2025
6 months
across 2024 and 2025
Two platforms (web and mobile) with different component sets
Regulated industry: changes had to pass compliance and QA
Research with members, internal teams, and support reps
Journey map of the assistive-technology experience
Usability studies and fixes
The brand color decision (semantic tokens)
Accessible component library and high-fidelity design

Measured 60 days after launch:
30%
40% faster design-to-code cycles
25% fewer UI inconsistencies across web and mobile
15+ reusable WCAG-compliant components
What I'd change: bring QA into accessibility planning earlier, define testing alongside design tokens, and document component decisions in Confluence sooner.
30%
Reduced WCAG 2.1 AA violations on login and transfer flows from 120 to 84
40%
Faster design-to-code cycles enabled by the new component library and reusable patterns, which reduced handoff friction.
25%
Reduction in UI inconsistencies through standardized component libraries aligned with ADA and brand guidelines across web and mobile.
15%
reusable WCAG-compliant components
Process details
What
Talked with 10 digital banking members (including screen reader and keyboard users), 5 product and QA team members, and 3 customer support reps.
Why
Automated audits list violations, but they don't show which ones stop a member from paying a bill. I needed both views.
How
Moderated sessions with members using their own assistive tech, interviews with QA, a review of support tickets with reps.
Result
The biggest blockers were in login and transfers. Support reps confirmed these drove the most accessibility-related calls.
Learned
Support reps were an underused source. They already knew where members got stuck.
The clear version
What
Mapped four stages (login, account review, transfer, logout) for an assistive-technology user.
Why
To decide where to start with limited time.
How
Scored each stage on screen reader compatibility, keyboard navigation, and member confidence.
Result
Authentication and transfer scored lowest, so they became the design priorities.
Learned
Scoring stages made prioritization easy to defend with stakeholders.]

Sixty days after launch, the impact was measurable across compliance, engagement, and team efficiency.
What
Ran 2-3 rounds of UAT and accessibility walkthroughs with assistive-technology users.
Why
To catch what automated tools miss.
How
3-4 rounds with 5-6 participants. Fixes came straight from the sessions:
Tab order skipped key actions in transfers. Fixed with a restructured DOM and explicit focus management.
Disabled buttons fell below 3:1 contrast. Adjusted the token to meet AA.
Mobile buttons were under 44x44px and caused missed taps. Scaled to 48px with 8px padding.
Result
Issues automated audits missed, like spacing for screen magnifier users, were found and fixed before launch.
Learned
Testing with real assistive-tech users was the most valuable step in the project.
What began as a compliance audit became a shift in mindset. Designing with accessibility at the core turned frustration into confidence for every user.
What
Resolved the conflict between Golden 1's yellow and WCAG contrast.
Why
The yellow is recognized from branches and marketing, but fails AA on white.
How
I compared three options: darken the brand palette, limit yellow to decoration, or build semantic color tokens. I chose tokens. Yellow stays as the brand color, and buttons, text, and interactive states map to accessible variants automatically.
Result
Engineers got one source of truth, and new components are accessible by default.
Learned
Fixing accessibility in the system, not page by page, is what made the work last.
What began as a compliance audit became a shift in mindset. Designing with accessibility at the core turned frustration into confidence for every user.
What
Added 15+ WCAG-compliant components to Golden 1's design system and finished high-fidelity designs for web and mobile.
Why
Different components on web and mobile were causing confusion and support calls.
How
Built accessible checkboxes, switches, radio buttons, progress indicators, status messages, and form fields with clear focus states in Figma, documented in Confluence, tracked in Jira.
Result
25% fewer UI inconsistencies and 40% faster design-to-code cycles.
Learned
Documenting decisions earlier would have saved rework.
