First, your second option isn’t quite valid HTML in the sense that all of the rows (TR) in a table should contain an equal number of columns (TD). Your header has 1 while the body has 3. You should use the colspan attribute to fix that. Reference: “The THEAD, TFOOT, and TBODY sections must contain … Read more
It is totally fine . The form will submit only its input type controls ( *also Textarea , Select , etc…). You have nothing to worry about a div within a form.
You should use different methods for different use cases: If you want to emphasise a phrase, use <em>. The <i> tag has a new meaning in HTML5, representing “a span of text in an alternate voice or mood”. So you should use this tag for things like thoughts/asides or idiomatic phrases. The spec also suggests … Read more
1) I think you should stick with the article element, as [t]he article element represents a self-contained composition in a document, page, application, or site and that is intended to be independently distributable or reusable [source] You merely have a list of separate documents, so I think this is fully appropriate. The same is true … Read more
To me, linebreaks should only be used inside paragraphs to indicate a new line. Adding line-breaks between paragraphs was used back in the day, when HTML looked like Chop Suey and the semantics of the HTML document looked like someone from preschool used Dreamweaver. I personally rely on margins and padding for content separation, if … Read more
As I state in my comment and you quote in the W3C, h1 is a heading and not a title. Each sectioning element can have its own heading element(s). You cannot think of h1 as being the title of a page only but as the heading of that particular section of the page. Just like … Read more
The <a>nchor element is simply an anchor to or from some content. Originally the HTML specification allowed for named anchors (<a name=”foo”>) and linked anchors (<a href=”#foo”>). The named anchor format is less commonly used, as the fragment identifier is now used to specify an [id] attribute (although for backwards compatibility you can still specify … Read more
Either: Add a heading (h1, …, h6) tag to your section element. Replace your section element with a div element. Ignore the warning. The message you’re seeing is a non-normative usage recommendation, as per the HTML5 spec (highlighting mine): The theme of each section should be identified, typically by including a heading (h1–h6 element) as … Read more
The address element must only be used if this postal address represents the contact information for “its nearest article or body element ancestor”, which, of course, is not the case for all addresses. But if address is used or not, it doesn’t affect the following. The whole address should be enclosed in a p element, … Read more
Yes, it’s valid. However, HTML5 encourages to use […] headings of the appropriate rank for the section’s nesting level. But it’s not a requirement, so you are free to choose. Using h1 everywhere allows for moving sections without having to adjust the heading ranks (although it would never be invalid, even if the ranks are … Read more