The state of web typography

Track: 
Design and UX
Experience: 
Beginner

In the beginning, web designers only had a handful of typefaces at their disposal to use in their designs. Then Flash and Javascript allowed unlimited fonts but lacked accessibility features. In the past year, it seems we finally have a winning solution: the @font-face method which has support from all major browsers and does so using only HTML and CSS.

Meanwhile, a second conversation is happening amongst those who actually own the fonts – the foundries. Would these emerging technologies ensure that their typefaces could not be easily copied from the web? Unfortunately @font-face is still not widely accepted by most foundries. Some allow you to use a hosted service like TypeKit, or you can venture into the burgeoning movement of open source and commercial-free fonts and enjoy free rein over your web typography.

Intended audience: 

Front-end web designers, UX designers, Graphic designers, Art directors

Questions answered by this session
Question 1: 
How have the methods for font replacement evolved over the past few years?
Question 2: 
How does web-embedded font licensing work?
Question 3: 
How do I use the @font-face method to ensure cross-browser compatibility?
Question 4: 
Should I host my own fonts or use a hosted service?
Question 5: 
How can I implement font replacement on my Drupal website?
3.666665
Your rating: None Average: 3.7 (30 votes)

Comments

Combine?

It seems that our sessions are very similar (http://chicago2011.drupal.org/sessions/type-revolutionary-s-cookbook). I'm told that we will have a better chance of getting any session on type into the schedule if we work together. I'd be happy to combine them if you are interested.

Diamond Sponsors

 
Palantir.net
VPS NET

Platinum sponsors

 
Trellon
workhabit

Gold Sponsors

 
Duo
Microsoft
Drupal Connect
Treehouse Agency
Chapter Three
HotDrupal.com
NorthPoint