Difference between revisions of "KDE Visual Design Group/HIG/StaticText"

m (1 revision imported)
(Move notice)
Line 1: Line 1:
== Purpose ==
Users tend to read only interactive control labels, especially those that appear relevant to completing the task at hand. By contrast, users read ''static text'' when they think they need to.
== Guidelines ==
{{Note|This page is now on [[https://hig.kde.org/style/writing/static.html https://hig.kde.org/]]}}
* Use the inverted pyramid for text. Start with the the conclusion and the fundamental "takeaway" that readers must have. Then fill in progressively more detail that readers may be interested in - perhaps just to scan.
* Remove redundant text. Leave full text in main instructions and interactive controls, and remove any redundancy from the other places.
* Avoid large blocks of UI text by chunking text into shorter sentences and paragraphs or providing help links to useful, but not essential, information.
* Use bold font sparingly to draw attention to text users must read. A different font, e.g. bold or italic, can be used to attract attention when changes to UI design are not applicable or not efficient enough.
== Implementation ==
[[Category:Usability]][[Category: Presentation]][[Category:Text]]

Latest revision as of 19:02, 5 February 2019

This page is now on [https://hig.kde.org/]

This page was last edited on 5 February 2019, at 19:02. Content is available under Creative Commons License SA 4.0 unless otherwise noted.