The Right HTML Element For Icons17 Feb 2015
Do you use
<i> for icons? Whatever your answer is, keep that at the back of your mind. I am sure you have reasons! Let me tell you what I use. It’s
In my conversations with people about html & semantics, over time, this topic has come up too often! For all we know, there isn’t a right choice. Not at least from what we have got from the HTML Spec.
So how do we go about choosing an element to deal with icons? I’ll say choose as a human would; by being stupid and finding a fit. Religious folks… angry?
People use spans stating it’s more appropriate “semantically”. Here’s what W3C says…
The span element doesn’t mean anything on its own, but can be useful when used together with the global attributes, e.g. class, lang, or dir.
Wait… what? That’s right. It’s the “meaningless” element. This allows you to use it for virtually anything and everything at text level but it’s meaningless nonetheless. The i element is a little different
The i element represents a span of text in an alternate voice or mood, or otherwise offset from the normal prose in a manner indicating a different quality of text, such as a taxonomic designation, a technical term, an idiomatic phrase from another language, transliteration, a thought, or a ship name in Western texts.
This makes more sense to me. Think about it, an icon is essentially a way to depict a piece of text otherwise. Graphically to be precise. It is a thought, a metaphor. This specification in fact forces us to be more creative and thoughtful about what “graphical metaphor” we should use. In an ideal world, we would be using an
<img> element to do this but even that has it’s own problems; an empty src makes a server request.
On the brighter side, both icon and
<i> have “i” to start with. To a human, “it fits the data” instinctively.
<i> element requires less characters. How do I leave that luxury? Saving bytes matter. I know there’s compression, but…
<span> <!-- 13 characters --> <i></i> <!-- 7 characters -->
Talking about screen readers( read accessibility ), neither a
span nor an
i helps. Almost always, the icons come in the form of CSS
background . With some mumbo jumbo of
background-position , we get the stuff done. Some would argue that today’s screen readers are habituated to find information like that using span. Don’t trust them. Focus on ARIA instead to get rock-solid accessibility. Here’s an example -
<i class="icon icon-settings" aria-label="Settings"></i>
Common usage tends to dictate language rules more than the other way around. If you’re old enough, do you remember that “Web site” was the official spelling when the word was new? Dictionaries insisted there must be a space and Web must be capitalized. There were semantic reasons for that. But common usage said, “Whatever, that’s stupid. I’m using ‘website’ because it’s more concise and looks better.” And before long, dictionaries officially acknowledged that spelling as correct.
Big names in the industry have used
<i> for icons. Bootstrap had earlier used it.(…they now use span though ) Facebook, Twitter -did it. Font Awesome examples utilize the
<i> element. Material Design Light too uses it in examples. Why can’t we?
<span> seems to be correct not by the reason it was built for but by the meaningless nature. For me, my intuition weigh in more. Using
<i> feels more familiar to me. I am gonna use it anyway.