Patterns: Create a user profile

Pronouns

Help users to provide their pronouns to ensure they are addressed in the manner they prefer.

The pronouns pattern helps users to provide information that will allow them to feel confident they will be addressed with the pronouns they use.

About this pattern

What problem does this solve?

A person’s name or sex are not indicative of the pronouns they use. Allowing users to specify their pronouns creates a more comfortable environment by removing the potential for frustration and alienation.

When to use this pattern

Follow this pattern when you are planning on referring to the person using pronouns instead of their name.

What’s the solution?

Provide a text entry field that supports a rich array of special characters and accents that allows the user to inform you of their pronouns. This pattern best supports verbal communication. This pattern is not appropriate for automated communication.

Guidance

What to do

  • Do understand why you are collecting this information.
  • Do provide examples and clear hint text. Many people may not be familiar with the concept of specifying pronouns.
  • Do provide an open text field. Language is evolving and forced choice can make a user feel as though they need to fit themselves into a label determined by the form designer.
  • Do support a rich array of diacritics, accents, and alternative characters.
  • Allow users to enter hyphens, apostrophes, and blank spaces in each field.
  • Do allow both upper and lowercase letters throughout each field.
  • Do support long text fields. Allow users to enter up to 128 characters per field, but follow form norms for field display size.
  • Do be prepared for a complex answer.
  • Do allow users to opt out of answering with a "Prefer not to answer" option.

What not to do

  • Do not make the field mandatory. While the information can be helpful, there are neutral options that can be used.
  • Do not assume pronouns. If a user chooses not to answer, use inclusive language like “they” or “you” instead of “he” or “she.”
  • Do not overwhelm the user with options. Default to a text entry field to allow user-provided pronouns.

For example, he, she, they, ze, he/they

<label class="usa-label" for="select-pronouns">Pronouns</label>
<div class="usa-hint" id="pronounHint">For example, he, she, they, ze, he/they</div>
<input class="usa-input usa-input--xl" id="select-pronouns" name="select-pronouns" aria-describedby="pronounHint">
<div class="usa-checkbox">
  <input class="usa-checkbox__input" id="prefer-not-to-answer" type="checkbox" name="prefer-not-to-answer"
    value="prefer-not-to-answer" />
  <label class="usa-checkbox__label" for="prefer-not-to-answer">Prefer not to share my pronouns</label>
</div>
<label class="usa-label" for="select-pronouns">Pronouns</label>
<div class="usa-hint" id="pronounHint">For example, he, she, they, ze, he/they</div>
<input class="usa-input usa-input--xl" id="select-pronouns" name="select-pronouns" aria-describedby="pronounHint">
<div class="usa-checkbox">
  <input class="usa-checkbox__input" id="prefer-not-to-answer" type="checkbox" name="prefer-not-to-answer"
    value="prefer-not-to-answer" />
  <label class="usa-checkbox__label" for="prefer-not-to-answer">Prefer not to share my pronouns</label>
</div>

Considerations

  • Confirm you need this information. As with all personal information, consider whether you need to collect it at all. Clearly explain the reason for asking for the information and what will be done to secure the user’s privacy.
  • If you don’t need a controlled vocabulary. Strongly consider allowing for user-provided pronouns with an open-ended text field. Users should also have the ability to opt out of providing this information.

Usability guidance

  • Provide clear hint text. Some users may be unfamiliar with this question and unsure how to answer. Provide clear hint text, such as, “For example, he, she, they, ze, he/they.” Do allow users to opt out with a “Prefer not to answer” option.

Accessibility

References

Disclaimer

Links to nongovernment sources are made for educational or source citation purposes only, and do not represent an endorsement of the organizations by the General Services Administration. The General Services Administration does not assume any responsibility for the content, operation, or policies of other entities’ websites.

Latest updates

Meaningful code and guidance updates are listed in the following table:

Date USWDS version Affects Breaking Description
2024-03-11 N/A
No

Replaced dead hyperlink with archived copy. Replaced reference to practicemakesprogress.org with plain text and a link to the archived page on archive.org. More information: uswds-site#2478

2022-11-14 3.3.0
  • Guidance
 No

Pattern published.