Tag Info

Hot answers tagged

121

Screen digits are right aligned to maintain positional consistency between what a number represents (in base 10 that would be units, tens, hundreds, etc.). E.g. If I were to have 764 and then multiply it by 24, the answer would be 18336. By aligning to the right I've consistently seen the same unit representation in the same position, and when I've had new ...


32

Digits are right aligned for similar reasons as you would right align them in a spreadsheet or a table. i.e. when you see multiple numbers (and they all have a fixed set of decimal places), then it's easier to compare the numbers with each other because the digits corresponding to each place value are in the same physical position, thus making it easier to ...


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 ...


15

There is no evidence that serif or sans-serif significantly impacts readability. Alex Poole conducted a study on Which Are More Legible: Serif or Sans Serif Typefaces?. His conclusion: What initially seemed a neat dichotomous question of serif versus sans serif has resulted in a body of research consisting of weak claims and counter-claims, and study ...


13

Disclaimer: I am not a native speaker of a language which does use guillemets as a way to denote quotes. But I wanted to offer a view on how context can help identify if the content being referenced is a phrase or a case of pagination I believe there are two aspects to it I believe this is one of those cases where users can visualize whether a phrase ...


10

I don't have any data about this question, neverthless here my thought: Readability is much better for right aligned numbers. Why? Consistency. The Decimal points always stays at the same location, decimal separators too. So it is much easier for a user to identify how big a number is. download bmml source – Wireframes created with Balsamiq ...


8

When using right aligned numbers you must note that decimal separators are aligned only if there are equal amount digits after decimal separator: 12 345,90 132 987,9376 Aligning such numbers left would probably be even worse, so in cases where number of digits after decimal separator are not equal numbers should probably be aligned by decimal ...


8

There are two theories/explanations for why text in All Caps is harder to read. One says that it's because of the less unique word shapes, and the other says that it's because it's less common. Small Caps suffers from both these problems - it has a generic word shape and it's even less common than All Caps. So whichever of the "all caps" theories may be ...


7

I guess it's because uppercase letters are both more distinctive and recognizable. Compare, for example, lowercase 'i' vs 'l' and 'I' vs 'L'. It has no effect for power users but important for newbies I believe.


7

There are very few advantages to using all caps, and that is why we usually don't. When we read text, largely what our brains are doing is recognizing the overall shape of words, rather than the individual letters. Lowercase letters have different sizes and visual densities; some have ascenders sticking up, or descenders sticking down. This means that ...


6

If you want to consider users with special visual and/or cognitive requirements, it becomes quite complicated and there's no single answer. The W3C Web Accessibility Initiative's Web Content Authoring Guidelines (WCAG) provide a good starting point. That's probably the single most thoroughly-researched resource on web accessibility, though it's not totally ...


4

A non-blind user will usually already be familiar with that symbolic usage of « and », and also pairs ‹/›, </>, <</>>. Color, size, padding and border can improve the recognizability – your sample image shows the latter two used successfully. Localized text at the open/tall side of the symbols helps even more. If they appeared inside a text ...


4

The best way is to show them. Take a screenshot of the tool itself and redesign it using properly treated Typography so they can see the difference. You can present your case with "Before" and "After" slides. In my experience because I like to advocate good design, sometimes will do this just for the heck of it because some bad designs look so gawd-awful. ...


4

In general, columns of numbers which are being examined as numbers should be decimal-point aligned (or right-aligned if the only decimal point is "implied"). Quantities which involve more than one radix point (e.g. currency amount in Britain prior to decimalization) should align each radix point, and right-align the columns between them; e.g. an itemized ...


3

I would simply make sure that each menu item was correctly padded/margined. If so, you'd get something more along the lines of this:


3

Actually, after writing that comment, I think I've thought of an answer the question. No, I don't think there is an ideal multilingual font size. The question is akin to asking "what is the ideal font size to use in the user interface for software that does everything for everyone?". It depends on context, purpose, audience and all the other usual factors ...


3

I believe it's partly alexeypegov's answer of distinctiveness, but also historical reasons. The first typewriters, which also had the first QWERTY keyboard, only supported upper case letters.


3

Well I'm not an avid book reader, but I am a programmer and I look at text all day. For me text is a tool. I started programming with notepad black and white and it really wasn't all that great. Today my workshop looks like this. This is highly tailored to my preferences. In low light environments I strongly prefer light on dark, and I suspect most ...


3

It was common knowledge that humans read words as a shape until Ph. D Susan Weinschenk informed the community in her article 100 Things You Should Know About People: #19 — It’s a Myth That All Capital Letters Are Inherently Harder to Read that the shape theory is wrong: It’s parallel letter recognition, not word shape — The old theory on word shapes ...


3

Not mandatory. But highly recommended. Roboto was introduced and standardized by Google for supporting devices of different dpi to have readability and legibility of fonts. You can see that many apps have their own custom fonts which are either unique to their brand or to match their site. So Google cannot make it mandatory. It's highly recommended ...


2

Using black text on white background can obviously make your screen contrast. To make your screen comfortable to view, you can change the brightness and apply for an app called F.lux. This is a freeware to make your computer color automatically changed by the time of day, no-glare on your eyes. Actually the color is not the point, the time on staring at it ...


2

Black text is not the problem. Glaring white background is. That background glare is the cause of eye-strain. Grey text just makes that worse as users often strain to read - which is why grey text often takes longer to read than black text. In fact, many people can "see" a whole page of black text and get a sense of the message in an instant - almost ...


2

You asked which is "better" and the Evil Closet Monkey cited an excellent article on legibility. But another interpretation of "better" concerns how the font will affect the reader's perception of the credibility of the information presented. This article notes a study that found certain Serif fonts created a slight increase of confidence for the reader ...


2

A few rules of thumb: I recommended providing at least two themes - dark on light and light on dark as some users may not be able to read one of the two. For light on dark, make sure the contrast isn't too high (e.g. use grey on black, not white on black). Make sure the contrast between the intensity of foreground and the intensity of the background is ...


2

There is no rationale to the best of my knowledge. It's a convention — one that's different in different places. For example in the UK it's much more common to see spaces or thin-spaces around em-dashes, or a spaced en-dash used instead of the closed em-dash. Long discussion on variations and what different style guides say at ...


2

You could be really aggressive and actually block admin users from entering titles longer than the maximum space you think they should take up. The down side is that this will make your system less flexible (there will always be genuine use cases for long titles), and create a negative experience for your admin users. Not good. Helpful hints can guide users ...


2

In my experience in French, a language that makes common use of guillemets, you would have no confusion using « and » as previous and next page links respectively, and giving the arrows affordance (such as boxing them in the same way as the page numbers, as the examples Mark Nugent provides) would absolutely ensure it. Your biggest challenge, as others have ...


2

To answer the question you would need to look at two things in particular: Best practice for bullet points Optimal length of characters per line Best practice would suggest that the purpose of a bullet point is to summarize or create an easily scannable list of items. The more you increase the length of the content in that bullet point item, the more you ...


2

Google is using 'Material Design' to give their vast number of different services a unified look and feel – so for google designers using Roboto is mandatory because it's part of their design by definition. IMHO if you want to build a material design 'inspired' website, you are of course free to quote any design patterns as you like – so using Roboto could ...


1

In my opinion truncated titles shouldn't be used. It seems to me that you can use a varied font-size depending on string length.



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