Patterns
Ask users for…
Gender
Use with caution: Candidate
Follow this pattern whenever you need to ask Veterans their gender.
Usage
When to use this pattern
- Don’t ask a user to provide information that VA already has. You should only ask users for race or ethnicity, sexual orientation, or gender identity when VA does not already have the user’s information or when VA’s last validation date pre-dates the most recent approved pattern.
- Only ask a user to provide information if it benefits the user experience. You should only ask a user for their race or ethnicity, sexual orientation, or gender identity if you can clearly explain how providing this information will benefit the user (not the VA) and the question is related to the larger action they are trying to perform.
- Only collect data when you can reinforce trust, transparency, and user choice. You must clarify their information will not be used for their medical treatment or benefits determinations and demonstrate how a user can change their race or ethnicity, sexual orientation, or gender identity and related privacy preferences in the VA.gov profile. If a user does not have and is not eligible to create a VA.gov profile, such as an unauthenticated users, then the data is not collected.
Note: Many forms are based off of paper forms with limited fields for gender. Work with your stakeholder to expand the fields.
Examples
How to design and build
How this pattern works
- Provide a way to opt-out of answering. An option labeled “Prefer not to answer” should be provided.
- These questions are optional. Clearly communicate that the information being collected is not required.
- Do not remove the user from the task at hand to communicate details about this data collection. Specific use descriptions, definitions, or other descriptive content must be brief and VA policy compliant with no need for a user to leave what they are doing.