Re:Show HN: Markupwand, magically convert your photoshop fil...
by Ingolmo on Tuesday July 24, 2012 @04:12AM
(#4284788)
You cannot use ONLY these "meant to be" semantic tags (<article>, <header>, ...) to describe semantically all the content you have.
Divs is then the only way to go I know.
Re:Show HN: Markupwand, magically convert your photoshop fil...
by brianfryer on Tuesday July 24, 2012 @02:24PM
(#4287158)
I'll quote ricardobeat's comment above (http://news.ycombinator.com/item?id=4284877):
"Not every, but 95% do. For the rest, there are other pssibilities and tools to make sense of it (microdata, ARIA attributes, etc). Just ignoring semantics altogether won't do any better."
Re:Show HN: Markupwand, magically convert your photoshop fil...
by nnash on Tuesday July 24, 2012 @11:35AM
(#4286104)
Your understanding of semantics is a bit hazy. Conversely to the pull quote you grabbed from me any semantic element can be used in a non-semantic way.
Re:Show HN: Markupwand, magically convert your photoshop fil...
by brianfryer on Tuesday July 24, 2012 @02:22PM
(#4287151)
I agree I still have much to learn. But I don't let this get in the way of trying to "do things right" :-)
Then they are not semantic at all.
<div class="content">, <div class="post-title">, <div class="meta-data"> all have semantic CSS class names. But they are not semantic HTML names. Remove the CSS, and all you have is <div>, <div>, and <div>. This makes it difficult for screen readers (and web surfers who don't use CSS (are these people even real?)) to understand what the page is saying.
However <article>, <header>, and <aside> all have semantic meaning that can be discerned whether or not CSS is used.
Also: Whether or not something validates is not a good indicator of it being "semantic".