Stop Using Arial and Helvetica (2013)
64notes.com
64notes.com
A bigger problem is, to many international users (and news publishers that have articles with names in international characters), it matters if it works. In that regard, Arial and Times New Roman are the winners hands-down. They will display whatever you can possibly imagine. Part of the reasons why many people chose those fonts over the "fucking amazing" fonts that the author suggested (Georgia included) is that most of them have abysmal international support. "日本語," "中文," "ไทย," or "Tiếng Việt," for example, reads just as well as rectangular boxes in Georgia [1] (fallbacks will cure the rectangular boxes but Georgia with fallbacks looks like crap in the case of "Tiếng Việt").
Verdana and Tahoma are not compact enough for many of the applications I was planning to do. The capitalized "I" character in Tahoma is annoying at best and plain ugly to look at at worst.
On a personal level, the Ubuntu-esque font in TFA somehow rustles my jimmies.
My theory is that the fallbacks are designed to work well for those popular fonts so it doesn't look off when the system falls back. The consistency in the width of the stroke seems to be the most important factor to my eyes. Here [2] you can see the mix looks natural, while in Georgia in dev tool it looks inconsistent. The screenshot is made on my Ubuntu computer.
1: https://www.myfonts.com/fonts/microsoft/arial/ 2: http://imgur.com/a/hBl0A
And as for Arial, most of the attitude directed towards it is nothing more than anti-Microsoft snobbishness.
You might be surprised how many people prefer 17pt comic sans to the crisp 7pt pale-gray-on-white designers usually label "joy to read" or "beautiful".
Perhaps because they are actually neither and many designers are not well-versed in typography. Making text beautiful (but not necessarily readable) is design; making text readable (but not necessarily beautiful) is typography. They of course, overlap, and good typography usually looks good as well.
I disagree. Arial features some truly revolting glyphs. The R being the worst offender. Probably of any font I can think of. The G is also pretty disgusting.
On the other hand I find it hard to make something look bad using only Helvetica.
Also, I don't really buy that "less contrast" argument. Not everyone uses a HDR Retina screen, so by dialing down the contrast in CSS, you're reducing the available contrast range on sub-par screens. People with high-contrast screens should just dial down the brightness a bit.
The problem is when inexperienced developers read about this UX rule and do both grey text and off-white bg, or use a grey text that is far too light and removed all contrast making the eyes strain to see the text at all, something that is all too common.
I use a sub-par screen regularly, a 2007 T42 screen, and the app I use most on that PC is FocusWriter, that has low contrast text aimed toward longer periods of writing .
If readability of multiple paragraphs of text is your goal, than there are many alternatives that are measurably easier to read (e.g., for sans-serif typefaces: try DejaVu Sans, Open Sans, or Calibri, or consider a typeface with serifs suitable for screens).
A lot depends on your target audience of course (age and eyesight matter as well), and HiDPI screens help a bit — but unless your demographics consist exclusively of Apple fans or mobile users only you can't rely on that. On average though reading Helvetica (and Arial) is cognitively more taxing than a lot of good alternatives. I'm surprised this isn't common knowledge in the HN crowd.
In the beginning, my personal template used to be very complex. Header, footer, a cloud chamber image as a watermark, custom fonts. Over time, I simplified it more and more, removed the watermark, the header and footer backgrounds, and so on. The only extravaganza remaining was the font (Source Sans Pro, and Source Sans Pro Light for the titles... I found it looks quite elegant to make the titles lighter instead of bolder, they draw enough attention already.)
Long story short, today I just droped the custom font and went all Arial. I'm surprized how clean and professional it looks (like "I don't have to pretty up my slides, I have confidence in my content :-D"). I think I'm going to try this out for a while. It also has the benefit that everybody can now edit my .pptx files.
Here's a mirror: https://web.archive.org/web/20160404030737/http://www.64note...
Ironically, the CSS didn't load for me, so I read this site with the "browser defaults", which do many of the things the site was complaining about.
I think these arguments are in wrong order. Availability and page performance are huge things in webdev. Accessibility profit from correct fonts does not always cover usability cost of waiting them to download.
Arial and Helvetica are good readable fonts which always exist on every platform and don't require additional download.
This used to be the case, but it is no longer so. The Microsoft Core Fonts are not necessarily present on each OS (except for Windows of course), although on GNU/Linux and Android (IOS as well I guess?) you often do get a set of comparable replacements that are automatically substituted. Helvetica is always present on Apple devices, but it is certainly not present on each common OS.
There are no fonts that are guaranteed to be present everywhere (and this is fine).
In HTML/CSS (and many other GUI APIs) you can always rely on getting a serif, sans-serif, or monospaced font when you use their corresponding reserved family names, and with @font-face you can load whatever you want (providing you use a font that can be redistributed by you that way). So if you want all users to see text on your website in Comic Sans Neue, then that is (trivially) possible.
Oh? Most programmers know how to adjust the brightness and contrast on their monitors. If you have more contrast than you can use then your text is too large.
I'm not trying to dissuade you, just make you aware (if you weren't already) that you're making a choice by not making a choice.
I just recently made wikipedia sane for myself: https://userstyles.org/styles/137180/clean-wikipedia-minimal... (and I like black on white and change screen brightness if I want less contrast)
You may like Wikipedia's "mobile" site: https://en.m.wikipedia.org/wiki/Launch_loop
The mobile site on desktop looks indeed great, quite close to what I built (just sans-serif, but that's a matter of taste).
What's with the jpeg images and labels? I had to closely look at it to see when did font A ended and font B started.
Author should've explained better imo, as I don't think I got the message, except "don't use it because...reasons"
Also, if the designer is focusing on "readable" they need to make the text of the jpegs very much larger.
My answer is: he chasing the wrong animal. The serif fonts are more readable for me. The serifs matter. I hope I'm still not in a minority.
Arial though renders well on low pixel density devices (like todays FHD screens) and when rendering small characters, that is, I think, why it is still used in many business webapps.
Glad to see some Georgia love, though.
What we really need is to purge ourselves of these so-called rules and design sentient fonts that can speak up and say "I can't go there! I'm serif/sans/fantasy/mono!".