Design Accessibility and Inclusion Features for the Chrome Browser

You are a product manager at Google working on its web browser; assume the browser is Chrome. What features would you add to make it more inclusive, so that people who are poorly served by today's web can browse comfortably and on their own? Explain whom you would design for and why, the problems they hit during everyday browsing, the features you propose, which one you would build first, and how you would measure whether it helps. ```hint Narrow the group and the task Inclusiveness covers many groups. Pick one, then walk through a common browsing task, such as filling in a form or reading a long article, and note exactly where it breaks for them. Design features for those steps. ``` ### Clarifying Questions - Does inclusiveness here mean accessibility for people with disabilities, or does it also cover age, language, literacy, slow connections and low-cost devices? - Which platforms are in scope: desktop, Android, iOS, or all of them? - Is the goal adoption among underserved users, task success, or a mission goal with no revenue target? - Must the features work on every website as it is today, or can they depend on site owners adopting new standards? ### What a Strong Answer Covers - A clear reading of inclusiveness and a reasoned choice of one underserved group, with awareness of the groups set aside - Barriers tied to concrete browsing tasks, such as filling in forms, navigating pages and managing tabs, rather than generic complaints - Features that work on websites as they exist today and complement operating-system assistive tools, prioritized by impact and effort - Success measures based on task completion for the chosen group rather than time spent, with privacy protections because usage can reveal a disability - Risks such as features that break page layouts or trigger the wrong action ### Follow-up Questions - How would you measure whether your feature helps people with disabilities without collecting data that identifies their disability? - Your first feature works on most sites but breaks the layout of some popular ones. Do you launch, and how? - How would you argue for this work against features that serve the browser's broad user base?