HTML and CSS Reference
In-Depth Information
HTML5
HTML4.01
Yes, you can do it with a
<div>
, but with, say, an
<article>
element, the browser, search engines,
screen readers, and your fellow web developers all
know for sure that's an article.
So? It still looks the same.
Remember, we use the right element for the job,
right? That way we can communicate the most
explict structure we can, and all our tools can do
the right thing.
Right thing? Like what? Display it exactly the
same?
See, that is just exactly where you are wrong. Take
the
<aside>
element, which is for marking up
supplementary content on a page. Now on a
mobile phone with limited screen space, if the
browser knows that content is an
<aside>
, you
might see that content pushed to the bottom so that
you see more important content first. If the content
is in
<div>
instead, then any number of things can
happen depending on where in the HTML file the
content is.
I still don't see what the big deal is.
Now the browser can know the difference between
the main content in the page and an
<aside>
. So
it can treat the content in the
<aside>
differently.
For instance, a search engine might prioritize the
main content in the page over the content in an
<aside>
.
Great, so with HTML5 we know how to deal with
asides.
No, no, this applies to all the new HTML markup:
header, footer, sections, articles, time, and so on.
Well, I think it is about time you take that footer of
yours and stuff it in
C
ENSO
RED
C
ENS
Note
to e
ditor
: the
y got
out
of
hand
—can
we g
et t
hem
back
to
