Search results
Results from the WOW.Com Content Network
3. Forms made by and for the government that concern an individual or family/household often – usually in one of the first questions – ask for the family/relationship status of the applicant. The predefined answers reflect legal statuses for tax and subsidy purposes. In Germany, for instance, there are these categories:
3. I'm revising a web form which has a 'relationship' drop-down, e.g. mother, father, sister, brother, aunt, uncle etc etc. There are currently around 20 relationship options, ordered seemingly at random. It's difficult for users to quickly find the relationship they're looking for. At the very least I'd like to follow a web standard.
Have you ever make a survey question with answers like. Yes, with coke. Yes, with beer. No. With this kind of choices within a form, should you add a period after the answer? Or just leave it like above? forms.
Very nice approach. But not always possible consider a money transfer form in an internet bank web site. The user enters an amount, which is valid in the format we show him an smile but logically the number is not correct as he does not have the amount in his account or lots of other business rules.
On the main page they have 2 options "Accept" or "Delay" (shown below). 90% of the time the users will press "Accept", however, occasionally they will need to press "Delay". The "Delay" button has more than 1 status (e.g. delay by x,y,z amount of time). When they tap on the "Delay" button to select a status they are faced with a modal dialog ...
Chicken or fish is a boolean in the airline situation; you have to pick a meal. It doesn't matter if your boolean uses 0/1, yes/no, fish/chicken, or whatever 2 terms. Phrasing it as yes/no implies (unnecessary) limits to the end user, as does calling it a tickbox. All that matters is it's a binary choice.
2. In a Web form I have a question to which an answer needs to exist, so that a result can be shown to the user. It's about the users family status (single, family). Because there is a majority of users that prefer the first option "single" we decided to prepopulate that option. Should this still be marked as a mandatory field (*), though the ...
5. We have a UI on a web-page, where relationships between users can be defined by admins. Users are divided to two roles, in this case "Lorem" and "Lorem ipsum". Right now a relationship between two users can be chosen from 3 options: - no relation - with notif - without notif. Our current solution was designed for maximum 25 users, the "Lorem ...
3. There's two important things to keep in mind when approaching gender inclusivity: The terms "male" and "female" refer to sex, not gender. Sex and gender are two different things. Gender isn't binary. There's not just two options. Many people identify as non-binary, trans, or something else.
Still users can assume that disabled (inactive) state could become active and they may wonder if they need to perform an action to make them active. What is good actually in this case. I use special column for displaying active and inactive state. Row with checked green circles indicate active state, and those with empty cells indicate inactive.