Sex, gender, and pronoun fields in forms
NOTE: I made a good faith effort to research this topic and document my sources as well as what I learned. However, this is an evolving topic and thus aspects of this article may expire at any time. Happy to accept referenced corrections.
My research
Have you started using “Sex”, “Gender”, and “Pronoun” field in your forms? Can you define each, relative the other? What was the outcome when you explain the need to stakeholders?
While working on a new internal call-centre case management product for an insurance entity here in Australia, I noticed different aspects of the product using fields labelled either “Sex” or “Gender” when in-fact they populate the same record in a database. This lack of consistency, along with the topic of pronouns popping up more frequently in everyday life, I decided to try to better understand what these mean in today’s world. Here’s what I learned…
Understanding each as they relate to one another
Well, I was wrong. I thought the original field, labelled as “Gender” or “Sex” interchangeably in forms, were more appropriately labelled “Gender” and essentially one in the same. That may have been the case previously but not today.
In today’s evolving world with the growing list of ways one self-identifies and the introduction of which pronoun one prefers to be referred to, that presumption no longer fits.
In-fact, “Sex” is now correct and “Gender” is the additional field. Here’s a more detailed outline of each and how they should be used:
Sex
Description: Assigned sex at birth and listed on one’s birth certificate.
Field’s question: “* What was your sex recorded at birth?” [Ref]
Options: “Male, Female, Another term” (Ability to type answer)
Input: Radio buttons with a text box to type the “Another term” selection
Justification: Typically needed for medical reasons, compliance, census, siloing research input, etc. Whatever the truth is for the information, be straightforward with users and state the reason. That will help reduce the chance of confusion, questions, concern, insult, etc.
Gender
Description: How one self-identifies but not one’s sexual orientation. It is about social and cultural differences in identity, expression and experience, as a man, a woman, or a non-binary person. Also referred to as “Gender identity”.
Field’s question: “* How do you describe your gender?” [Ref] or “* I identify my gender as:” [Ref]
Options: “Male, Female, Non-binary, Prefer not to answer, Another term” (Ability to type answer)
Input: Radio buttons with text box to type the “Another term” selection
Justification: Affords non-binary gender people the ability to feel included and addressed using identifying pronouns.
Again, be honest and explain the need for the information.
NOTE: With over 60 recognised genders and growing, there are too many to list and maintain, but a core list may be justified. That is something you’ll have to decide.
Pronouns
Description: How one prefers to be addressed.
Field’s question: “* Which pronouns do you prefer when you are addresses?” or “* What are your preferred gender pronouns?” [Ref]
Options: “He/him/his, She/her/hers, They/them/their, Neither”
Input: Radio buttons
Justification: Help reduce the chance of referring to someone inappropriately.
Salutations
If a list of salutations are provided, consider including “Mx”. Mx offers an option to non-binary people and those who do not wish to be referred to by their sex.
Sexual orientation
To add clarity to these fields, Sexual orientation is not likely a relevant field for most forms.
Description: The gender for which one feels sexual desire or attraction. It is not who the user is but instead about others one has a desire or attraction.
Field’s question: I have no suggestion.
Options: Likely radio buttons with an “Other” option, but uncertain.
Justification: I am uncertain but perhaps along the lines of dating profile.
Using fields in forms
Form’s continue to be the single most interactive element of most digital products. So much so, poorly designed forms may be turning users away and in search of a better or at least less onerous interaction in a competitor’s product.
When asking for this information, it is important for all users to understand why and how the information will be used. This understanding is important for different reasons which largely depend one user demographics, like age. Admittedly, this is a generalisation but older users may be confused or even be put-off with multiple questions, while younger users may be offended when they’re not given these options.
When adding the fields to a form, ask the “Sex” question immediately before “Gender” and then “Pronoun” while ensuring all are on the same page.
Use case
For the call-centre product that triggered this research, there exists specific needs for each field. Sex is needed for medical reasons, where as Gender is needed to help all callers’ feel included. Then Pronoun will reduce the chance of inadvertently causing additional stress for callers or agents by using the desired pronoun one wants to be addressed.
Only last month we completed the 2021 Australian Bureau of Statistics census here in Australia. There was a heavy push to change the usual question around one’s sex to include the “Gender” field by those it would most effect. In the end, the decision was made to include it but those desiring the change had to take an extra step to do so. Another interesting point is the option for “Male” or “Female” isn’t labelled at all. If interested, a detailed analysis of the 2021 Australian census was performed by PeakXD.
Inclusive design and justification
To optimise one’s user experience, the optimisation of forms’ is imperative they include all users. That is, the user who is indifferent to the fields, those living with a challenge (typically referred to as one living with an accessibility need), and those who feel they’re being left out by not allowing them to self-describe.
Understandably, there are plenty of products which don’t need the fields’ but may be beneficial to convey the corporate brand is aware and understanding of the needs of their audience. This may be for selfish reasons, like maximising revenue or to avoid creating user-detractors instead of user-advocates. This may be due to the only form on the product is a contact form and thus irrelevant.
