User Experience Design Technology & Digital Applications 3 β Questions and Answers
Question 1: When designing for touch interfaces, what is the recommended minimum touch target size according to most platform guidelines?
- 44x44 points (iOS) or 48x48 dp (Android) (Correct answer)
- 16x16 pixels
- 24x24 pixels
- 60x60 pixels
Correct answer: 44x44 points (iOS) or 48x48 dp (Android)
Apple HIG recommends 44x44 pt and Google Material Design recommends 48x48 dp as minimum touch targets to prevent mis-taps.
Question 2: What is 'skeleton screen' loading, and why is it preferred over spinner-based loading in UX?
- Placeholder content shapes that mimic the final layout, reducing perceived wait time (Correct answer)
- A dark-themed loading screen shown on low battery
- A wireframe shown while JavaScript initializes
- An error state displayed when content fails to load
Correct answer: Placeholder content shapes that mimic the final layout, reducing perceived wait time
Skeleton screens show the page structure before data arrives, giving users a sense of progress and reducing the feeling of waiting compared to an indefinite spinner.
Question 3: In web accessibility, what is the purpose of ARIA `role` attributes?
- To convey semantic meaning of UI elements to assistive technologies when native HTML semantics are insufficient (Correct answer)
- To style elements based on their function
- To restrict keyboard focus to specific elements
- To define animation behaviors for screen reader users
Correct answer: To convey semantic meaning of UI elements to assistive technologies when native HTML semantics are insufficient
ARIA roles supplement or override the implicit semantics of HTML elements, ensuring screen readers can correctly interpret custom widgets.
Question 4: Which of the following best describes the UX benefit of using a design system with a shared component library?
- It ensures visual and behavioral consistency across products while speeding up design and development (Correct answer)
- It prevents designers from creating new UI patterns entirely
- It eliminates the need for user research before launching features
- It automatically generates accessible code
Correct answer: It ensures visual and behavioral consistency across products while speeding up design and development
Shared component libraries create a single source of truth that aligns design and engineering, reducing inconsistency and duplicated effort across teams.
Question 5: What is 'infinite scroll' and what is a key UX drawback of this pattern?
- Continuously loading content as users scroll down; it makes it hard to reach footers and track position in a list (Correct answer)
- A scroll animation that loops back to the top; it wastes bandwidth
- Paginated content loaded on demand; it's too slow for mobile
- A fixed sidebar navigation; it obscures content on small screens
Correct answer: Continuously loading content as users scroll down; it makes it hard to reach footers and track position in a list
Infinite scroll improves content discovery but traps users in a feed with no clear end, making it difficult to find previously seen items or access page footers.
Question 6: In the context of digital UX, what does 'deep linking' enable?
- Navigating directly to a specific screen or state within an app via a URL (Correct answer)
- Embedding one app inside another app's interface
- Caching app content deep in device storage
- Linking databases directly to UI components
Correct answer: Navigating directly to a specific screen or state within an app via a URL
Deep links allow users to open a specific in-app location (e.g., a product page) directly from a URL in a browser, push notification, or another app.
Question 7: What is 'feature flagging' and how does it benefit UX teams?
- A technique to enable or disable features for specific user segments without redeploying code (Correct answer)
- A method to mark UI bugs for developer review
- A way to hide deprecated features in the settings menu
- A process for flagging accessibility violations in production
Correct answer: A technique to enable or disable features for specific user segments without redeploying code
Feature flags let teams roll out new UX changes to a subset of users for A/B testing or gradual releases, reducing risk and enabling data-driven decisions.
When designing for touch interfaces, what is the recommended minimum touch target size according to most platform guidelines?