Use a more precise required/optional fields legend #4719
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References
Background
Usability tests showed some users were struggling when seeing the word "Required" as a legend (it's actually styled as a title), since this isn't a common pattern when filling in forms. They were expecting something like "Fields with * are required", and so the "Required" text alone made them feel the sentence wasn't complete.
We could also add an "*" to required fields in addition to the "Required" text. In this case, however, some users wondered what the asterisk was about: "It can't mean 'required' because they've already said these fields are required".
Objectives
Visual Changes
Before these changes
After these changes
Notes
We'll probably have to revisit required and optional fields again. For now, we're just doing a small improvement.