Gender Inclusivity Is More Than an “Other” Option
summary
Argues that forms should start with ask why before how not with design tweaks, cites League user testing showing people feel invalidated when options miss them, recommends asking sex for medical/legal cases, and warns against required gender fields. Describes a built quiz site shouldiaskforgender.com that returns No/Yes/Maybe plus resources, urges making gender optional, giving users edit access and propagation for name/email changes, and calls out banks and services that still force snail‑mail or phone workflows.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:15About Alex
- 2:27Online Forms
- 3:01Gender Frequently
- 4:21Disclaimer
- 4:40Advocate for your users
- 5:45Primer on words
- 6:08Gender and sex
- 9:21Other quick definitions
- 11:11Why does this matter
- 11:28UX Design
- 12:44User Testing
- 14:32Everyone battles unconscious bias
- 17:09Photo Upload
- 18:41We Dont Know What We Dont Know
- 20:06Why
- 25:01Should I Ask
- 25:18Avoid Asking for Gender
- 26:44Thinking Beyond the Form Field
- 27:07User Story
- 27:51Reducing Friction
- 32:48Legal Name Changes
- 34:27Paypal
- 35:23Personal Experience
- 37:26Summary
- 38:25More Questions
- 40:04Resources
related talks
42mWhy User Data is about more than Forms
21mWeb Forms: When Someone's Gender is Your Business
44mInclusive Form Inputs
16mHow to Include Inclusivity from the Earliest Stages of Designing a Service or App...
41mDesigning for Gender Equity
27mCreating Beautiful, Accessible, and User Friendly Forms
20mInclusive design as the new norm
43mBuilding a Design Culture for Inclusivity