{"id":67,"date":"2014-10-19T22:59:30","date_gmt":"2014-10-20T02:59:30","guid":{"rendered":"http:\/\/expectedly.org\/inclusivetech\/?p=67"},"modified":"2014-12-23T08:10:39","modified_gmt":"2014-12-23T13:10:39","slug":"gender-options","status":"publish","type":"post","link":"https:\/\/expectedly.org\/inclusivetech\/gender-options\/","title":{"rendered":"Dealing with gender on websites"},"content":{"rendered":"

The best solution is actually the simplest: just avoid requiring your users to pick a gender,\u00a0<\/em>either by omitting gender as a field or making it optional rather than required. But if you want to include a user’s gender as an option, the most inclusive way of handling it would be to allow genders other than the binary ‘male’ and ‘female’ options, even if it’s just ‘other’. Sarah Dopp has written a very helpful guide<\/a> for developers that can help them create more inclusive gender selectors. You can also use the SGOSelect menu<\/a> as a model for creating gender-inclusive dropdown menus.<\/p>\n

Some popular websites like Tumblr don\u2019t even ask for a gender, which hasn\u2019t had a negative impact on the popularity of the site. Older websites, however, like Yahoo and AIM, still demand that you should choose from two binary options, with no ‘decline to state’, ‘other’ or write-in options to choose from. Forcing people to choose a binary gender can be alienating or offensive, especially to people who don’t identify with the gender binary or see themselves as being gender-fluid. It can also be a violation of privacy; many women prefer not to identify themselves as women online because of the potential for sexist bullying and sexual harassment. (And if you’re forcing people to choose a gender because of advertising, you may just be displaying things based on gender stereotypes, a problem Sarah Dopp has also mentioned in her article – ‘not every woman likes baking, and not every man likes cars’. There are men who collect dolls and women who restore classic cars. Single fathers who wouldn’t mind having diapers\/nappies advertised to them, but childfree butch women who would. People are complicated<\/em>.)<\/p>\n

If you do include a gender selector, there is no need to restrict it to \u2018male\u2019 and \u2018female\u2019. It\u2019s becoming increasingly common for web services – even advertising- and data-driven ones like Google – that require a gender to be selected to choose a neutral option. Google services offer the \u2018other\u2019 gender option, which isn\u2019t perfect, but it\u2019s still better than having to choose from the binary options. Facebook introduced a variety of non-binary gender options in 2014 on their English-language sites (both US and UK). Livejournal and Dreamwidth offer \u2018other\u2019 or \u2018unspecified\u2019 options. Flickr has offered \u2018decline to say\u2019 and \u2018other\u2019 options for years, though their parent company, Yahoo, has never included an \u2018other\u2019 gender option.<\/p>\n

And whatever you do, don\u2019t<\/em> call your gender selector a \u2018sex\u2019 selector.<\/p>\n","protected":false},"excerpt":{"rendered":"

The best solution is actually the simplest: just avoid requiring your users to pick a gender,\u00a0either by omitting gender as a field or making it optional rather than required. But if you want to include a user’s gender as an option, the most inclusive way of handling it would be to allow genders other than… Continue reading Dealing with gender on websites<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/67"}],"collection":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":2,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":116,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/posts\/67\/revisions\/116"}],"wp:attachment":[{"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/expectedly.org\/inclusivetech\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}