Inclusive Form Inputs
summary
Claim: replace binary inputs with spectrums. Concrete work includes 12 interviews across gender spectra, prototypes that implement multi‑select + custom entry and rename the field to identity instead of sex/gender, and added preferred pronouns and name fields. Tests reveal legacy insurance systems sometimes force a legal sex value, so the design models both legal and social identity, explains why data is needed, and QA uses long and non‑Latin names to catch overflow. Prototypes iterate, some fail, but internal adoption and conversations increase.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:01Overview
- 4:12Agenda
- 4:45History of Forms
- 7:38Insurance
- 10:05Universal Form Design
- 14:57Insurance Forms
- 16:49Gender Identities
- 17:56Participants
- 19:07Companies Approach
- 19:28Gender
- 24:59Sex vs Gender
- 26:26Gender is performative
- 26:43How to ask for gender
- 27:42Facebook example
- 29:14The Trevor Project
- 31:41Form Fields
- 33:47Custom Fields
- 34:48Security Questions
- 36:02Summary
- 37:07Collecting more information
- 37:52Talk to people
- 38:06Test your inputs
- 38:26Why you need to know
- 39:14QA
related talks
46mGender Inclusivity Is More Than an “Other” Option
42mWhy User Data is about more than Forms
21mWeb Forms: When Someone's Gender is Your Business
32mHow We Do Identity Wrong
16mHow to Include Inclusivity from the Earliest Stages of Designing a Service or App...
51mDisability Inclusion Beyond Accessibility Standards
20mInclusive design as the new norm
24mEliminating Unconscious Biases in Technology Through...