ptg16476052382 LESSON 13: Structuring a Page with HTML5
sections of a page that should be treated as page content, and parts that are boilerplate
used across multiple pages like headers, footers, and navigational elements. The structural
elements are combined into a page outline that represents the overall structure of the page
and leaves out the sections that are not part of the page content. In Table 13.1, there’s a
list of the new elements introduced in this lesson. As you’ll see, the descriptions of most
of them include the names of the elements themselves. That was the intention behind the
design of HTML5.TABLE 13.1 New Tags Discussed in Lesson 13
Tag Description
<header> Represents the header of an HTML document. Excluded from the page out-
line.
<footer> Represents the footer of an HTML document. Excluded from the page outline.
<nav> A section containing navigation elements. Included in the page outline.
<section> Represents a section of a page. Included in the page outline.
<article> An article. Included in the page outline.
<aside> An aside, sidebar, or other supplemental content. Not included in the page
outline.Workshop
The workshop contains a Q&A section, quiz questions, and activities to help reinforce
what you’ve learned in this lesson. If you get stuck, the answers to the quiz can be found
after the questions.Q&A
Q You talk a lot about sematic markup. What are the tangible advantages?
A For regular desktop browsers, web pages look the same whether they are written in
semantically correct markup or not. That said, proper semantic markup makes web
pages much easier for users with disabilities who use screen readers to browse the
Web. It also makes it easy to process the content of web pages with software and
extract meaning from them. Finally, as a developer, it’s easier to understand how a
web page is constructed when it uses semantically accurate tags.