Skip to main content
UX Design Engineering
Settings

Settings

Theme
Text size
100%
Typeface

Chapter 4

Making visual and interaction decisions

Use hierarchy, content, state models, and accessibility to help people understand eligibility and recover from assignment failures.

The first design puts an Assign button in every row and an eligibility explanation in a tooltip. It looks tidy in a screenshot. During review, the team asks how someone using a touch screen or keyboard will discover why a case is unavailable. Another reviewer asks whether eligibility can change while the administrator is choosing a team.

The decision is how the interface should communicate what people can do and what has happened. Visual order and behavior need to answer the same task questions.

Put the next decision in the hierarchy

For Casework, the administrator needs to identify the case, understand its current status, choose an appropriate specialist team, and confirm the outcome. Give those facts visual priority. A decorative summary chart may be attractive, but it competes for attention unless it helps this task.

Compare two treatments. One uses a small colored dot beside each case with a hover explanation. Another places a short status and reason near the assignment action. The second takes more space, but it exposes information needed to choose an action. A responsive design can move that explanation below the case title instead of compressing it until it is unreadable.

Use typography and spacing to distinguish case identity, eligibility, and supplementary details. Color can reinforce status, while visible text communicates its meaning. Review with long case titles and enlarged text; a compact arrangement should not rely on truncating the deciding information.

Write content around the action and the outcome

“Something went wrong” gives the administrator little help. “This case was closed before your assignment was saved” explains a known result and why the action failed. “We could not confirm whether your assignment was saved” describes a different situation that requires checking the service before attempting another write.

Only use the specific explanation when the service supports it. If you know merely that the request was rejected, explain that and provide a useful next step. Do not invent a business reason to make the message sound complete.

SituationInformation to communicateUseful next action
Case is closed when loadedAssignment is unavailable because the case is closedContinue to another case or use the established reopening workflow
Case closes during editingThe assignment was rejected and the latest status differsReview the updated case
Permission is revokedThe service did not allow the assignmentCheck access through the established support route
Response is lostThe outcome is not confirmedCheck the latest recorded assignment
Assignment is confirmedWhich case was assigned to which teamContinue with the next task

Model the states before polishing them

Write the relevant states and the events that connect them. In the worked flow, loading leads to an available or unavailable case. An administrator chooses a team and submits. Submission leads to confirmed success, a known rejection, or an uncertain outcome. Checking the latest case can resolve uncertainty or fail again.

For each state, answer four practical questions: what information is visible, which actions are available, where focus remains or moves, and what assistive technology should announce. A disabled save button alone does not explain why the action is unavailable. Include the reason in readable text near the form.

During submission, preserve the selected team and prevent another write. After an ordinary network failure, keeping a user’s choice avoids forcing them to repeat work. After a confirmed save, display the recorded team so the interface does not leave them guessing.

Review the whole interaction

Use native labels and controls where they fit. A specialist-team selector should have a persistent label. Associate supporting instructions or errors with the field when relevant. A status region can announce progress or confirmation without moving focus on every update. Use an error announcement deliberately; repeatedly announcing the same message can make the interface harder to use.

Test the reading order and focus order when the layout changes. Do not hide essential controls inside an interaction that only appears on hover. If a modal is genuinely needed, define its focus and dismissal behavior; a simple inline assignment form avoids adding that complexity to this case.

Accessibility checks examine part of the experience. They do not prove that the specialist labels match an administrator’s mental model. That question needs task evaluation with people familiar with the work.

Practice: compare two complete designs

Make two interface alternatives using the same case data. Include the unavailable, submitting, rejected, uncertain, and successful states. For each alternative, explain the hierarchy, content, responsive behavior, and recovery path.

Review them with a keyboard and enlarged text. Ask a peer to identify the current case, whether assignment is possible, and what happens after a lost response. Record observed problems separately from your proposed fixes. Change the behavior model before making another polished mockup.

Review your work

You should be able to explain how the design supports the task without referring only to appearance. Essential reasons remain available across input methods and screen sizes. Messages distinguish known rejection from unknown outcome. The state model identifies a recovery action and focus behavior for each consequential failure.

Use accessibility-driven interaction for the underlying browser techniques. The next chapter tests whether this approach resolves the intended uncertainty.

Found an error? Report it.