On Styling Links Within Content

05.10.07

Design This Site Typography

Recently, Jonathan Nicol, who is ever so generous with his comments on this site, curated a nice collection of approaches to styling and denoting links. To return the favor of furthering the conversation, here is my remix of the topic. Styling links is something I have thought about for a while and is a recurrant problem with every new website design. Before this topic becomes less relevant to me, I figured I might jot down some thoughts on how I have approached this design decision in the past.

As I was writing this, I found things getting very drawn out, so this post will be mostly confined to links that live within content (i.e. inline links).

Jacob Nielsen’s Design Guidelines for Visualing Links is probably the best document to provide prescriptive advice on styling links. The value of the work lies in the quantifiable HCI research that led to the final synthesis. My ideal starting point for a link is largely the prototypical link that would emerge from applying Jacob’s advice: blue and underlined, in all of its default-browser-styles glory.

I favor, what I’ve referred to in the past as, design conservatism – which, unfortunately, can be a really misleading term to use. The central concepts of the approach are tradition and culture.

Tradition can be seen as the collective synthesis of meaning across a culture. By ignoring it, you run the risk of diluting the communicative potential of your work. There’s such a long and established tradition (largely thanks to browser defaults) of denoting links with blue, underlined text that having such treatment not be a hyperlink is as jarring as an inverted traffic light. By appealing to tradition, you leverage cultural expectations of interaction and meaning for greater clarity. Maximizing perceived affordance is a closely related strategy, but I feel that confines the approach to interaction design.

From Type: The Secret History of Letters:

It has been remarked that ‘extreme conservatism as to the presentation of reading matter has always been the oustanding characteristic of the reading public’. In other words, if it looks strange and unfamiliar, the reader won’t go near it.

In the case of links, the most conservative choice would be to make them blue and underlined. This represents a starting / reference point. But since links don’t live in isolation, but rather in the context of a web page that introduces its own set of design tensions, this style is not always the end point. One needs good reason to transcend the treatment, where the end result extends and never subverts the tradition of the device.

Putting Blue in Context

One of my favorite takeaways from toiling through Robert Bringhurst’s Elements of Typographic Style was a morsel of advice on how to choose the appropriate typeface. I think these excerpts sum it best:

Choose a face whose historical echoes and associations are in harmony with the text.

If, for example, you are setting a text by a woman, you might prefer a face, or several faces, designed by a woman

But perhaps a text by a French author, or a text dealing with France, might be set in a French typeface.

These assertions tie a decision like choosing a typeface closely to the cultural context under which it was conceived - in other words, a cultural artifact always carries with it the baggage of its past. Similarly, choosing blue speaks heavily to the history of the medium, which can often be too specific or wrong under the circumstances of your design goals. Some of the first sites on the web were those created by those with ties to academia, technology and government. The pedigree of the style make it an appropriate choice for non-profits, academic sites, archives, sites with a long heritage and those made for the tech-savvy audience. Sites meant for ubiquity, like Google, are complimented nicely by adopting this style as the core of their visual language. Communicating a novel, modern brand with blue underlined text can prove a challenge, making the color a good candidate to cycle through some transformations.

More obvious reasons not to use blue as your link color is if the content is set on a dark background or if it clashes with the already-defined color pallette of a brand’s identity.

When I go through design iterations, something I frequently try out is setting the link color to one found in the identity’s palette – especially when it’s a color that provides good contrast within the design. I like the way this associates “action” (that of clicking on a link) and instills a certain dynamicism to a company’s brand. This doesn’t always work, but using an identity’s color to constitute a specific piece of your visual language is also an option: doing so with buttons and headings can also further a cohesive and logical experience. Dan Cederholm’s Cork’d serves as a nice example of this:

Visual relationship between buttons and identity on Corkd.comNotice how the colors of the buttons “search” and “sign up!” match the wine glass logo. The relationship suggests: “search cork’d” and “sign up (to) cork’d”.

Transcending the Conventional Underscore

Getting past the underscore is not as natural as choosing a different color for the link, as the device is more closely associated with the concept of the link than the color is. Still, the default underscore (text-decoration: underline) leaves something to be desired.

I find underlined links can often be disruptive to the rhythm of the text. Content densely populated with such links begins looking busy with all of the extra lines crowding the leading. The default underline also tends to cut off the characters’ descenders. For example, take text set in 11px Verdana (figure 1). It is composed of 81 pixels, with the underline contributing 70 more. This effectively amounts to a 45% increase in the footprint of the link, which can quickly add up 1 + 1 = 3 clutter.

