Instructions and covered skills
Read each prompt carefully before selecting a response. Focus on the meaning and purpose of the content rather than its visual presentation. Keep your attention on the test and turn off notifications where possible. Consider how browsers and assistive technologies interpret document structure. Choose the response that best matches the intended HTML semantics. Review your selection before moving on, and avoid making assumptions based only on element names.
Key Areas
This test examines the ability to create meaningful HTML document structures using semantic elements. Candidates interpret the purpose of major landmarks, including header, nav, main, aside, and footer, and determine when each landmark communicates useful page-level or regional meaning. It also covers the distinction between self-contained content represented by article and grouped thematic content represented by section.
Heading structure is another central area. Candidates should understand how h1 through h6 express a logical hierarchy based on content relationships, not visual size. The test also addresses contextual semantic elements such as figure, figcaption, time, address, details, summary, mark, and cite. These elements add meaning that can be understood by users, tools, and collaborators reviewing the source.
Questions emphasize choosing elements according to the content's role. A semantic choice should remain appropriate if stylesheets are removed, visual layout changes, or the content is reused elsewhere. Candidates should recognize when a generic div is suitable and when a named element communicates a clearer purpose.
Recommended Preparation
Review the HTML specification and trusted accessibility references for landmark and sectioning elements. Practice mapping common page regions, such as site navigation, product information, related links, article metadata, and legal notices, to appropriate semantic elements. Build small document outlines and inspect whether the heading order reflects the relationships among topics and subsections.
When reviewing existing markup, ask what each region means rather than how it looks. Check whether repeated content has a meaningful container, whether independent entries can stand on their own, and whether supplementary material is separated from primary content. Use browser accessibility inspection tools or screen-reader landmark navigation to confirm that the structure exposes useful regions and labels. This preparation supports maintainable templates, clearer content models, and more understandable web documents.