This repository is currently being migrated. It's locked while the migration is in progress.
Conditionally revealed fields #6010
babsdenney
started this conversation in
Radio button
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The VADS has guidance in the patterns section on using conditionally revealed fields. We want to explore this further and see how teams are using this pattern, and whether there are any knowledge gaps or assets that would benefit teams. Can you share your use cases?
Here are some questions to spur discussions and conversations. Please feel free to share any thoughts, ideas, or use cases you have around conditionally revealed fields.
Q1: In what scenarios do you typically use conditionally revealed fields?
Q2: How do you decide when a field should be conditionally revealed versus part of the form flow?
Q3: Can you share a specific example of conditional fields?
Q4: Have you encountered situations where conditionally revealed fields caused confusion or usability issues?
What happened, and how did you address it?
Q5: How do you ensure users understand why additional fields appear or disappear?
Do you use microcopy, animations, or other cues?
Q6: How do conditionally revealed fields impact form completion time or error rates in your experience?
Have you observed any measurable effects?
Q7: When collaborating with engineers, what challenges come up with implementing conditional logic?
Any common pitfalls or things that help streamline the process?
Q8: If you could improve our current guidance on conditionally revealed fields, what would you add or change?
What’s missing or unclear today?
Beta Was this translation helpful? Give feedback.
All reactions