Web Designers should all be using this idea by now: Font Icons.
somerandomdude.com
Web Designers should all be using this idea by now: Font Icons.
1–10 of 78 posts
Re: Web Designers should all be using this idea by now: Font Icons.
#2Great idea and great icon set. I will be using this right away!
Re: Web Designers should all be using this idea by now: Font Icons.
#3Not to toot my own horn, but I created exactly this a few months back: http://tipogram.com/
Re: Web Designers should all be using this idea by now: Font Icons.
#4Drew Wilson's Pictos Font is pretty awesome if you're looking for alternatives: http://store.drewwilson.com/pictos-font
Re: Web Designers should all be using this idea by now: Font Icons.
#5I generally like to think that icon use should be handled as part of the CSS, as it's a design element and not part of the document semantics. Putting it in the markup means that if the design is updated, the markup is still stuck with the old icon, which means it's more work to update the site.
Re: Web Designers should all be using this idea by now: Font Icons.
#6I like this muchly, buy it does not render the icons on my phone (motorola photon).
Re: Web Designers should all be using this idea by now: Font Icons.
#7You can do this with sprites too.
Re: Web Designers should all be using this idea by now: Font Icons.
#8I can't find the information, but my understanding is that this approach isn't good from an accessibility standpoint because a screenreader still interprets the icons as their corresponding character and reads that character. As a result, instead of ignoring a checkmark icon, it would try to pronounce it as a single letter.
UPDATE: Further digging seems to validate that most modern screen readers do ignore pseudo elements. So, there's no doubt that this solution is promising. However, as with anything, your user agent baseline should be considered before using it. Saying that everyone should be using this right now probably isn't a reliable blanket recommendation.
Re: Web Designers should all be using this idea by now: Font Icons.
#9I can't find the information, but my understanding is that this approach isn't good from an accessibility standpoint because a screenreader still interprets the icons as their corresponding character and reads that character. As a result, instead of ignoring a checkmark icon, it would try to pronounce it as a single letter. UPDATE: Further digging seems to validate that most modern screen readers do ignore pseudo ele…
Do screen readers parse CSS in their reading? I would think this would avoid that problem by using the :before pseudo classes rather than injecting it into the dom directly.
edit: fuller thought.
Re: Web Designers should all be using this idea by now: Font Icons.
#10I can't find the information, but my understanding is that this approach isn't good from an accessibility standpoint because a screenreader still interprets the icons as their corresponding character and reads that character. As a result, instead of ignoring a checkmark icon, it would try to pronounce it as a single letter. UPDATE: Further digging seems to validate that most modern screen readers do ignore pseudo ele…
This is the same problem I have with this approach. It seems like a cool idea, but I don't want to break accessibility. I think you can get around this using aria and having it skip over that element.
See aria-hidden:
http://www.w3.org/TR/wai-aria/states_and_properties#aria-hid...
Authors MAY, with caution, use aria-hidden to hide visibly rendered content from assistive technologies only if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using aria-hidden to hide visible content from screen readers MUST ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.