Overview

Summary of article…

General Principles

Overall advice, e.g.:

The language we use around gender, identity, orientation, and related concepts is rapidly evolving. These are sensitive and personal topics, around which there are strong feelings — and different, strongly felt opinions around language usage, even among thoughtful, well-meaning people.

For scholarship programs that serve the LGBTQ+ community, or those programs that simply want to ensure the LGBTQ+ community is well-represented in the students they support, this can present a challenge. When should a scholarship program ask for LGBTQ+ information? How does an application designer label the input fields when the label itself could cause offense?

This article suggests some general principles and provides a few specific examples of application form structure that adhere to the principles. These principles were collected from community input, academic studies, and feedback from students in the LGBTQ+ community using application systems designed by NSPA Members. With an evolving and sensitive topic like this, we’re sure these usage guidelines will change. But, the following represents our latest recommendations.

General Principles

Consider the following general principles when designing an application:

• Don’t ask for gender detail or LGBTQ+ specifics unless the information will be used. Consider not asking.

• Never “required.”

• “Prefer not to answer”

• “Gender assigned at birth…” by default

  • If “current” gender is intended for some reason, suggest adding “prefer to self-identify” and “prefer not to answer”

• Avoid “other…”

• Self-identification…

Application Examples

Option 1. Minimalist

• Gender M/F, define gender as “assigned at birth”

Option 2. Minimalist with Options

• Gender M/F, Prefer to Self-Identify

Option 3. General Approach to Inclusivity

• Gender M/F, LGBTQ+ options + self-identify

Option 4. Specific Audiences

• LGBTQ+, plus self-identify, plus “description”

References

• Articles, Wikipedia, etc.