Every article that I read about SxSW from this year’s South by Southwest has me wishing more and more that I had decided to go. One such article is Samantha Warren’s “SXSW 2009 Wrap Up.” Aside from her insider explanation about participating in the SxSW Web Typography panel discussion, she discusses an opinion I share; that designers should start using advanced web typography now.
Samantha says that as designers we need to push boundaries and get more creative with online typography whether they are personal, technical, or industry based. To view the slides from the discussion be sure to check out sxswtypography.com and to get some more great web typography resources.
Better Typography is on its Way
Regardless of mixed agendas and the technical limitations imposed as a result, advanced methods for web typography is closer to mainstream adoption than ever before. In order for it to get there though web designers are going to have to start using the tools we have now. For too long a lack of demand has pushed web typography to the bottom of the list of priorities for browser manufacturers. One approach, which happens to be the most disputed, is the subject of linking fonts with @font-face.
Font linking may not be a perfect solution however; web designers need to show interest in order for innovation to happen. Sure SiFR and other similar automated replacement scripts may work, but they are no more than fancy hacks. Hacks that are far too complicated, for what is really an issue of conflicting agendas not technology. At some point the issues will have to subside and then typography on the web will become an issue of what really matters; creativity. To get the full rundown on all the issues keeping font linking from going mainstream right now, I suggest taking a look at the article “@font-face in IE: Making Web Fonts Work” by Jon Tan.
A Practical Approach
The @Font-Face discussion is bound to continue for some time, however that does not mean web designers should wait. In order to jump right away and get creative, web designers just need to know how to make progressive enhancements to their designs. For example, designers can choose to use font linking for display type, and custom font stacks to enable other widely available fonts for body type. Yes, choosing to take this approach can lead to older and less capable browsers receiving different results but by now most web designers should be willing to accept websites looking differently in different browsers.
This is the approach I have been taking with my clients, what has your approach been? Have you been using some of these new approaches to utilize more interesting web typography?
March 30th, 2009 at 8:02 am
Hey Zinni
I really appreciate you featuring this topic! In addition to sIFR and font-linking, there are a lot of simple CSS techniques that really make a huge difference. Pseudo-elements (though not compatible with all browsers) can enhance the typographic experience for some and also just experimenting with font variety (like making your links a sans-serif while your body copy is a serif). There are so many possibilities, sorry I am just getting carried away… AGAIN, thanks for writing this, I am glad other people are getting stoked on web typography!
March 30th, 2009 at 8:08 am
Samantha,
Thanks for the comment, I agree that there are tons of ways that web designers can create more interesting typography right now. Pseudo selectors is a great example of a toll that can be used to improve web typography. What can be done right now is such a large topic that has been overlooked for far too long. I think once more designers accept that their typography might look less interesting in a couple of older / less capable browsers for a while then the floodgates of options really opens for them.
I think I am going to have to put together a couple of functional examples to show other designers just what can be done right now…
March 31st, 2009 at 8:08 am
Thanks for this post. As a typography fanatic, I appreciate the thoughts!
March 31st, 2009 at 4:58 pm
As a developer I cringe when I get handed designs with “advanced web typography”. There are so many times where a designer or client demands a specific font on copy that should really be a web standard font. One example would be copy that has to be translated in to multiple languages. For each different piece of copy you are looking at cutting multiple images. It adds so much time and complication to a process that should be as simple as updating the html or database with new copy.
There is a time and place for this stuff but so often I am forced to implement it in the wrong places.
Recent advancements with tools like Cufon reduce some of the headache but until @font-face is fully supported and older browser die off I find myself on the other side of this argument.
March 31st, 2009 at 7:12 pm
Evan,
It is the job of the designer to know when any potential tool is appropriate. Everything is contextual, real designers know this and practice restraint when something is not feasible. It is foolish to write off progress though just because it does not work in all situations. Every client and project are different so I would urge you not to completely close off the idea.
April 19th, 2009 at 3:37 am
Thanks for this post.