Request a font

We add new fonts to the Typekit library all the time. Fonts are carefully evaluated before being added to the library, and we often work closely with our foundry partners to optimize fonts for the web before releasing them. We have a preference for great text faces, but will also accept outstanding display faces. We do not typically accept pixel fonts, grunge fonts, ornaments, or dingbats.

Icon/symbol fonts

Typekit is committed to serving fonts in a standards-based, accessible manner. As such, our current policy is not to include icon or symbol fonts in the subscription library.

Using such fonts on the web requires that you map the symbols to characters in the alphabet (e.g., a shopping cart icon may be mapped to the letter “B”). Doing so is both non-semantic and inherently inaccessible. If for some reason the font failed to load, a user would see a “B” instead of the shopping cart. Worse, even if the font did load correctly, a screenreader would read the “B” and have no idea that it means “shopping cart.”

The new version of Unicode promises a much expanded set of values for icons, so the future is bright. In the mean time, we will continue to look for an accessible means of supporting these kinds of fonts.

Web-safe fonts

Web-safe fonts – such as Arial, Courier, Georgia, Times New Roman, and Verdana – are commonly installed on a wide range of operating systems. The availability of these fonts means that they can be used on any website even though they are not included in the Typekit library. No additional code is needed to use a web-safe font; simply add the family name to your CSS stack:

body {
font-family: "Times New Roman", Times, Georgia, serif;
}

These fonts are also good choices to use as fallback fonts because they are available on most user machines.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.