Kavya Sriram

UX Strategist · Chennai | Bangalore | Hyderabad
01 · About & Experience

Kavya — about and experience

Strategy, systems and people — untangled on a whiteboard, long before anything reaches a screen.

These are the hats I wear.

The three roles Kavya works in
UX DesignInterfaces, flows, systems.
UX ResearchDiscovery, testing, synthesis.
Design StrategyPositioning, product direction.
02 · Case Study

Nestora case study

An AI-driven, trust-first home-buying companion. Three builds, three rounds of testing, and one open question still being answered.

03 · Case Study

Wisr case study

A conversational layer over an existing bank. It turns a ledger into an answer — in English, with a Hindi, Tamil, Kannada or Telugu flavour.

05 · Recognition
06 · Contact

Reach out to Kavya

04 · Case Study

Playground

Digital Accessibility

01 · About & Experience

Kavya Sriram

Good design isn't about the pixels. It's about the decisions that come before them.

Who I am

Portrait of Kavya Sriram, smiling with her arms crossed, standing among palm trees
Senior Lead · Wongdoody · Bangalore

I'm Kavya — a UX Strategist who thinks the most important design work happens before anyone opens Figma.

In short

I’m a UX strategist focused on AI-led design and customer experience innovation. My background spans product design and financial services, where I’ve worked on building trust through thoughtful, human-centered interfaces. I’ve contributed research and mentorship within the IIT ecosystem and completed a certification in AI applications in design at IIT Delhi. I design for accessibility from the first wireframe rather than as a final check, and I’m an Infosys Certified Digital Accessibility Expert — this site is built that way, and you can inspect it.

02 · Experience

Senior Lead · Wongdoody, an Infosys companyJuly 2024 – Present

Owned end-to-end UX strategy and delivery for a savings-platform redesign for a major Irish bank — 100+ high-fidelity screens across complex customer journeys, from discovery through delivery.

Led design for an AI-powered Root Cause Analysis tool for a major global technology company, mapping business requirements to end-user needs — lifted task completion rates by 60%.

Built Wisr, a conversational banking assistant, out of an internal innovation initiative — kept developing it independently since.

Alongside the product work: RFP pursuits for a global banking client (UI modernisation) and an East Asian investment firm (rebranding and digital transformation), one of them won. I also designed and led a 12-week cross-disciplinary design bootcamp, mentoring designers into active delivery teams, and have hosted employee engagement experiences and produced social collateral — mailers, hiring campaigns, event coverage.

BFSI — deepCMT — 2 client projects, 1 liveEdtech — UX auditsServices — UX audits
Associate UI/UX Designer · Sarvatech LabsJan – Jul 2024

Six months inside an early-stage startup — the direct answer to whether I've worked inside a product company, not just alongside one as an agency partner. I designed end-to-end UX/UI for digital products — wireframes, interaction models, high-fidelity prototypes — tied to real user and business goals, working directly with developers on feasibility and implementation. I also built investor-facing pitch decks, translating product vision and growth opportunities for people deciding whether to fund it, not just people deciding whether to use it.

Research Assistant · IIT HyderabadOct 2023 – Jan 2024

A 14-month field study on digital transformation in rural FMCG supply chains across remote villages in Telangana — examining what actually stops technology adoption, and where inclusive design could close that gap. The research fed design frameworks for digital literacy, rural employment, and gender equity through kiosk and chatbot interfaces, and was co-authored into a peer-reviewed paper published at ICoRD 2025, included in Springer's Lecture Notes in Mechanical Engineering.

Download Resume

03 · How I Use AI

I don't use AI to skip the thinking. I use it to protect time for the thinking that matters. My process is tool-agnostic — I work across Copilot, Claude, and ChatGPT depending on context, client, and what the work actually needs.

Articulating Design Rationale

Strategic decisions are only as strong as the case you can make for them. Once I have the core of a rationale forming — even half-baked — I use AI to sharpen it into something I can pitch and sell. Not to generate the thinking. To make it land.

Generating Design Artefacts to React To

I use AI to generate first-draft artefacts — affinity maps, journey maps, task flows, synthesised session notes. The output is never final. It is a starting point to interrogate and push back on. Starting from a generated draft rather than a blank canvas surfaces better thinking faster.

Rapid Prototyping for RFPs and PoCs

Every RFP starts the same way: I read it manually, word by word. The real ask only reveals itself when you slow down. Once I've built my own understanding, AI enters to pressure-test my interpretation and scope what I might have missed. From there, prompting begins. The first draft is always rudimentary — what follows is a collaborative loop until we have an MVP ready to anchor a proposal.

I've designed for 15+ RFP pursuits across banking and investment clients, and the proposals I've contributed to have won at roughly a 60% rate — the highest-stakes writing I do, and where this process gets tested for real.

06 · Contact

Most of the good stuff starts with a conversation.
04 · Case Study

Playground

Digital Accessibility

Overview

I audited the portfolio you are reading, fixed what I found without removing the playful interactions, and left every change inspectable.

The animations were never the problem. For many visitors, they were the only way in.

Try it

Two tools run on every page of this site. Neither is a plug-in or an overlay; both are ordinary HTML, CSS and JavaScript you can read.

The X-ray button sits next to A11y in the top right corner of every page.

The audit

What I found in my own site

17

issues in the original build, across the home page, both case studies, the testimonials and the panels

8

of them serious: they stopped some people doing something, rather than just making it harder

4

