I would recommend looking at how someone like gov.uk handle errors on their forms. Adam Silver has written a great book on form design.
Here is an example of a great form error pattern that is tried and tested by the team at gov.uk
I highly recommend this book: https://www.smashingmagazine.com/2018/10/...
I think your instincts are correct. A 36-question form in a narrow modal popup window could create a number of challenges:
What if the user accidentally clicks outside of the window and closes it?
Lengthy scrolling in a modal window is a poor experience.
What does this look like on mobile (if that's a consideration)?
Consistency is definitely one of the ...
It looks like you already have a good answer in your question.
I would suggest perhaps going with "Building Number" as your main label though. It's a very broad term and it's hard to imagine somebody living somewhere that you couldn't class as a building of some sort.
It's important to have the subtext you have suggested too...
House number, flat ...
Whether it is good or bad will depend exclusively on your specific scenario and user testing. However, this is a very common pattern, it's called Progressive Disclosure.
In general, Progressive Disclosure is a great tool to IMPROVE conversions. However, if users find a "surprise", they will probably abandon the flow.
IN short: go for it. But as ...
You should activate (or make visible) the mandatory password field only if the "yes" radiobutton in selected.
Otherwise you can make a step by step process in which, if the "yes" option is selected, the following page asks for a password creation.
First of all, I wasn't exactly sure what you meant by "user is required to fill in at least 5 select boxes". Judging from the image, I assumed they were optional.
Maybe simply separating each select box on a new row would make it
less daunting? However it will take up alot more vertical space and
the user could be exporting 10 different people or ...
If your business requires those fields as mandatory there are few things you can do. Maybe you can work to simplify the cognitive effort for the user. I tried a quick'n'dirty sketch. To me there is no need to put a title for each combo box. I would just put a combo box with the first line in it as explanatory.
The moment you click the sign up button, you should lose access to the "Already have an account? Login" button. You have two options when "Sign up" is clicked:
(1) Directly disable the login button (greyed out, default cursor, etc.) Very soon they will be taken to a confirmation page. Users are quite used to options being taken away ...
Agree with precious answer, you need to sort out the goals and user stories here.
One possibility is also to have a mix of your two option - start with Option B but have all the fields in A under an accordion named “add more details” or similar.
I tend to lean more towards the simpler form but this product isn't for me. It depends on your users and what they want to do with this information. If the end goal is to build a calendar day, then you might need more details. If it leans more towards a simple roster for the day then you could get away with the simple form.
It all depends on the user need that you are trying to satisfy. Is the product going to be used for scheduling/time management?
Is it going to help anyone if there is no time/location set?
Does the user use anything else for setting up meetings and this app that you are building serves another purpose ?
In order to make a good decision you should find out if ...
The “Delete” buttons need labels, so that the user who cannot see the locations knows what each button would delete.
Clicking the “Add new country” button inserts content into the page above the button. A blind user might not know that anything was inserted. So you would need to do something with the focus or a live region to ensure that the user is informed....
What's on the user's mind when they input the data? Is it a quick task and they just want to input the data and leave? Or is it that they'll sit there, look at the data of other combos/cells, and input their data based on the data in other cells?
A table view is great for complex data entry and manipulation. It's also great when users need to compare data. ...
I think you are close to two good options; in both options, you'll want to remove the "Delete" button next to the first dropdown (allowing the user to delete additional dropdowns, but not the first one.) You say that language isn't important, but you might want the Add button to be more like "Add additional country".
The version on the ...