Tagged ‘forms’

3 common examples of button text that degrades UX and how to rewrite them so they’re clear

7 reasons to replace advanced search with filters so users can easily find what they need

3 questions to evaluate design patterns and avoid unnecessary work that degrades UX

The problem with disabling paste and what to do instead

The problem with input masks and what to do instead

4 common mistakes UI/UX designers make when trying to help users spot required form fields (and what user research shows is better)

The problem with automatically focusing the first input and what to do instead

The problem with nested fieldsets and how to avoid them

The billion dollar unsubscribe link

The problem with disabled buttons and what to do instead

Designing a time input

Material Design text fields are badly designed

Stopping Chrome from ignoring autocomplete=off

Pressing back after deleting something

Form design: multiple inputs versus one input

Building an accessible autocomplete control

Form design patterns webinar, course update, January resolutions

Where to put buttons on forms

The problem with tooltips and what to do instead

Form design: from zero to hero all in one blog post

Defining graceful degradation, Patterns Day, journey mapping, question protocol mapping

Prototype kit extensions, small checkboxes and radio buttons, multi-select autocomplete

Semantic HTML, design crits, GOV.UK form components in Angular, pattern sharing

Angular forms, hiding elements, boring development, responsive design mindsets

Form builders, design system thoughts, new design system components

Defining interaction design, scoping a rich text editor component, links inside SPAs, fudgability

How to avoid optional form fields with branching questions

Form design: when to use the number input

Buttons shouldn't have a hand cursor part 2

But sometimes buttons look like links

The problem with live validation and what to do instead

The problem with float labels and what to do instead

Buttons shouldn't have a hand cursor

Always use a label

The problem with placeholders and what to do instead

Embracing simplicity

The hidden cost of one bad design

Select boxes shouldn’t submit on change

Forms with multiple submit buttons are problematic