Difference between revisions of "Projects/Usability/HIG/Tooltip"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Purpose)
m (Language correction)
 
(3 intermediate revisions by 2 users not shown)
Line 7: Line 7:
  
 
== Guidelines ==
 
== Guidelines ==
 +
 +
=== Is this the right control ===
 
* Use tips to label unlabeled controls and to provide additional information.  
 
* Use tips to label unlabeled controls and to provide additional information.  
 
* Don’t use tips for warnings.
 
* Don’t use tips for warnings.
 +
 +
=== Behavior ===
 
* Keep tips brief, typically five words or less for tool-tips; whenever appropriate, provide keyboard short-cuts and default values.  
 
* Keep tips brief, typically five words or less for tool-tips; whenever appropriate, provide keyboard short-cuts and default values.  
 +
* If the control is disabled, add a short explanation about the reason to the tip. If a control already has a tooltip when it’s enabled, write the reason in brackets behind the usual tooltip when it’s disabled. For instance: 'Go to the next unread message' in case of enabled controls and 'Go to the next unread message (No unread messages left)' when disabled.
 +
* Consider to add small info buttons for using tips with a touch screen.
 +
 +
=== Appearance ===
 
* Format tool-tips to make their content easier to read and scan by grouping and aligning the content. The information should be:
 
* Format tool-tips to make their content easier to read and scan by grouping and aligning the content. The information should be:
 
** concise: large, unformatted blocks of text are difficult to read and overwhelming
 
** concise: large, unformatted blocks of text are difficult to read and overwhelming
** helpful: it shouldn't be obvious or just repeat what is already on the screen)
+
** helpful: it shouldn't be obvious or just repeat what is already on the screen
** supplemental: important information should be communicated using self-explanatory control labels or in-place supplemental text)
+
** supplemental: important information should be communicated using self-explanatory control labels or in-place supplemental text
** (in discussion) <font color="blue">static: tips should not change from one instance to the next)</font>
+
** static: tips should not change from one instance to the next
* (in discussion) <font color="blue">If the control is disabled, add a short explanation about the reason to the tip. Do not add information beyond that.</font>
+
* Consider to add small info buttons for use tips with a touch screen.
+
(in discussion) <font color="blue">
+
 
* Do not use icons and formattings for tips of unlabeled controls.
 
* Do not use icons and formattings for tips of unlabeled controls.
 
* Use tool-tips with icons and formattings
 
* Use tool-tips with icons and formattings
Line 23: Line 28:
 
** when content is lengthy and formatting improves readability
 
** when content is lengthy and formatting improves readability
 
** for tips that are implemented primarily for joy of use.
 
** for tips that are implemented primarily for joy of use.
</font>
 
  
 
== Implementation ==
 
== Implementation ==
  
[http://qt-project.org/doc/qt-4.8/qtooltip.html QToolTip]
+
{{qt|QToolTip}}
 +
 
 +
[[Category:Usability]][[Category:Behavior]][[Category:User_Assistance]][[Category:User-driven_assistance]]

Latest revision as of 22:04, 2 December 2013


[edit] Purpose

A tool-tip is a small pop-up window that labels the unlabeled control being pointed to, such as toolbar controls without caption or command buttons. Tool-tips may as well provide more descriptive text including formatting and icons. Tips are a form of progressive disclosure, eliminating the need always to have descriptive text on the screen. Especially novice users are reluctant to click things if they are unsure what they do, so hovering feels more "safe". This time-delay mechanism makes tips very convenient, but it also reduces their discoverability. When tips are used consistently they support user’s expectation and foster predictability.

[edit] Examples

[edit] Guidelines

[edit] Is this the right control

  • Use tips to label unlabeled controls and to provide additional information.
  • Don’t use tips for warnings.

[edit] Behavior

  • Keep tips brief, typically five words or less for tool-tips; whenever appropriate, provide keyboard short-cuts and default values.
  • If the control is disabled, add a short explanation about the reason to the tip. If a control already has a tooltip when it’s enabled, write the reason in brackets behind the usual tooltip when it’s disabled. For instance: 'Go to the next unread message' in case of enabled controls and 'Go to the next unread message (No unread messages left)' when disabled.
  • Consider to add small info buttons for using tips with a touch screen.

[edit] Appearance

  • Format tool-tips to make their content easier to read and scan by grouping and aligning the content. The information should be:
    • concise: large, unformatted blocks of text are difficult to read and overwhelming
    • helpful: it shouldn't be obvious or just repeat what is already on the screen
    • supplemental: important information should be communicated using self-explanatory control labels or in-place supplemental text
    • static: tips should not change from one instance to the next
  • Do not use icons and formattings for tips of unlabeled controls.
  • Use tool-tips with icons and formattings
    • if tips describe comprehensive functions,
    • when content is lengthy and formatting improves readability
    • for tips that are implemented primarily for joy of use.

[edit] Implementation

QToolTip


This page was last modified on 2 December 2013, at 22:04. This page has been accessed 1,025 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal