In which we take a look at selection-dependent inputs, and see that they’re a lot more simple to put together than they look. Forms. They’re often the bane of users’ online lives. But it doesn’t look like they’re going away any time soon. So its up to us, UX designers, to make them as smooth and easy to use as possible for our users while still reaching the best business outcomes. If we prototype our forms, we can get them

Forms are important—they’re the most common way to get information from our users. But just making wireframes of a form misses a big piece of the picture—what it’s like to interact with it. An HTML prototype of a form, on the other hand, can look and behave just like the real thing. In the first post, I showed you how to lay out a form and align the labels the way you want, using HTML and Foundation. In the second

Forms are one of the most important parts of any site or app—they are the most common way for our users to give us the information that we need to help them do what they want to do. But in many instances, we design forms statically, often as wireframes. But so often, what makes or breaks a form is what it’s like to interact with it. When the user clicks on a particular radio button, some additional inputs appear. How