Comparison of text with and without an underscorefigure 1 - Along with obscuring descenders (notice the bottom of the ‘g’), the default underline adds 45% more pixels to this text. On link-heavy sites like Wikipedia, this can easily become a burdensome treatment at the expense of the content.

From my perspective, link text that distinguishes itself by color alone (without an underscore) is a bit too anemic and fails to stand out. More importantly, I’ve always taken to the almost-axiomatic idea, endorsed by accessibility professionals, that color alone shouldn’t be used to convey meaning. A crude test you can perform is take a screenshot of your website, drop it in Photoshop and desaturate the image. Upon desaturation, you might also find that the color of the type is far too light to be a comfortable read. Simply removing the underline is not the solution for me.

Instead, I find the light-colored underline to be a pretty fair compromise. It allows you to maintain the underscore to denote the link while minimizing the noise a conventional underscore can introduce. Most people use a light grey, or a darker, but dotted underline (effectively same thing). To accomplish this, I’m currently using a light color from this site’s color palette to underline my inline links. The only way to achieve this is to use the border-bottom CSS property, which has the added benefit of placing the underscore below your descenders.

Having made the leap of faith to embrace links with a light underline, this style can now serve as a valid future starting point.

I think it’s time to wrap up this overwrought prose. To be continued in the comments.

« Older Snap Preview Extreme Make-out
Newer » Ditching ‘Next’ and ‘Previous’ for Blog Navigation

5 Comments

1Jonathan Nicol

An excellent addition to the topic!

You may be interested to know that my current approach to styling links is the same as the one you advocate. A few days back I launched a client site using border-bottom on links instead of the traditional underline. I agree that a subtle underline is less disruptive to a pages’ visual design.

In his Vitamin article on the topic Paul Boag argues against messing with the underline at all due to poor support for border-bottom on certain devices, but I think he’s in the minority on this one.

2Erik

One issue I wrestle with when designing an advertising-supported website is how to differentiate text ads from non-ad links. This question is touched upon in the selected Simon Loxley quote:

if it looks strange and unfamiliar, the reader won’t go near it.

Good design demands that users are not confused or tricked into clicking ads that look too much like main content, but text ads that appear “strange and unfamiliar” will probably receive fewer clicks.

Assuming that some similarity between text ads and non-ad links is a good idea, constraints arise as long as advertisers demand control over the presentation of their ads (admittedly, a reasonable demand). For example, Google currently allows website designers to customize the colors of AdSense for Content text ads, but does not allow customization of other CSS properties, including font-family, font-weight, text-decoration, or border-bottom. This limits the website designer who wants to apply some of these properties to both text ads and non-ad links.

3Ephram Zerb

@Jonathan: Thanks for bringing up Paul Boag’s comments. He makes a good point and it’s something to keep in mind when designing for mobile devices. Equipped with this knowledge, this appears to be easily remedied by a mobile-specific stylesheet (this obviously necessitates browser support). However, from a brief assessment it would appear that both Opera and IE mobile browsers appear to support border-bottom without much difficulty (in context of inline links).

Paul Boag also notes that IE5 struggles with the border-bottom property. It’s true, but trivial. For one, the extent of the problem rests in the underline simply not showing up - the links still work and the main color remains. I have also made a conscious decision to not fully support an equivalent experience outside of the Grade-A browsers, making it all the less relevant for me. But I can comfortably say: ditching IE5 support is a safe bet for just about every new website project.

Btw, nice work on the Te Tuhi site. Love the grid-based design, semantic HTML and strong colors.

4Ephram Zerb

@Erik: There is definetly a tension, when using something like Google Adsense on your site, to make the ads consistent with the rest of your link treatments while also distinguishing the ads from your content. On the one hand, ethics dictate that ads shouldn’t be misinterpreted as your site’s content. On the other hand, a disparate treatment will likely make the ads less effective from the click-through perspective.

Super consistency in you link-treatments is a difficult thing to scale. If you look at the Bookmarks that are featured on this site’s homepage in the sidebar, you’ll notice that the links are neither blue nor underlined. Another example would be the navigation through the NYTimes.com property. Maintaining an effective content-hierarchy drives decisions like this and the context that the positioning affords, makes them viable.

Most of the time, the positioning of the ads already communicates that the links and text are ad units. If anything would make users stay away from those links, it would be just that. The fact that there are certain inalienable properties that appear accross billions of google ads contributes to this effect as well.

I think you’re right that a lot of designers would love the added control that you desire. Unfortunately, when working with something so unmaleable it’s an issue of compromise. But encapsulating decions like this, with the help of context, can make them more manageable.

5UtahLuxury.com

I prefer to not stuff links into my content unless it is an internal link. That way there isn’t any blurring of what is content and what is ad.

Leave a Reply

required

required (will not be published)


required