Designing a New iPhone Capability for an Underserved Disability Group

Quick Overview

An accessibility product design question for Apple: choose a group of iPhone users with disabilities, find a need the phone's existing features leave unmet, and design a feature for it. It tests user empathy, awareness of what already ships, prioritizing a first version, safety and privacy, and success metrics for a small population.

Designing a New iPhone Capability for an Underserved Disability Group

Company: Apple

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Apple. Design a new iPhone feature that improves accessibility for people with disabilities. Choose the group of users you will serve, describe their needs and where the iPhone still falls short for them, propose and prioritize solutions, and explain how you would measure whether the feature succeeds. ```hint Start from what already ships The iPhone already includes a broad set of accessibility features, such as a screen reader, voice control, live captions and switch control. A strong answer finds a need those features leave unmet instead of rebuilding one of them. ``` ### Clarifying Questions - Is the choice of disability mine (vision, hearing, motor, speech, cognitive), and may the feature serve more than one group? - Should the feature be software on existing iPhones, or may it involve new hardware or accessories? - What is Apple's goal here: reaching people who do not use an iPhone today, deepening use among people who already rely on accessibility settings, or strengthening trust in the platform? - Should any markets or languages come first, given that speech and text features depend on language support? ### What a Strong Answer Covers - A chosen disability group with a justification (size, severity of the unmet need, Apple's capabilities), and awareness of the accessibility features the iPhone already has. - Concrete pain points drawn from a realistic daily journey, ranked to identify the biggest remaining gap. - A feature described in enough detail to judge (interaction model, where processing happens, behavior when it fails), with prioritization and a clear first version. - Success metrics suited to a small, sensitive population, including task success and trust, with privacy guardrails. - Risks such as errors in safety-relevant situations and camera or health-data privacy, and how disabled users take part in design and testing. ### Follow-up Questions - How would you validate the feature when the target population is small and its needs vary widely? - The feature gets something wrong in a safety-relevant moment. How should it behave, and how should it communicate uncertainty? - How would you measure success without collecting data that reveals a user's disability?

Overview: An accessibility product design question for Apple: choose a group of iPhone users with disabilities, find a need the phone's existing features leave unmet, and design a feature for it. It tests user empathy, awareness of what already ships, prioritizing a first version, safety and privacy, and success metrics for a small population.

Apple logo
Apple
Aug 12, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Apple. Design a new iPhone feature that improves accessibility for people with disabilities. Choose the group of users you will serve, describe their needs and where the iPhone still falls short for them, propose and prioritize solutions, and explain how you would measure whether the feature succeeds.

Clarifying Questions Guidance

  • Is the choice of disability mine (vision, hearing, motor, speech, cognitive), and may the feature serve more than one group?
  • Should the feature be software on existing iPhones, or may it involve new hardware or accessories?
  • What is Apple's goal here: reaching people who do not use an iPhone today, deepening use among people who already rely on accessibility settings, or strengthening trust in the platform?
  • Should any markets or languages come first, given that speech and text features depend on language support?

What a Strong Answer Covers Guidance

  • A chosen disability group with a justification (size, severity of the unmet need, Apple's capabilities), and awareness of the accessibility features the iPhone already has.
  • Concrete pain points drawn from a realistic daily journey, ranked to identify the biggest remaining gap.
  • A feature described in enough detail to judge (interaction model, where processing happens, behavior when it fails), with prioritization and a clear first version.
  • Success metrics suited to a small, sensitive population, including task success and trust, with privacy guardrails.
  • Risks such as errors in safety-relevant situations and camera or health-data privacy, and how disabled users take part in design and testing.

Follow-up Questions Guidance

  • How would you validate the feature when the target population is small and its needs vary widely?
  • The feature gets something wrong in a safety-relevant moment. How should it behave, and how should it communicate uncertainty?
  • How would you measure success without collecting data that reveals a user's disability?