Accessible banking product case for people who are blind or have low vision

You are a product manager asked to design a banking app for customers who are blind or have low vision. Explain exactly who you are designing for, which everyday banking tasks matter most to them, how the experience works for those tasks, what you would build first, and how you would measure success. ```hint Bank without looking Pick one routine money task, such as paying a bill, and walk through it with the screen out of sight; mark every step where a sighted customer depends on a visual cue. ``` ### Clarifying Questions - Is this a new app built only for these customers, or the bank's main app made to work well for them? - Which platforms are in scope: phone, web or both? - Should the design target people who are fully blind, people with low vision, or both, given that their needs differ? - Which banking services should the app cover: everyday accounts, cards, bill pay and transfers, or more? ### What a Strong Answer Covers - How needs differ between people who are fully blind and people with low vision, and which group the first version is designed around - The key banking tasks traced step by step, with the moments where sight-dependent design breaks them - How the design works with screen readers, magnification and voice, and how sign-in, verification and fraud protection stay usable without sight - Prioritized features with explicit criteria, and a plan to test them with blind and low-vision customers - A primary success metric with guardrails, and the risks of moving money without visual confirmation ### Follow-up Questions - How would a blind customer confirm the amount and recipient of a payment with confidence before the money moves? - How would you protect these customers from scammers and from people overhearing a balance read aloud? - How would you keep features that other teams ship later from breaking accessibility?