Rocket Validator automatically checks your pages on the W3C Validator.
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
<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
<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
</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>
<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
<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>
When was the last time you validated your whole site?
Keep your sites healthy checking for A11Y/HTML issues on an automated schedule.