Rocket Validator integrates the W3C Validator HTML checker into an automated web crawler.
<section> element can be used to define sections of a document, like chapters, tabbed content, etc. Consider using a heading element (any of
</h6>) to present each section. Example:
<h1>All about guitars</h1> <section> <h2>Guitar types</h2> <p>Acoustic, electric, classical... we have them all!</p> </section> <section> <h2>Amplifiers</h2> <p>Analog, digital, portable...</p> </section>
Related W3C validator issues
The <article> element can be used to define complete, self-contained compositions of a document, for example blog posts. Consider using a heading element (any of <h2> to </h6>) to present each article.
<h1>Our blog</h1> <article> <h2>How to validate accessibility</h2> <p>Use Rocket Validator for a in-depth scan</p> </article> <article> <h2>How to monitor sites for accessibility</h2> <p>Define schedules in Rocket Validator</p> </article>
The HTML <h1> to <h6> elements represent headings for the different sections of a document, where <h1> is the highest section and <h6> is the lowest. Headings are specially important on screen readers as they give a quick overview of the contents of the different sections in the web page, so although it’s technically correct (not an error) to use a <h1> in this way:
<section class="about"> <article> <h1>Article heading</h1> <p>Lorem</p> </article> </section>
this will raise a warning as it would be preferrable for example to leave the <h1> for the heading of the <section>, and <h2> for the heading of the article, like this:
<section class="about"> <h1>About heading</h1> <article> <h2>Article heading</h2> <p>Lorem</p> </article> </section>
The main element represents the dominant contents of the document, so it should not be contained within another section.
A document must not have more than one main element that does not have the hidden attribute specified.
A hierarchically correct main element is one whose ancestor elements are limited to html, body, div, form without an accessible name, and autonomous custom elements. Each main element must be a hierarchically correct main element.
25,000 HTML checks per month. Fully automated.
Save time using our automated web checker. Let our crawler check your web pages on the W3C Validator.