# Design exercise: UX & Interface Design

> User goals, information architecture, interaction states, feedback, accessibility, usability testing, and design systems. Implement designOutline() returning non-empty values for: userGoal, interactionStates, accessibility. Each value must name a concrete mechanism or decision.

Canonical: https://learn.significanthobbies.com/curriculum/drills/practice-ux-interface-design

User goals, information architecture, interaction states, feedback, accessibility, usability testing, and design systems. Implement designOutline() returning non-empty values for: userGoal, interactionStates, accessibility. Each value must name a concrete mechanism or decision.

## The mechanism

An interface is a state machine for human intent. Make the next action clear, expose system status, prevent errors, support recovery, and test with real tasks.

## Expected evidence

A design outline with userGoal, interactionStates, accessibility plus an explicit failure mode or trade-off.

## Hints

- Name the failure mode before selecting the mechanism.

## Sources and practice

- [W3C Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/)
- [Study UX & Interface Design](https://learn.significanthobbies.com/curriculum/concepts/ux-interface-design)
- [Try the interactive drill](https://learn.significanthobbies.com/drills/practice-ux-interface-design)
- [All practice briefs](https://learn.significanthobbies.com/curriculum/drills/)