semantic-markup

After the article I have list of tags related to article. Is it semantically correct to wrap list of those tags in <nav> html tag? If no, what would be the proper one? <nav class="tags"> Tags: <ul> <li><a href="#">Tag1</a></li> <li><a href="#">Tag2</a></li> <li><a href="#">Tag3</a></li> </ul> </nav> MDN states: Not all links of a document must be in a <nav> element, which is intended only for major block of navigation links; typically the <footer> element often has a list of links that don't need to be in a <nav> element. User agents, such as screen readers targeting disabled users, can use

A matter of semantics. If I have a HTML page that is basically one big table, what element do I use for a header? Ordinarily, you'd use a h1 for the heading of the page, and a caption for the table's heading. But what if the table is the only thing on the page? Including both looks a bit silly. So do I use a h1 and forget about the caption , or vice versa? Are there formal (W3C or WHATWG) recommendations about this? If so, I can't find them. PS For the sake of this question, let's assume that the table is filled with tabular data, OK. A table caption can contain free-form content. You could

is it necessary to have <th> in any table? even if table has no heading? table has 3 other tag <thead> <tbody> <tfoot> is it necessary to use all even if i have nothing for table footer. Firefox by default add all these in code. and is it necessary , <th> always should be in a <thead> and if I have a heading in content received from client , and heading is from outside the table but related to table then how should i place that heading for table As a above table <h3>Heading of table<h3> <table>......</table> as a heading of table <table> <thead><tr rowspan=3><th>Heading of table</th></tr><

Is it necessary to have a heading of <section> in HTML5 like mentioned here http://blog.whatwg.org/is-not-just-a-semantic Sometime on a page we have some elements which are related and can be combined in a <section id="semantic name"> instead <div id="semantic name"> But we don't have any Heading for that.. Is it OK to use <section> without having <h1> , <h2> , <h3> inside According to the HTML5 Doctor , you should not use <section> if there is no natural heading for it. Also, they say: The section element represents a generic document or application section…The section element is not a

Is it useful to add whole code in #container , #Wrapper in every CSS layout? Can't we make layout without this extra div ? What are pros and cons to use this extra div ? Is it good practice ? Is it useful for any type of design/layout? Is it semantically correct? Is it useful to add whole code in #container, #Wrapper in every CSS layout? It would not be needed in every layout unless every layout was the same, and then only if they require a wrapper/container. Can't we make layout without this extra div ? Yes, you can sometimes dispense with the extra wrapper div. What are pros and cons to use

I’d like to include published and modified time of an article. I looked through documentation and cannot find info about this. So far, I got this: <article> <h2>Summer</h2> <p>Also the favorite word of <strong>5000</strong> people more</p> <time pubdate="2009-11-13">1s</time> <time datetime="2009-11-13">10s</time> </article> The time element can’t have a pubdate attribute. (It was part of early drafts, but it got removed.) HTML5 itself doesn’t provide a way to specify that a date is a publication or a modification date. If you need to specify this in a machine-readable way, you could use an