were flagged by an automated scanner (axe-core). The other 13 came from keyboard testing, measurement and emulation

  • Measured: axe-core 4.10 against WCAG 2.2 AA on every page and panel, with contrast calculated from the colours the browser actually painted.
  • Walked: keyboard only, then reduced motion, forced colours, a 320px viewport and the WCAG 1.4.12 text-spacing values.
  • Re-run: every fix was checked again against the test that caught it.

Design

Equal path, not a lesser one

My rule was that no interaction gets removed. Each keeps its delight and gains an equal route, and the accessible route is the default, not a hidden mode.

What I kept, and the equal path to it
InteractionWhat it doesEqual path
Ring cursorA ring trails the pointer and swells over links.It wraps the real pointer instead of replacing it. Off for touch, reduced motion, forced colours, or “Pointer only”.
Flip, then expandA card flips and its colour grows into the next page.Cards are real links, so Enter, middle-click and open-in-new-tab all work. Under reduced motion it just navigates.
Photo and hat revealsHovering the About card brings in my photo and a hat per role.The same state on keyboard focus, with the hats cycling by themselves and Esc to dismiss. Static under reduced motion.
Typing bubblesSmall decorative hover scenes.Hidden from assistive technology. Nothing important lives only here.
Full-screen panelsAbout and Contact open over the home page.Native dialogs: focus moves in, the page behind is inert, Esc and Back close it, and #about is a shareable address.
Colour-coded tilesEach section has its own accent colour.Meaning also lives in headings and text. Text colours pass 4.5:1, and High contrast mode goes further.

Preferences, not an overlay

The site has to be accessible without anyone touching a setting. The A11y panel only adds comfort, starting from your device settings for motion and contrast. Nothing is injected from a third party, and nothing is claimed on the page’s behalf.

A11y preferences and the criterion each one serves
ControlCriterionLevelHow it’s met
Text size1.4.4 Resize TextAALarge and Larger set the root size to 125% and 150%, and every size on the site is in rem, so all text scales without clipping or sideways scrolling.
Spacing1.4.12 Text SpacingAAThe layout holds at the 1.4.12 line, letter, word and paragraph values, and Roomy adds extra spacing for anyone who wants it without a browser extension.
Contrast1.4.6 Contrast (Enhanced)AAAHigh swaps tinted backgrounds for white, darkens the text colours, thickens borders and underlines every link, aiming for the 7:1 enhanced ratio.
Motion2.3.3 Animation from InteractionsAAAReduce turns off flips, reveals and transitions, and Auto follows the device’s reduced-motion setting.

Evidence

17 fixes, by X-ray layer

Each fix opens in the X-ray on the live page, with the real code and its before and after.

Landmarks · 1

Shown as markers in the X-ray.

Headings · 1

Shown as markers in the X-ray.

Controls · 3

Shown as markers in the X-ray.

Images · 1

Shown as markers in the X-ray.

Measurements · 2

Shown as markers in the X-ray.

Behaviour · 9

No marker. These change how the site behaves.

Impact

How it was tested, and what I am claiming

Target: WCAG 2.2 Level AA. Status as of 13 October 2026: automated and scripted checks pass; testing with real assistive technology is still to do, and I will not claim it until it is done.

Checks run on the fixed build
CheckResultDetail
axe-core 4.10.2 (WCAG 2.0–2.2 A/AA + best practice)Pass0 violations on the home page, About and Playground panels, Nestora, Wisr, Says and this page.
Keyboard, dialogs and historyPassScripted walks: cards, panels, Back button, focus return and browser Back behave correctly.
320 px reflow (1.4.10)PassNo horizontal overflow on any page.
Reduced motion and forced colorsPassEmulated; no overflow or script errors. Visual review of forced colors is still manual.
Target size (2.5.8)PassEvery visible control measured at 24 × 24 px or larger, or is a stretched card link.
Screen readers (NVDA, VoiceOver, TalkBack)PendingNot yet tested. No conformance claim is made until this is done.
Assistive-technology testing
CombinationStatus
NVDA with Firefox (Windows)Pending
VoiceOver with Safari (macOS and iOS)Pending
TalkBack with Chrome (Android)Pending

Known gaps

  • Screenshots of the Nestora and Wisr prototypes have text alternatives that summarise each screen, not a full transcription of every word on it.
  • Fonts load from Google Fonts. If they are blocked, the page falls back to Georgia and system sans-serif, which is readable but not the intended look.
  • Prototype screens are images, so their own text does not respond to the text-size preference.
  • Hindi, Tamil, Kannada and Telugu text on the Wisr screens has not been checked against screen-reader pronunciation.
  • Font coverage for the Indian-language text on Wisr has not been checked.
  • Nobody who uses assistive technology every day has tested the site yet, only me and the scanner.
  • There are no demo videos yet. Any added to Nestora or Wisr will need captions and a transcript first.

Found a barrier I missed? Please tell me: Kavya.sriram2000@gmail.com.

Certification

Infosys Certified Digital Accessibility Expert

Everything above is the how. This is the credential behind it.

Infosys Certificate of Achievement awarded to Kavya Sriram for successfully completing Infosys certified Digital Accessibility Expert on September 30, 2026. Issued Friday, October 9, 2026, valid till Saturday, September 30, 2028. Signed by Satheesha B. Nanjappa, Senior Vice President and Head, Education, Training and Assessment, Infosys Limited.
Earned 30 September 2026, valid until 30 September 2028. Verify by scanning the QR code at validate.onwingspan.com (opens in a new tab).

Reflection

I expected the playful parts to be the casualties, and they mostly survived. What failed was structure: real links, focus management, heading order and colour maths. That is why I would rather catch it in the first wireframe than in the last sprint.