I would like to add my vote for this request. Many organisations and governments are now mandated to provide these options.

Just remove the gender question-type. Depending on the cultural background you will be forced to have a different wording or options. There might be countries, where "Other" would raise trouble. So you would end up with a radio list anyway, which could need some improvement as well. A questions theme of different gender questiontype would still be possible, when using radio list question type.

I support Jelo.
Now having the bootstrap button option this question type is easily displayed with all needed answer options using the normal radio list question type.

I support jelo as well

For my organization, gender issues are very important. At least there should a third option like "inter / divers" or "other"

Judgment of the German Federal Constitutional Court on this topic:
https://www.bundesverfassungsgericht.de/SharedDocs/Pressemitteilungen/DE/2017/bvg17-095.html
https://www.bundesverfassungsgericht.de/SharedDocs/Entscheidungen/DE/2017/10/rs20171010_1bvr201916.html

German Law "Gesetz zur Änderung der in das Geburtenregister einzutragenden Angaben":
http://www.bgbl.de/xaver/bgbl/start.xav?startbk=Bundesanzeiger_BGBl&jumpTo=bgbl118s2635.pdf

"Much Ado about Nothing" (Shakespeare)
It is really, really not mandatory to use the "Gender" question type, when asking for gender.
Gender is a simple single punch question. So anybody can use a "list (radio)" with as many precoded answer options as desired and additionally an "Other" option.
Same as you would ask for religious denomination.

In my opinion these question types (Gender and Y/N) are obsolet and should be removed - supporting Jelo.
Some "special" array types as well like "array(Y/N)" and "array(Increase/Decrease)".

@gn1571, the code is quite old and everyone is afraid to touch it. Moreoever, people with different cultural backgrounds interpret the gender question differently. We always recommend our users to use a list (radio) question as a workaround since it gives you the possibility to edit the predefined answers and to add many other answer options (as mentioned above by other community members).

Its removal could prove to be an efficient solution though.

My opinion : lets' all question to be in plugin/theme/etc … with «options»
Then :

1. we can have different Gender question
2. specific system can create / update a new one
3. etc …

BUT : this need a complete rewrite of Question system with QuestionObject with

1. Answers list (here) and answer restriction (list,date, string, numeric …)
2. Core attribute allowed : mandatory, other …
3. Some base question included in core and that can not be deactivated (free text + single choice + multiple (free text + single choice) + array (free text + single choice))
4. See if this 2 one are ok for extending ( for example multiple question type is a multiple single choice (Y or N) ; numeric is a free text with restriction)
5. Create some other one : multiple date for example
6. See how to create some other (or do we need a new core Quetsion) : list with comment + multiple with comment
7. etc : even the moon is not so far …

@Denis: The decoupling of questions-types is the right direction. That was the promise (being able to create your own questionstypes) of the first LS2 (with the different PHP framework). Then the porting to Yii1 happened. Perhaps when Yii1 will reach EOL and the WYSIWYG mode is in beta, the refactoring will reach a new level. Or LimeSurvey will become EOL.

;)

Remove the gender question type. Convert the gender question to a single choice question.
Or allow it only for imported and existing surveys. No new questions with this question type.
Warning for EOL of this question type in the next version of LS.
Everybody can create their own gender question with more generic questions types.

What metric is used in "Users affected in %"?
How is that measured?

Agree with @Joffm and @cdorin. The general problem for "button question" is usually the button icon itself.
Sometimes yes/no don't fit with actual symbols. The same is for gender buttons.

I expect in the future they can be removed for a general "buttons" answers, having customizable icons. Today we can use UTF8 icons, maybe they can fit in the button's label.

✅❎
⭕❌
��

Just raising bug's heat �

@tassoman : with Button theme : you can add icon from Font awesome, no ?

Furthermore you can use all bootstrap 5 icons on bootstrap buttons or other UTF-8 icons

In my opinion all predefined question types like "arrays (5-point, 10-point, Yes/No/Uncertain, Increase/Same/Decrease)", "Yes/No", "Gender" are obsolete.
How often do we read in the forum "There is only a 5-point array, but I need 7 points". The generic type "array" is sufficient.

And since there are bootstrap buttons we do not need the two "button questions". Another advantage: I can use the codes I like.

a1.PNG (3,146 bytes)   

a1.PNG (3,146 bytes)   

a3.PNG (3,940 bytes)   

a3.PNG (3,940 bytes)   

Another advantage: I can use the codes I like.

Remind of A11Y here ;)