Page MenuHomePhabricator

Subtle gendered language flagging tool for Wikipedia articles (browser extension MVP)
Open, Needs TriagePublic

Description

Problem

Editors often rely on intuition to identify gendered or biased language, but research shows that terms like “female scientist”, “chairman”, or “manpower” persist in articles—even when they’re unnecessary or reinforce binary assumptions. While Wikipedia’s Manual of Style recommends gender-neutral phrasing, there's no lightweight tool to assist editors in spotting and reflecting on these patterns during the reading or drafting process.

Proposed Solution

Create a minimal browser extension (MVP) that passively scans the content of English Wikipedia articles for subtle gendered or outdated language patterns and flags them in a non-invasive UI.


Note: This is not a prescriptive tool. It offers context-aware prompts based on:

  1. Wikipedia Manual of Style – Gender-neutral language
  2. UN Gender-Inclusive Language Guidelines
  3. Widely used editorial references like the Chicago Manual of Style (non-binding)

Features (MVP Scope)

  • On-page scanner activated by button or auto-load
  • Flags common gendered terms (from curated list)
  • Offers inline notes or side-panel explanations (“Why this was flagged”)
  • Optional suggestions or questions to prompt reflection
  • No writing or editing capability; this is a reader-facing tool

Stretch Goals

  • Enable editors to submit new phrases or edge cases
  • Expand to multilingual support (start with EN, flag DE/FR/ES for future)
  • Respect quotation blocks, titles, and names via basic rule-based filtering
  • Track frequency of flagged terms for analytics (client-side only)

Why?

Equity doesn’t start with new articles. It starts with how we describe people in the ones that already exist. This tool helps reduce linguistic bias without adding workflow bloat or triggering manual review drama. It’s designed for editors who care about tone, power, and representation—but don’t always have time to do a line-level bias audit.

Sample Terms to Audit

https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=%22unmanned%22&format=json
https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch="female scientist"&format=json

Event Timeline

hey @Rockingpenny4, thanks for the interest! here’s what i’m working on (Subtext—flags subtle gendered language on English Wikipedia). super minimal MVP. if you’re all still down to help, pick something and just drop a message here.
if not, all good, no pressure.

  • JS DOM work: scan #mw-content-text, wrap flagged phrases
  • Term list help: 10–20 terms + 1-sentence tooltips (use MoS, UN guides)
  • Basic CSS: highlight .subtext-flag class (readable + Grammarly-inspired design)

i’ll keep it moving either way

I did a little work on a related-but-separate take on this, as an edit-check inside of VisualEditor that'd warn a user when they were about to use a gendered term in an edit they were making. https://meta.wikimedia.org/wiki/User:DLynch_(WMF)/EditCheckGenderedTerms.js

image.png (836×1 px, 236 KB)

I did a little work on a related-but-separate take on this, as an edit-check inside of VisualEditor that'd warn a user when they were about to use a gendered term in an edit they were making. https://meta.wikimedia.org/wiki/User:DLynch_(WMF)/EditCheckGenderedTerms.js

image.png (836×1 px, 236 KB)

Nice

I did a little work on a related-but-separate take on this, as an edit-check inside of VisualEditor that'd warn a user when they were about to use a gendered term in an edit they were making. https://meta.wikimedia.org/wiki/User:DLynch_(WMF)/EditCheckGenderedTerms.js

image.png (836×1 px, 236 KB)

Is it possible to have this as a standalone user script?

Also, the prompt feels a fair bit wordy, it might make sense to have a short description and have a learn more link/button somewhere in the GUI ?

We did work on this in the hackathon and created a chrome extension. However, everything is pretty much hard coded and we should probably find a more native solution and integrate with the visual editor itself. Scaling with NLP would be better as well to catch more gendered phrases if the ai team would like that. Here's the etherpad with the demo video and everything https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2025_Closing_Showcase

Is it possible to have this as a standalone user script?

That one actually works perfectly well as a userscript. Stick the following into your common.js (or your global.js on metawiki if you really want to):

// Turn on edit check regardless of your wiki's settings
mw.loader.load( 'https://meta.wikimedia.org/w/index.php?title=User:DLynch_(WMF)/alwaysbechecking.js&action=raw&ctype=text/javascript' );
// Stop edit check from being restricted to only a single Add Reference check regardless of your wiki's settings
mw.loader.load( 'https://meta.wikimedia.org/w/index.php?title=User:DLynch_(WMF)/alwaysbemultichecking.js&action=raw&ctype=text/javascript' );
// Register the gendered terms check
mw.loader.load( 'https://meta.wikimedia.org/w/index.php?title=User:DLynch_(WMF)/EditCheckGenderedTerms.js&action=raw&ctype=text/javascript' );

Agreed it's a bit wordy, though. Part of the issue is that edit checks are supposed, conceptually, to be education for new users who don't yet know policy, so some amount of explaining why we're asking them to do something is considered to be a good idea. Because I was hacking this together, I just copied a bit from the Manual of Style, which is verbose. Arguably I could remove all of that and just have this:

image.png (386×644 px, 31 KB)

I did a little work on a related-but-separate take on this, as an edit-check inside of VisualEditor that'd warn a user when they were about to use a gendered term in an edit they were making. https://meta.wikimedia.org/wiki/User:DLynch_(WMF)/EditCheckGenderedTerms.js

image.png (836×1 px, 236 KB)

Is it possible to have this as a standalone user script?

@Soda: might you be willing to share what prompted you to ask this question?

Reason I'm curious: the Editing Team (of which @DLynch is a member!) is planning to introduce a new range of Edit Checks that will operate like suggestions. Meaning: these would be Edit Checks that get shown on existing content, rather than being limited to edits people are in the midst of making. Holding these plans in mind with the question you asked caused me to think, "Hmm, I wonder if @Soda is thinking of using this script to help them identify gendered terms that are in need of cleanup."