HTML • Chapter 16 • Foundations to Production
Figure Content
Each topic contains substantial explanation, ten focused teaching examples, its own HTML code example, code reasoning, expected browser result, and practice.
16.1 figure Element
figure Element is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
For figure Element, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In figure content, the markup should remain understandable as a document before presentation is added.
In Chapter 16, a reliable way to learn figure Element is to write a small valid fragment, inspect the browser result and document outline, then test one incorrect or missing attribute. This makes the reason for each piece of markup visible instead of treating HTML as a collection of tags to memorize.
Concept in plain language
figure Element is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid event page example that demonstrates figure Element. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 16, topic 1, example 1.
Example 2: Content variation
Change the text or resource used by figure Element in the FAQ page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 16, topic 1, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the photo story example using figure Element. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 16, topic 1, example 3.
Example 4: Accessibility review
Read the support page example using the semantics of figure Element. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 16, topic 1, example 4.
Example 5: Mobile review
Open the dashboard shell markup containing figure Element on a narrow screen. Ensure embedded content, long text, controls, and translated labels do not force the page wider than the viewport. This is Chapter 16, topic 1, example 5.
Example 6: RTL review
Translate the language page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 16, topic 1, example 6.
Example 7: Validation exercise
Run the booking page fragment using figure Element through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 16, topic 1, example 7.
Example 8: Progressive-enhancement check
Use figure Element in the media page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 16, topic 1, example 8.
Example 9: SEO and semantics review
Inspect how figure Element contributes to the meaning of the school page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 16, topic 1, example 9.
Example 10: Production review
Review figure Element in the course lesson for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 16, topic 1, example 10.
HTML code example
<figure>
<img src="/images/form-structure.webp" alt="Labeled HTML form structure" width="900" height="520">
<figcaption>Figure 1. Relationship between labels and controls.</figcaption>
</figure>Step-by-step code explanation
- Identify the element or attribute responsible for figure Element.
- Read the markup from the outer document structure inward and verify that each child is allowed in its parent context.
- Check the semantic meaning and any accessibility relationship such as labels, alternatives, headings, captions, or landmarks.
- Open the fragment in a browser and compare the rendered result with the source instead of assuming visual appearance proves validity.
- Validate the markup and test responsive, RTL, and no-JavaScript behavior where they apply.
Expected browser result: The browser displays or exposes the structure appropriate for figure Element while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for figure Element in Chapter 16. Validate it, remove one important attribute or related element to observe the difference, then restore the correct markup. Test the result with keyboard navigation when interactive, on a narrow screen, and in Arabic or Persian when the content can be translated.
16.2 figcaption Element
figcaption Element is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
For figcaption Element, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In figure content, the markup should remain understandable as a document before presentation is added.
In Chapter 16, a reliable way to learn figcaption Element is to write a small valid fragment, inspect the browser result and document outline, then test one incorrect or missing attribute. This makes the reason for each piece of markup visible instead of treating HTML as a collection of tags to memorize.
Concept in plain language
figcaption Element is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid photo story example that demonstrates figcaption Element. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 16, topic 2, example 1.
Example 2: Content variation
Change the text or resource used by figcaption Element in the support page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 16, topic 2, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the dashboard shell example using figcaption Element. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 16, topic 2, example 3.
Example 4: Accessibility review
Read the language page example using the semantics of figcaption Element. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 16, topic 2, example 4.
Example 5: Mobile review
Open the booking page markup containing figcaption Element on a narrow screen. Ensure embedded content, long text, controls, and translated labels do not force the page wider than the viewport. This is Chapter 16, topic 2, example 5.
Example 6: RTL review
Translate the media page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 16, topic 2, example 6.
Example 7: Validation exercise
Run the school page fragment using figcaption Element through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 16, topic 2, example 7.
Example 8: Progressive-enhancement check
Use figcaption Element in the course lesson so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 16, topic 2, example 8.
Example 9: SEO and semantics review
Inspect how figcaption Element contributes to the meaning of the news article. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 16, topic 2, example 9.
Example 10: Production review
Review figcaption Element in the contact page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 16, topic 2, example 10.
HTML code example
<figure>
<img src="/images/form-structure.webp" alt="Labeled HTML form structure" width="900" height="520">
<figcaption>Figure 1. Relationship between labels and controls.</figcaption>
</figure>Step-by-step code explanation
- Identify the element or attribute responsible for figcaption Element.
- Read the markup from the outer document structure inward and verify that each child is allowed in its parent context.
- Check the semantic meaning and any accessibility relationship such as labels, alternatives, headings, captions, or landmarks.
- Open the fragment in a browser and compare the rendered result with the source instead of assuming visual appearance proves validity.
- Validate the markup and test responsive, RTL, and no-JavaScript behavior where they apply.
Expected browser result: The browser displays or exposes the structure appropriate for figcaption Element while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for figcaption Element in Chapter 16. Validate it, remove one important attribute or related element to observe the difference, then restore the correct markup. Test the result with keyboard navigation when interactive, on a narrow screen, and in Arabic or Persian when the content can be translated.
16.3 Images with Captions
Images with Captions is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
For Images with Captions, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In figure content, the markup should remain understandable as a document before presentation is added.
In Chapter 16, a reliable way to learn Images with Captions is to write a small valid fragment, inspect the browser result and document outline, then test one incorrect or missing attribute. This makes the reason for each piece of markup visible instead of treating HTML as a collection of tags to memorize.
Concept in plain language
Images with Captions is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid dashboard shell example that demonstrates Images with Captions. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 16, topic 3, example 1.
Example 2: Content variation
Change the text or resource used by Images with Captions in the language page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 16, topic 3, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the booking page example using Images with Captions. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 16, topic 3, example 3.
Example 4: Accessibility review
Read the media page example using the semantics of Images with Captions. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 16, topic 3, example 4.
Example 5: Mobile review
Open the school page markup containing Images with Captions on a narrow screen. Ensure embedded content, long text, controls, and translated labels do not force the page wider than the viewport. This is Chapter 16, topic 3, example 5.
Example 6: RTL review
Translate the course lesson into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 16, topic 3, example 6.
Example 7: Validation exercise
Run the news article fragment using Images with Captions through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 16, topic 3, example 7.
Example 8: Progressive-enhancement check
Use Images with Captions in the contact page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 16, topic 3, example 8.
Example 9: SEO and semantics review
Inspect how Images with Captions contributes to the meaning of the product description. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 16, topic 3, example 9.
Example 10: Production review
Review Images with Captions in the profile page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 16, topic 3, example 10.
HTML code example
<video controls>
<source src="/media/lesson.mp4" type="video/mp4">
<track kind="captions" src="/media/en.vtt" srclang="en" label="English" default>
<track kind="subtitles" src="/media/fa.vtt" srclang="fa" label="فارسی">
</video>Step-by-step code explanation
- Identify the element or attribute responsible for Images with Captions.
- Read the markup from the outer document structure inward and verify that each child is allowed in its parent context.
- Check the semantic meaning and any accessibility relationship such as labels, alternatives, headings, captions, or landmarks.
- Open the fragment in a browser and compare the rendered result with the source instead of assuming visual appearance proves validity.
- Validate the markup and test responsive, RTL, and no-JavaScript behavior where they apply.
Expected browser result: The browser displays or exposes the structure appropriate for Images with Captions while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Images with Captions in Chapter 16. Validate it, remove one important attribute or related element to observe the difference, then restore the correct markup. Test the result with keyboard navigation when interactive, on a narrow screen, and in Arabic or Persian when the content can be translated.
16.4 Code Figures
Code Figures is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
For Code Figures, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In figure content, the markup should remain understandable as a document before presentation is added.
In Chapter 16, a reliable way to learn Code Figures is to write a small valid fragment, inspect the browser result and document outline, then test one incorrect or missing attribute. This makes the reason for each piece of markup visible instead of treating HTML as a collection of tags to memorize.
Concept in plain language
Code Figures is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid booking page example that demonstrates Code Figures. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 16, topic 4, example 1.
Example 2: Content variation
Change the text or resource used by Code Figures in the media page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 16, topic 4, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the school page example using Code Figures. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 16, topic 4, example 3.
Example 4: Accessibility review
Read the course lesson example using the semantics of Code Figures. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 16, topic 4, example 4.
Example 5: Mobile review
Open the news article markup containing Code Figures on a narrow screen. Ensure embedded content, long text, controls, and translated labels do not force the page wider than the viewport. This is Chapter 16, topic 4, example 5.
Example 6: RTL review
Translate the contact page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 16, topic 4, example 6.
Example 7: Validation exercise
Run the product description fragment using Code Figures through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 16, topic 4, example 7.
Example 8: Progressive-enhancement check
Use Code Figures in the profile page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 16, topic 4, example 8.
Example 9: SEO and semantics review
Inspect how Code Figures contributes to the meaning of the documentation page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 16, topic 4, example 9.
Example 10: Production review
Review Code Figures in the event page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 16, topic 4, example 10.
HTML code example
<figure>
<img src="/images/form-structure.webp" alt="Labeled HTML form structure" width="900" height="520">
<figcaption>Figure 1. Relationship between labels and controls.</figcaption>
</figure>Step-by-step code explanation
- Identify the element or attribute responsible for Code Figures.
- Read the markup from the outer document structure inward and verify that each child is allowed in its parent context.
- Check the semantic meaning and any accessibility relationship such as labels, alternatives, headings, captions, or landmarks.
- Open the fragment in a browser and compare the rendered result with the source instead of assuming visual appearance proves validity.
- Validate the markup and test responsive, RTL, and no-JavaScript behavior where they apply.
Expected browser result: The browser displays or exposes the structure appropriate for Code Figures while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Code Figures in Chapter 16. Validate it, remove one important attribute or related element to observe the difference, then restore the correct markup. Test the result with keyboard navigation when interactive, on a narrow screen, and in Arabic or Persian when the content can be translated.
16.5 Multiple Media in a Figure
Multiple Media in a Figure is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
For Multiple Media in a Figure, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In figure content, the markup should remain understandable as a document before presentation is added.
In Chapter 16, a reliable way to learn Multiple Media in a Figure is to write a small valid fragment, inspect the browser result and document outline, then test one incorrect or missing attribute. This makes the reason for each piece of markup visible instead of treating HTML as a collection of tags to memorize.
Concept in plain language
Multiple Media in a Figure is part of the HTML structure covered in Chapter 16. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid school page example that demonstrates Multiple Media in a Figure. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 16, topic 5, example 1.
Example 2: Content variation
Change the text or resource used by Multiple Media in a Figure in the course lesson. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 16, topic 5, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the news article example using Multiple Media in a Figure. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 16, topic 5, example 3.
Example 4: Accessibility review
Read the contact page example using the semantics of Multiple Media in a Figure. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 16, topic 5, example 4.
Example 5: Mobile review
Open the product description markup containing Multiple Media in a Figure on a narrow screen. Ensure embedded content, long text, controls, and translated labels do not force the page wider than the viewport. This is Chapter 16, topic 5, example 5.
Example 6: RTL review
Translate the profile page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 16, topic 5, example 6.
Example 7: Validation exercise
Run the documentation page fragment using Multiple Media in a Figure through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 16, topic 5, example 7.
Example 8: Progressive-enhancement check
Use Multiple Media in a Figure in the event page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 16, topic 5, example 8.
Example 9: SEO and semantics review
Inspect how Multiple Media in a Figure contributes to the meaning of the FAQ page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 16, topic 5, example 9.
Example 10: Production review
Review Multiple Media in a Figure in the photo story for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 16, topic 5, example 10.
HTML code example
<figure>
<img src="/images/form-structure.webp" alt="Labeled HTML form structure" width="900" height="520">
<figcaption>Figure 1. Relationship between labels and controls.</figcaption>
</figure>Step-by-step code explanation
- Identify the element or attribute responsible for Multiple Media in a Figure.
- Read the markup from the outer document structure inward and verify that each child is allowed in its parent context.
- Check the semantic meaning and any accessibility relationship such as labels, alternatives, headings, captions, or landmarks.
- Open the fragment in a browser and compare the rendered result with the source instead of assuming visual appearance proves validity.
- Validate the markup and test responsive, RTL, and no-JavaScript behavior where they apply.
Expected browser result: The browser displays or exposes the structure appropriate for Multiple Media in a Figure while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Multiple Media in a Figure in Chapter 16. Validate it, remove one important attribute or related element to observe the difference, then restore the correct markup. Test the result with keyboard navigation when interactive, on a narrow screen, and in Arabic or Persian when the content can be translated.
Chapter 16 review — 10 questions and answers
1. What should you check first when using figure Element?
Answer: Check that the markup for figure Element matches the meaning of the content, is valid in its context, and does not depend on visual styling to communicate essential information.
2. How do you review figure Element before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that figure Element adds real document meaning or browser behavior.
3. What should you check first when using figcaption Element?
Answer: Check that the markup for figcaption Element matches the meaning of the content, is valid in its context, and does not depend on visual styling to communicate essential information.
4. How do you review figcaption Element before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that figcaption Element adds real document meaning or browser behavior.
5. What should you check first when using Images with Captions?
Answer: Check that the markup for Images with Captions matches the meaning of the content, is valid in its context, and does not depend on visual styling to communicate essential information.
6. How do you review Images with Captions before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Images with Captions adds real document meaning or browser behavior.
7. What should you check first when using Code Figures?
Answer: Check that the markup for Code Figures matches the meaning of the content, is valid in its context, and does not depend on visual styling to communicate essential information.
8. How do you review Code Figures before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Code Figures adds real document meaning or browser behavior.
9. What should you check first when using Multiple Media in a Figure?
Answer: Check that the markup for Multiple Media in a Figure matches the meaning of the content, is valid in its context, and does not depend on visual styling to communicate essential information.
10. How do you review Multiple Media in a Figure before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Multiple Media in a Figure adds real document meaning or browser behavior.