Request posted for translations: https://meta.wikimedia.org/wiki/Research_talk:Characterizing_Wikipedia_Reader_Behaviour/Demographics_and_Wikipedia_use_cases#Translations

Comment: The question about gender could/should be rephrased to be more incluse of non-binary genders IMO.

Comment: The question about gender could/should be rephrased to be more incluse of non-binary genders IMO.

@jhsoby-WMNO Yeah, we spent a good bit of time with this and thanks for raising the concern. The main issue I think is that you're not seeing the full question which also has a "Other" and open-text field (which in retrospect, I should have noted), but it's worth laying out the thinking all the same. The answers available on the survey are "Man, Woman, Prefer Not to Say, Other... w/ open-text". It's a not fully satisfying compromise but I think it's best given the constraints. We were trying to make sure it was inclusive but also had to conform to Google Forms and keep it simple enough that it could be translated easily across languages. A few thoughts:

• We use Man/Woman instead of Male/Female as we are asking about gender and not sex.
• "Prefer not to say" is included because we did not want anyone uncomfortable w/ providing this information to not be able to easily skip the question.
• The current guidance seems to be that "In another way" or "Prefer to self-describe" are the best ways to provide an open-text option. Unfortunately Google does not allow us to change the wording for their open-text response (Other) or we would choose one of those.
• We were concerned that adding more options like "Non-binary / Third-gender" would complicate translation and our ability to cross-compare the results from different languages.
• From the English pilot (~600 responses), we found that 3% chose not to say and 1% provided open-ended responses.

A few resources I've been relying on outside of conversations with others who think about these challenges:
HCI Guidelines for Gender Equity and Inclusivity: https://www.morgan-klaus.com/sigchi-gender-guidelines
Equality and Human Rights Commission: https://www.equalityhumanrights.com/sites/default/files/rr75_final.pdf
UX Collective: https://uxdesign.cc/designing-forms-for-gender-diversity-and-inclusion-d8194cf1f51

Good to hear! An "other" option would suffice I would say, so it's good that it's included.

Yes, thanks again for raising the concern. I had not been thinking about how much context I'd stripped in the translation doc, but it's heartening to know that people will say something when something appears off like that!

Current translation status

• Complete (translation + verification complete):
  • English
  • Norwegian (Bokmål)
  • Russian
  • Spanish
  • Arabic
  • German (still need to identify who will notify community)
• Translation complete; verification/walk-through needed:
  • Hebrew
  • Chinese
  • Romanian
• Waiting on translation
  • French
  • Hungarian
  • Ukrainian
  • Portuguese
  • Persian
• No volunteer identified -- possibly dropping
  • Japanese
  • Hindi
  • Indonesian

Privacy Policies

I need to provide Privacy w/ the translations in a Google doc and they will handle the upload. As each translation is completed, I make sure it is prepared for easy upload to foundation.wikimedia (lang code; appropriate credit to the volunteer; formatting/headings/text/links etc. ready for upload)

Interface Pages

T&S is helping me gain the necessary permissions for creating the Mediawiki namespace pages in each language for the survey widget text. Internal permissions granted. Waiting on support from stewards.

Deployment

I have been preparing the necessary configuration for each language. Currently we are aiming for either 1000 responses in each language (good statistical power for reporting basic demographic stats and some stratifications such as how gender and motivation interact) or 10,000 responses (can also compare countries and do subgroup discovery to examine correlations with reader session behavior such average article quality). For the Africa-specific surveys in English/French, we are aiming somewhere in between as a compromise between what we can achieve and having enough responses to do some country comparisons.

• 1000 responses: Norwegian, Arabic, Hebrew, Romanian, Persian, Chinese, Ukrainian, Portuguese, Hungarian
• 2000 responses: French (Africa)
• 5000 responses: English (Africa)
• 10000 responses: English (World), Russian, Spanish, German, French (World)

Updates:

• Hebrew and Romanian now complete.
• Preparation started for testing on beta wiki for english and hebrew (T225819)
• Still waiting on interface permissions -- I will send out a reminder to check on the status of that

@Isaac update on my end: I pinged fr, hu, pt, and uk point of contacts. I am also working on fa.

See T212444 for most recent status on translations. Currently Ukrainian, Portuguese, and Farsi pending verification. There likely is not time to include Polish, Hindi, Japanese, and Indonesian before the survey launch but they are under consideration for future rounds.

@Isaac: @Amirsara and I worked on the fa one and have it ready. Shall I go ahead and do the verification step myself?

@leila yes, that'd be great thanks!