Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

We have an issue in our company right now where gay people are complaining that our forms are not "gay friendly" we have a wedding registry page where it says groom and bride but they want a different way of presenting it so that it would be acceptable by that demographic. Any good suggestions on how we handle this? (Hope no one gets offended, Its a legitimate question and were actually dealing with this right now)

Here is a screenshot of the form

alt text

share|improve this question
    
arrghhh...i hate yellow on web pages!!! make it stop!! –  RPM1984 Nov 25 '10 at 3:47
    
Fascinating question, though not really programming related. I'd probably have an option like 'Same sex marriage', which then changes the labels and marks the wedding appropriately (so any relevant considerations can be made later). –  Noon Silk Nov 25 '10 at 3:51
1  
+1 to close, this isn't really a programming question and the answer is really a matter of opinion. Surveying your users will yield a better answer than what people here will be able to give you. –  Darko Z Nov 25 '10 at 4:20
add comment

migrated from stackoverflow.com Nov 25 '10 at 21:28

This question came from our site for professional and enthusiast programmers.

4 Answers

up vote 4 down vote accepted

There's no real standard or perfect way of doing it. Some options:

  • First spouse
  • Second spouse

or

  • Party A
  • Party B

or

  • Partner A
  • Partner B

or

  • Bride/Groom
  • Bride/Groom
share|improve this answer
    
Mmmm, this might seem to work. Great idea! –  Raymund Nov 25 '10 at 3:58
add comment

Assuming that you can get consultation from the same people who are complaining, I think you'd be better off polling them for comment.

If I was going to make an arbitrary choice on how to do this, I suppose I'd add a same-sex checkbox which changd those labels to text boxes, and allow the applicants to decide their own labels. (instead of making any sort of "one size fits all" decision and filling in something 'alternative')

share|improve this answer
    
I'm in favor of the "First Spouse/Second Spouse" suggestion because "same sex" doesn't also take into account transgendered people. Not to mention that as an LGBT person myself, I wouldn't be impressed if I had to check a separate flag in a form or survey, making me feel like I'm not being treated as equally as other clients. In all my websites I've never forced users to disclose gender. –  Lotus Notes Nov 25 '10 at 22:28
add comment

Have Bride/Groom in a drop down in front of the 2 input fields for first & last name. Have the form default to the hetero configuration (i.e. one line has bride preselected and one line has groom preselected) so the majority of users (no slight on homosexual couples, it's just statistics) don't have to change the form

EDIT: Similiar to @Narveson's answer, but with bride/groom drop downs in front of the name inputs instead of "name of spouse"

EDIT EDIT: I guess its not even relevant whether a person is a bride or a groom for the purpose of the form, I don't imagine you do anything meaningful with the gender information?

share|improve this answer
    
It might not be relevant for the form, but it is for the app. When somebody wants to come in and look for the wedding where the groom's name is Smith, knowing that it's the groom eliminates half the possible matches. And then after the wedding you know that the bride is much more likely to have the groom's last name than vice-versa. –  Gabe Nov 25 '10 at 5:29
    
As @Lotus Notes points out, my solution doesn't help with trans users who don't identify as a bride or a groom. Rather than speak for the LGBT community myself, I would say the best bet would be some direct consultation with them. –  micmcg Feb 10 '11 at 1:08
add comment

Put the first and last name boxes on the same line. I would tell you to do this even if you were keeping the bride and groom terminology.

      Name of spouse: (first) [      ] (last) [     ]
Name of other spouse: (first) [      ] (last) [     ]

Even better, just use a single text box for each party's name. Who says everybody has a first name and a last name anyway? Adam and Eve didn't.

share|improve this answer
    
Since he will almost certainly want to enable people to search by groom's last name or bride's last name, he will need to know the last names separate from the first names. He will also probably want to have bride/groom labels. –  Gabe Nov 25 '10 at 5:33
    
"Adam and Eve didn't" -> yeah but they're fictional characters. I'm pretty sure everyone in modern civilisation has a first name and surname. If you need to keep first/last name separately for searching purposes, You're Doing It Wrong. –  DisgruntledGoat Nov 27 '10 at 17:01
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.