ux-research 4 linked patterns checked
NN/g Marking Required Fields in Forms
Documents the need to mark required fields clearly in forms and explains why relying only on optional-field marking or top instructions can make form completion harder.
Read with a purpose
What this source can teach
Use this source to examine the study question, participants, observations, and limits before applying a finding.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Create user profile | Choose create user profile when the user is defining visible identity information that other people or public surfaces will see. | The form states which profile fields are required, optional, managed, hidden, or public before users save. | NN/g supports explicit required-field marking for forms with mixed required and optional fields. |
| Disabled controls without recovery | Flag this anti-pattern when a disabled control blocks a task and the surrounding UI does not provide a reachable next step. | Users can discover the cause of unavailability without activating or hovering the disabled control itself. | Required field guidance supports visible requirements instead of hidden eligibility rules. |
| Profile setup | Choose profile setup when an existing profile is usable but incomplete, stale, or missing recommended details that improve collaboration, discovery, trust, or public presentation. | Opening profile setup loads the current saved profile and clearly distinguishes already-complete, missing, recommended, optional, managed, and visibility-sensitive fields. | NN/g supports clearly communicating required and optional fields, relevant to profile setup with required versus recommended details. |
| Required field hidden by conditional logic | Flag this anti-pattern when a required field can block submit while it is hidden, collapsed, disabled, off-screen, absent from the current route, or disconnected from its trigger. | Selecting a trigger that creates a required follow-up reveals that follow-up immediately in logical DOM and visual order. | NN/g supports marking required fields clearly so users can predict what must be completed. |
Comparisons supported by this source
- Create user profile vs account creation vs onboarding vs single-page form
NN/g supports clear required-field marking, relevant to profile forms with mixed required and optional fields.
- Profile setup vs create user profile vs onboarding vs account creation
NN/g supports clear required-field marking when profile setup mixes required and optional fields.
- Required field hidden by conditional logic vs conditional reveal fields vs dependent fields vs error summary vs single-page form vs review before submit
NN/g supports clearly marking required fields before users submit.
Evidence Role
This source is treated as ux-research evidence. Its value comes from the specific claims and setting described above.
Publisher: Nielsen Norman Group. Last checked: .