TOPIC
Accessibility
These are the same questions found in the library, grouped here by the capability each one mainly examines.
24 questions
A · Professional problem solving and implementation14
- A core flow passes mouse testing, but keyboard or screen-reader users cannot complete it. How would you include accessibility in release gates?
- A critical user journey across several pages and services regresses often. How would you define the scope and priority of automated tests?
- A custom dialog works with a mouse, but keyboard users cannot reliably enter, close, or return from it. Which focus-management behaviors would you inspect, and how would you verify a fix?
- Interview participants are almost all power users and community members. Feedback on the latest redesign is positive, but retention continues to fall. How would you redesign recruitment and research questions?
- Teams are copying shared components and adding local variants, making similar features inconsistent. How would you decide which differences belong in the shared design system and which should remain team-specific? How would teams help maintain those rules?
- During user interviews, people repeatedly suggest buttons, filters, and reminders but rarely describe their goals or blocked situations. How would you adjust question order and wording to distinguish real experiences, stated preferences, and proposed solutions?
- The team believes a new flow is simpler, but usability tests show only familiar users succeed; newcomers get stuck on permission explanations and next steps. How would you recruit, design tasks, and define observations to judge whether it is actually usable?
- An operations table uses red, yellow, and green for risk. Some users cannot distinguish the colors, and screen readers announce only values. How would you redesign the information?
- After submitting a form, users see “validation failed,” with no field identified and no entered data preserved. How would you redesign the error and recovery path?
- A desktop admin table has 14 columns, while mobile users need to handle exceptions in the field. How would you decide what to retain, hide, or move to details?
- A dashboard flags anomalies but shows no magnitude, baseline, or related events. Users export data to interpret it themselves. How would you improve diagnosis?
- Review feedback centers on “not premium enough” or “I dislike this color,” but the team has no shared user goal. How would you run the next review?
- Operators, managers, and auditors share a workspace but need different information and permissions. How would you design default views and personalization?
- The product serves professionals and must use industry terms, but new users often stop or choose incorrectly. How would you design comprehension support?
No questions in this section match your target. ·
C · Value judgment and direction setting7
- Brand asks for low-contrast text, but users with low vision struggle to read it; increasing contrast changes the brand presentation. How would you make and validate the design decision?
- A critical flow is two weeks from launch when a review finds that keyboard users cannot complete one step. A full redesign would affect the date. How would you assess the impact, negotiate scope with the team, and explain what can be staged versus what cannot safely ship?
- A mobile onboarding redesign helps more users complete setup on day one, but active retention drops two weeks later; the flow also requests more permissions. How would you judge whether short-term conversion masks lower long-term value or loss of trust?
- A keyboard-navigation defect affects few users but prevents them from completing a critical task; a feature expected to add revenue is also waiting. How would you compare user harm, obligations, opportunity cost, and repair scope?
- Accessibility improvements require changes to several shared components and will not add immediate revenue, but can reduce user blockers, legal risk, and repeated fixes. How would you estimate value, scope the work, and demonstrate effectiveness?
- A configuration form has 28 fields. A multi-step design may increase abandonment, while one page is hard to understand. How would you gather evidence and decide?
- A map relies on dragging and zooming, making the same location data hard to access on mobile and by keyboard. How would you design equivalent controls?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth3
- An accessibility review finds screen-reader and dynamic-type issues in a mobile app. How would you carry the lessons into future implementation?
- After launch, low-vision users cannot complete a key task, and the original study did not include them. How would you review and correct the research process?
- There is no formal accessibility project, but you notice a common flow fails for users with dynamic type. How would you assess and drive improvement?
No questions in this section match your target. ·