Adapting Facebook for blind users: needs, solutions and success metrics

You are a product manager asked how Facebook should be built for people who are blind. Set the goal, decide exactly who you are designing for, find where the current experience fails them, propose and prioritize solutions, and explain how you would measure success. ```hint Use it without looking Go through an ordinary session step by step as someone who cannot see the screen, and note at each step which information or action is lost. ``` ### Clarifying Questions - Does "blind" mean people with no usable vision only, or should low vision and color blindness be covered too? - Is the expected output a separate product or changes inside the existing Facebook apps? - Which platforms are in scope: the mobile apps, the website, or both? - Is the goal to bring more blind people onto Facebook, or to deepen engagement among those already using it? ### What a Strong Answer Covers - A goal for the effort and how it ties to what Facebook is for - Blind users segmented in a meaningful way, with one segment chosen and the reason - Pain points found by walking a real session without sight, ranked by frequency and by how much they block - Solutions compared with explicit criteria, with a clear reason the top choice wins - A primary metric with guardrails, the main risks, and how blind people take part in testing ### Follow-up Questions - How would you keep new features from breaking accessibility as many other teams ship changes? - How would your priorities change if the target were people with low vision rather than no usable vision? - How would you find and recruit blind users for research, and what would you want to learn from them first?