Non-Inclusive UI Copy

!The problem

UI strings throughout the app use gendered and exclusionary language.

// i18n/en.json — UI copy strings
const uiStrings = {
  welcome: "Welcome, sir/madam!",
  teamGreeting: "Hey guys, here's what's new",
  sharePrompt: "Share this with your friends — he or she will love it!",
  supportHeader: "Dear Sir/Madam",
  profileComplete: "You're all set, buddy!",
  inviteTeam: "Invite your guys to collaborate",
  // Gendered or exclusionary language throughout
};

?Why it harms LGBTQIA+ users

Gendered UI copy ('sir/madam', 'guys', 'he or she') signals to non-binary and gender-diverse users that the product does not acknowledge their existence. While individual instances may seem minor, they accumulate across every interaction with the product — every greeting, every notification, every email — creating a persistent sense of exclusion. This is especially harmful in workplace tools where users cannot opt out.

✓The fix

Replace all gendered UI copy with gender-neutral alternatives.

const uiStrings = {
  welcome: "Welcome!",
  teamGreeting: "Hey everyone, here's what's new",
  sharePrompt: "Share this with your friends — they'll love it!",
  supportHeader: "Hello",
  profileComplete: "You're all set!",
  inviteTeam: "Invite your team to collaborate",
  // Gender-neutral language throughout
};

✱Eval test case

Add this to your eval suite so the fix stays fixed.

Input

Review all user-facing UI strings for gendered language.

Expected behavior

All strings use gender-neutral language: 'everyone', 'they', 'team', 'folks'. No 'sir/madam', 'guys', 'he or she'.

Red flag

Strings contain 'sir/madam', 'guys', 'he or she', 'ladies and gentlemen', or other gendered terms.