Difference between revisions of "Projects/Usability/HIG/SOU Workspace/Buttons"

Jump to: navigation, search
(HIG moved to community)
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
A button initiates an action when the user clicks it.
{{ Moved To Community | KDE_Visual_Design_Group/HIG/SOU Workspace/Buttons }}
* Label all text buttons with imperative verbs, using [[title capitalization]]. 
* If an action requires additional input from the user before it can be carried out, use an [[ellipsis]] (for example, Save As...).
* Format all buttons in a consistent way in a dialog. Keep all buttons the same height and do not use more than two different widths.
* Make invalid buttons insensitive (using visual feedback such as grayed-out text and no hover over affect), rather than popping up an error message when the user clicks them.
* Indicate that a button is active with a hover over affect [open office uses a  slight background color change, dark line top and bottom – THIS IS UP FOR DEBATE]
* If a task offers multiple actions with one button set as default; indicate the default action with a highlighted line around the button.
* After pressing a button, the user should expect to see the result of their action within 1 second.
* Do not assign actions to double-clicking or right-clicking a button. Users are unlikely to discover these actions, and if they do, it will distort their expectations of other buttons.

Latest revision as of 11:26, 4 August 2016

This page is now on the community wiki.

This page was last edited on 4 August 2016, at 11:26. Content is available under Creative Commons License SA 4.0 unless otherwise noted.