Do you have any best practice on how to handle buttons with long label?
- truncate the label
- button in 2 lines and keep the width but might be ugly
- button in 2 lines, keep the width and have the space height for all button
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
A button should be a succinct action statement:
Add to cart
When the button verges on a sentence, there's likely room to optimize.
How scannable will these actions be for the user?
Is there a better way to organize the information?
Do you need to create subsections?
Let's work with your example (though I don't totally understand the context).
In this format, you could just as easily allow multiple selection to download all desired formats or provide a
Send by email option.
Are these user-defined titles or do you define these? If the former, you could put a length limit on the names a user may give. In general, people can't navigate deserts of text like that quickly.
If you provide them, shorten the titles to the important parts, and structure them by combining similar options and making their variants hierarchical objects indented under their radio button:
Try to reduce your number of UI elements and length of text as much as possible, it encourages scanning.
Not so much a design challenge as an information architecture and/or copy writing question.
I look at your original image and see at least a 2-node taxonomy flattened into one level. That's your prerogative, but it's also spawned this problem.
I would consider decoupling the file format and the associated options as the independent parameters that they are. Uliwitness has done a nice practical illustration of this. The CSV options should be a subset.