Skip to main content

Comic Sans Is (Generally) Lousy: Letters and Reading Challenges

Specimen of the typeface Comic Sans.
Specimen of the typeface Comic Sans. (Photo credit: Wikipedia)
Personally, I support everyone being able to type and read in whatever typefaces individuals prefer. If you like Comic Sans, then change the font while you type or read online content. If you like Helvetica, use that.

The digital world is not print. You can change typefaces. You can change their sizes. You can change colors. There is no reason to argue over what you use to type or to read as long as I can use typefaces that I like.

Now, as a design researcher? I'll tell you that type matters a lot to both the biological act of reading and the psychological act of constructing meaning. Statistically, there are "better" and "worse" type for conveying messages. There are also typefaces that are more legible and more readable. Sometimes, legibility does not help readability, either, as a type with overly distinct letters (legibility) can hinder word shapes and decoding (readability).

One of the common myths I constantly correct in social media and in online forums is that Comic Sans is somehow the "best" typeface for children and adults with dyslexia, ADHD, autism, and other disabilities. A blog post caused a small wave of arguments on social media in February (2017):

https://theestablishment.co/hating-comic-sans-is-ableist-bc4a4de87093

No, hating Comic Sans is not ableist, sexist, or racist. The typeface has serious legibility and readability problems. See one excellent technical critique at Design for Hackers:

https://designforhackers.com/blog/comic-sans-hate/

There really are explanations for why people find Comic Sans annoying. It's a bitmap font designed for 12-px text (not 12-pt) on lousy 14-inch CRT displays in the era of 800x600 computer monitors. It has lousy kerning, small counters, true monoline strokes, easily confused letters from a distance (i I l 1, e c o, m = rn) and is not meant for long text flows.

A much better replacement is available: http://comicneue.com/

Comic Neue fixes the flaws of Comic Sans. Download it. Use it when you have any reason to use Comic Sans. It's a lot better.

What makes a type both legible and readable? Distinct letter forms that enable quick recognition based on word shapes.

A typeface can be a serif or sans-serif face. It doesn't matter. It can be classic or modern. The face is less important than the letter shapes and their overall conformity to standard word shapes.

Erik Spiekermann, from Stop Stealing Sheep:
"Research has shown that our eyes scan the tops of the letters' x-heights during the normal reading process, so that is where the primary identification of each letter takes place. The brain assembles the information and compares it with the shape of the word's outline. If we had to consciously look at individual letters all the time, we would read as slowly as children who have not learned to assume a word's meaning from such minimal information." (p. 107)

  • Ascenders (and descenders) matter to word shape. Ascenders more, since they are at the top.
  • Too large an x-height, caps and lowercase blend.
  • Too short ascenders and descenders, all words look like rectangles
  • Too small x-height, slows reading, too

Sans or serif, what matters most is word shape and distinctiveness. When I (i), l (L), i and 1 look similar from a distance, there's a problem.

Now, if you want a more interesting debate… research has suggested teachers give lower grades and readers find less trustworthy text set in sans-serif type. The same article in various typefaces, the same academic paper, the same letter set in different typefaces reveals a curious pattern: we trust "classic" serif typefaces more than the "newer" sans-serif typefaces.

Use whatever type you want. But know that whatever typeface you select when sharing a text with others will influence those readers.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.