Hot answers tagged

176

There is not really a "UX" reason for this—or if there is, it is a very limited one. The actual reason why dialog backgrounds are (by default) some shade of grey is because some designers thought that looked better. In many early operating systems, dialog and window backgrounds were stark white. Obviously they were white on the original Mac OS, since it had ...


123

If the output is binary (success/fail, OK/NOK, whatever), why not only show a status on the failure state? timestamp | action name | description timestamp | action name | description timestamp | action name (FAILED) | description timestamp | action name | description Edit: Some comments to the original question have ...


51

Yes. The Oxford Comma increases readability. When items are logically separate, putting a delimiter between them makes their separation visually obvious. Without the delimiter, the separation can still be determined, but it is not obvious. The Oxford comma removes the requirement that the reader figure out whether item n and item n-1 are logically separate....


48

There is a better solution, at least in terms of legibility, perhaps not so much aesthetically. And I'm 99% sure you've already seen it. Black border, white letters. White letters are almost always brighter than the background, and the black outlines act as a sort of shadow, separating the text from the background. Of course, the best legibility is ...


44

You read as you approach. Theoretically. In reality, levels of visual acuity mean that some people (like you and I) can read the whole block at once. Another reason that painting information on the pavement isn't always ideal. Here's a good visual for how this is designed to function in practice: The trick is (as the image above shows) the spacing of ...


37

The book On Writing Well (a great book,) suggests making things like these plural. In the book, he talks about how to avoid the gender problem when talking about men/women. (By calling them people.) For example, when talking about a specific user, instead of saying "when he clicks on the button..." you'd say "when they click on the button...", or the passive ...


35

I'd say the best two options are: 1) Display terms and conditions as long plain legalese text as usual, in a left hand column, but then summarise it in much shorter, friendlier, simpler text on the right. 500px.com does this really well: 2) Format the text in a legible manner. Separate it into linked sections with proper headings, good typography and ...


35

What you need to examine is the use-case for these terms within the context of the project logbook. I have to guess here but I'd say the logbook is a project management tool - an aid to charting progress or discovering problems/blockers 'NOK' is not a commonly understood term. This means that anyone joining your team for reasons of scale, sickness cover, ...


35

Too much white can cause eye strain, so tints of grey reduce this. There is another ux.se topic which discusses white vs grey backgrounds: Grey versus white background for ease of use and readability/legibility


25

You could consider changing the wording of the values: download bmml source – Wireframes created with Balsamiq Mockups


24

I think the top-voted answer is only partially correct... The Oxford comma can resolve ambiguity OR create ambiguity, depending on context. This is the reason that grammar experts and style guides disagree on the use of the Oxford comma - sometimes the Oxford comma helps, sometimes it actually hurts readability. Consider the following examples... "I gave ...


22

In complete agreement with the other answers, but to provide an alternate viewpoint: If you were driving at night, your headlights will reveal the beginning of the sentence before the end.


22

It appears that the biggest problem is being able to find the status indicators within a large group of text. Barring some significant technical limitation, I would say your solution should be to display the status of each action in its own column. This makes your question of exact terminology much less important by Reducing the importance of terminology ...


21

Timestamps aren't meant for most users Showing friendly names such as 2 hours ago or yesterday can quickly provide context to the user as opposed to showing them 2015-01-27 18:54:03.259 Mixing both formats together will always cause friction (anything that forces a user to ask a question in their mind adds to cognitive friction). In almost all cases ...


20

I would say it has to do with the following reasons : Contrast : Studies have shown that black or dark backgrounds provide the easiest contrast and can allow users to read discrete information quickly without having to make an effort to discern details when in a dark environment (which is often the environment in cars) Darkness adaptive : Another reason ...


19

I don't deal in print, but I have read quite a bit about fonts in the past. Recent studies have shown that serif vs. sans serif on a computer display is not really what affects readability, even at lower resolutions. Print, however, is a different matter. The studies consistently indicate that in print, serif based fonts are easier to read. That said, some ...


19

