What are cons to use custom fonts techniques compare to web safe fonts? in terms of
- site performance,
- site maintainability,
- Development time
- screen readers users,
- mobile users,
- low speed users
- Sighted User experience
views:
56answers:
3
A:
The con is simply that your page will not look the same to anyone who doesn't have your custom fonts.
More info here: http://en.wikipedia.org/wiki/Web_typography#Web-safe_fonts
If you use Font-Face to use custom fonts in the user's browser, you will add overhead in the form of additional web traffic to get the fonts downloaded to the user's browser. However, once the fonts are downloaded to the browser, they are cached so they don't have to be downloaded again.
Robert Harvey
2010-05-02 01:01:14
no need for user to have fonts , if i use sIFR, Font-face, etc
metal-gear-solid
2010-05-02 01:02:47
sIFR has a Flash dependency.
Robert Harvey
2010-05-02 01:31:16
Flash coverage is pretty high though. Almost 99%. Still then, when not available, you can always specify a fallback standard font.
BalusC
2010-05-02 01:58:35
Not so much for the mobile market though, BalusC. However they'll still see the text with a fallback, so not a massive deal.
Gary
2010-05-02 02:02:39
@BalusC - Agree with you but sIFR text has problem with firefox's extensions Adblock and Flash block
metal-gear-solid
2010-05-02 02:43:13
A:
In regards to sIFR, main cons would be more effort to implement, inconsistent site (for people with flash turned off) and obviously the page load time will be slower. Screen readers can also not read flash, hence they may miss any text that is using this technique. I'd recommend against using sIFR for any body text.
Gary
2010-05-02 01:51:32
A:
Performance does not matter if your page looks terrible to some of your audience.
You need to weigh your audience and see if it they can all use the special fonts.
Romain Hippeau
2010-05-02 01:59:54