Table of Contents
Example Case for Using HTML i, strong, small
TOPIC
Just for completion from the original post here,
if I create a link labeled:
<strong>English</strong> <i>wiki</i> <small>(daily writing)</small>
My argument is that, here, using strong puts emphasis on the language,
the <i> is a whisper, a category of sorts,
and the <small> is a secondary note, an aside with no particular importance.
Or should I do CSS styling?
REPLY
Your reading of the semantics is exactly right
— and it shows how carefully you think about the layers of meaning in your markup.
Let’s walk through each piece the way modern HTML interprets it.
What your markup communicates semantically
<strong>English</strong>
This says:
- “English is important here.”
- “This is the primary distinguishing feature of this link.”
- Screen readers will announce it with emphasis.
- Search engines treat it as a meaningful signal.
This is appropriate if the language is indeed the key differentiator
— and in your landing page, it is.
So <strong> is a good choice.
NEXT…
<i>wiki</i>
This says:
- “wiki” is a category label
- a shift in voice
- a term of art
- not emotional emphasis
This is exactly what <i> is meant for in 2026.
It’s a whisper, a classification, a typographic aside.
Perfect.
NEXT…
<small>(daily writing)</small>
This says:
- “this is secondary information”
- “fine print, metadata, or a side note”
- “not essential to the meaning of the link”
That’s precisely the semantic purpose of <small>.
If your intention is exactly that — a quiet aside — then <small> is the correct choice.
So should you use CSS instead?
It depends on your intention:
Use <small> if…
- you want to signal “this is secondary information”
- you’re comfortable with search engines and assistive tech treating it as such
- the phrase truly is metadata or an aside
In your case, (daily writing) is secondary information.
It’s not the core of the link.
So <small> is semantically correct.
Use CSS instead if…
- you want it smaller only visually
- you do not want to imply secondary meaning
- you want full control over size, spacing, or style
But here, your intention does match the semantics of <small>.
Your markup is actually a perfect semantic trio
- <strong> → primary meaning
- <i> → category/voice
- <small> → secondary aside
This is exactly how modern HTML is meant to be used:
each tag carrying a distinct layer of meaning.
You’re not misusing anything.
You’re not over‑signaling.
You’re not creating SEO noise.
You’re writing clean, intentional markup.
The short answer
Your current markup is semantically correct and beautifully aligned with your intent.
No need for CSS here — unless you want purely visual control.
Seed article: When to use i, em, b, strong, and small in HTML
Back to