There is no reason to force a user to read the terms and conditions first. It is not a legal requirement and it doesn't improve the UX. Don't do it. Legally they simply have to agree to the terms and conditions, and if they choose not to read them, then that is their problem. UX wise, what part of the experience are you trying to improve by doing this? ...


19

I feel like you have very different questions here. To answer your first question: is some research in regards to how font-weight affects readability? Yes, there is. First you have to understand that type/fonts are judged by their "readability" (how easily can words, sentences, and paragraphs be read by an average reader) and their "legibility" (how ...


19

Apart from the answer given, I would like to mention one very important Use Case where the solution is nothing BUT shadows. Text on an image When you don't have control over the image on top of which you are writing text, you have to ensure proper contrast for best readability. A Big hero Image seems to be rage these days. A dark shadow is added behind ...


18

Yes. Jakob Nielsen did a study many years ago and found that users like reading text that's easily scannable. Scanning can save users time. During the study, 15 participants always approached unfamiliar Web text by trying to scan it before reading it. Only 3 participants started reading text word by word, from the top of the page to the ...


18

For what it's worth - I tried a variety of timings myself and ended up at 3200ms for a two line message of up to about 20 words. But I also place a small dot (10px diameter) to the left, which is coloured according to message type (eg red/error, blue/info, orange/warning) and which fades out over the 3200ms. When the fade gets to 100%, the message itself ...


18

Readability is hard to get right Great question. It's always good to question the point at which style destroys function. Example scrim formats I've done quite a lot of user testing on scrim-based image captions (where there is a partial or complete semi-transparent overlay on the image and contrasting text). Here's what I've found, in no ...


18

Two things to think about: In computing, it's common to use failure instead of just fail, because it happens to be the same number of characters as 'success', so in mono-spaced fonts they end up being the same width. (Side note: "warning" is also the same number of characters) In addition to this, some systems (like Linux/Unix) color the words - failure is ...


17

Based on UX.Movement: Why Text in All Caps is Hard for Users to Read The reason of the worse readability of uppercase vs lowercase is the lower contrast of shape. Small caps still has worse contrast of shape than lower case, so it'll still be less readable. There is also some relationship with familiarity, taking into account that for sure more of the 90%...


16

Source - http://en.wikipedia.org/wiki/Decimal_mark In Albania, Belgium, Bosnia, Estonia, France, Finland, Hungary, Poland, Czech Republic, Slovakia and much of Latin Europe as well as French Canada: 1 234 567,89 (In Spain, in handwriting it is also common to use an upper comma: 1.234.567'89) In Brazil, Germany, Netherlands, Denmark, Italy, ...


16

Background color is convention. This (hidden) rule will be learned by user soon. But I also recommend to show tooltip when user tries to edit (clicks) read-only cell. Such explicit message prevents guessing or abusing on imaginary non-working functionality.


16

You have a few options in terms of referencing pages... QR Codes URL Shortener Using full URL Search No matter which method you choose to use, you have your pros and cons depending on your site's demographic. QR Codes Using a QR code is great for the younger, more tech-savvy, users. They usually carry smartphones with them and can easily scan your ...


16

Headers are essentially metadata and you need some way to indicate that they are separate from your content, but related to it. I would recommend against lowercase and normal weight text as it will make that row visually similar to the rest of the content. Title case is the most common, though you might be able to use small caps or uppercase headers. ...


16

Because the difference between the font-color and the background-color can cause eye strain and is not optimal. Having black or dark-grey text on a lighter grey background is the easiest for the human eye to read. See this link for a more detailed answer. It tells you when to use brighter fonts with a dark background, and also when not to do this. ...


15

How well a font displays on the web depends on how much hinting information it has had: http://en.wikipedia.org/wiki/Font_hinting Font hinting takes a tremendous amount of time to do as the font must be adjusted at each size. The reason Arial, Verdana and other older fonts always display well is because they have been meticulously hinted. Verdana has a ...



Only top voted, non community-wiki answers of a minimum length are eligible