Lately I have been messing around with Sifr, and I am aware or its pluses and minuses. I also am aware of Cufon, and the many different ways to replace text with images. What do you guys think of typeface replacement? From a programming standpoint at least.
04/16/2009 - 14:35
I haven't played with them enough to give any real good answers, but at the moment I think I prefer Sifr simply because it supports text selection. As soon as the javascript implementations figure that out I think they will take over.
04/16/2009 - 14:38
That seems to be the biggest "pluses" that sifr has.
04/16/2009 - 14:53
How do these affect things like screen readers (for the blind) and search engine's ability to parse the page contents?
04/16/2009 - 15:09
I know sIFR is layered above elements (technically it creates a flash object AND the element it is layered above), so screen readers can still be used, as well as page parsers. I actually read a whole bunch of their FAQs and a few articles on sIFRs abilities, and it seems like the best choice for custom typefaces on the web.
Quote from the offical sIFR FAQs:
Isn't the use of Flash a problem for screenreaders?
That's exactly what sIFR is about. It's a behaviour layer, laid over the markup and styling. This way, screenreaders will see the normal heading, as it should. It's the same as with the above question.