Context matters, both for the designer and the user. If a shipping address is desired, ask for one with name. Give the user a textbox entry field. It is OK t

Context matters, both for the designer and the user. If a shipping address is desired, ask for one with name. Give the user a textbox entry field. It is OK to reduce a round-trip with client side checks for length and line count, etc; the server MUST perform final validation for correctness and MUST also indicate success or why failure. It is OK to ask the user for variations of their name for different contexts. How it should be displayed for legal reasons, how they'd prefer to see it, if there's a short name of any kind they'd like used for less formal settings. Please try to accommodate any valid form of input. Some users have touch-screen devices (mobile, tablet). Some have keyboard and mice, or speech dictation, braille (spelling?) or possibly devices you've never heard of before. Don't just default to dropdown boxes and sliders when alternatives like specified input type. https://html.spec.whatwg.org/multipage/input.html#the-min-and-max-attributes https://html.spec.whatwg.org/multipage/input.html#the-min-an... The client software should provide the end user the best suited widget for the requested type.