Skip to contentHarish ReddySenior Product Designer
Back to design systems

Fintech / Production-ready / Design handoff

Finlens
Design system.

The production-ready design system behind Finlens. Clear financial signals, reusable research components and specifications that connect product design to implementation.

Explore the components
Finlens / A connected design language
Aa
Stock research / Verdict card

One clear view.

BuyConfidence
High
<Component variant="default" />

Accessibility / Design & developer handoff

Built around WCAG 2.2 AA.

WCAG 2.2 Level AA guides the design and implementation requirements. Recommendations, risk and price changes pair color with labels, signs and values. Charts need a readable summary and an equivalent data view; hover alone must never hide essential research.

Readable, beyond color

Text contrast: at least 4.5:1, or 3:1 for large text. Essential control boundaries and state indicators: 3:1. Labels and symbols carry meaning alongside color.

1.4.1 · 1.4.3 · 1.4.11

Keyboard & focus

Every action works by keyboard, with visible focus that stays in view. Dialogs contain focus, support Escape and return focus to the trigger. Web targets meet the 24 × 24 CSS px minimum or its spacing exception.

2.1.1 · 2.1.2 · 2.4.7 · 2.4.11 · 2.5.8

Clear names & feedback

Controls expose their name, role and state. Inputs have persistent labels and linked error messages. Async results use status announcements without moving focus.

1.3.1 · 3.3.1 · 3.3.2 · 4.1.2 · 4.1.3

Adaptable layouts

Support text resizing to 200% and reflow at 320 CSS px without losing controls or content. Respect reduced-motion preferences and provide text alternatives for meaningful graphics.

1.1.1 · 1.4.4 · 1.4.10 · Motion preference

Release checklist: test every state with keyboard and screen readers, zoom and narrow layouts; measure actual foreground/background pairs. Static product screens document visual intent and do not establish app conformance. View the WCAG 2.2 requirements ↗

FoundationsComponents & statesSpecificationsDeveloper handoff
←Back to Finlens case study
Finlens Design System Storybook
atoms/button
Canvas:

Button Component

Primary CTA, Secondary Button, and Tertiary Ghost variants.

Purpose & Usage Guidelines

Primary interaction trigger for requesting AI stock verdicts and submitting high-intent user actions.

When & Where to Use: Use Primary Button for the single key action per surface ('Get AI Verdict', 'Try App'). Use Secondary Button for secondary actions ('Add to Watchlist'). Use Tertiary Button for inline text actions.

Best Practices & Guidelines

DO'S (Recommended)
  • Pair primary CTA with an icon (Sparkles or Arrow) to reinforce AI and movement.
  • Provide smooth hover (#CDFFAD), pressed (#8ED960), and focus outline states.
  • Maintain minimum 44px height for touch targets.
DON'TS (Avoid)
  • Do NOT place multiple Primary Buttons side by side.
  • Do NOT use primary lime background for destructive actions.

Arrivals / Contact

Every great journey starts
with a conversation.

Open to senior product design roles and thoughtful product collaborations.