Nicolas Gallagher 12 December 2011 A couple of little issues in this recap of the font-icon technique. 1. :before and :after are pseudo-elements, not pseudo-classes 2. The @font-face technique that is referenced is not the most bulletproof method at the moment. This one is – Further hardening of the bulletproof syntax 3. The last testing results I read showed that most screenreaders (but not VoiceOver) don’t read CSS generated content (but probably should), and there are support issues for @font-face on mobile – Dingbat Webfonts: Great potential, but we see (and hear) accessibility issues
Nicolas Gallagher
A couple of little issues in this recap of the font-icon technique.
1. :before and :after are pseudo-elements, not pseudo-classes
2. The @font-face technique that is referenced is not the most bulletproof method at the moment. This one is – Further hardening of the bulletproof syntax
3. The last testing results I read showed that most screenreaders (but not VoiceOver) don’t read CSS generated content (but probably should), and there are support issues for @font-face on mobile – Dingbat Webfonts: Great potential, but we see (and hear) accessibility issues