HTML • Chapter 14 • Foundations to Production
Images
Each topic contains substantial explanation, ten focused teaching examples, its own HTML code example, code reasoning, expected browser result, and practice.
14.1 img Element
img Element is part of the HTML structure covered in Chapter 14. 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 img Element, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In images, the markup should remain understandable as a document before presentation is added.
In Chapter 14, a reliable way to learn img 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
img Element is part of the HTML structure covered in Chapter 14. 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 media page example that demonstrates img Element. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 14, topic 1, example 1.
Example 2: Content variation
Change the text or resource used by img Element in the school page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 14, topic 1, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the course lesson example using img Element. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 14, topic 1, example 3.
Example 4: Accessibility review
Read the news article example using the semantics of img Element. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 14, topic 1, example 4.
Example 5: Mobile review
Open the contact page markup containing img 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 14, topic 1, example 5.
Example 6: RTL review
Translate the product description into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 14, topic 1, example 6.
Example 7: Validation exercise
Run the profile page fragment using img Element through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 14, topic 1, example 7.
Example 8: Progressive-enhancement check
Use img Element in the documentation page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 14, topic 1, example 8.
Example 9: SEO and semantics review
Inspect how img Element contributes to the meaning of the event page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 14, topic 1, example 9.
Example 10: Production review
Review img Element in the FAQ page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 14, topic 1, example 10.
HTML code example
<img src="/images/course-diagram.webp" alt="Diagram showing the parts of an HTML document" width="800" height="450" loading="lazy" decoding="async">Step-by-step code explanation
- Identify the element or attribute responsible for img 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 img Element while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for img Element in Chapter 14. 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.
14.2 src Attribute
src Attribute is part of the HTML structure covered in Chapter 14. 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 src Attribute, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In images, the markup should remain understandable as a document before presentation is added.
In Chapter 14, a reliable way to learn src Attribute 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
src Attribute is part of the HTML structure covered in Chapter 14. 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 course lesson example that demonstrates src Attribute. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 14, topic 2, example 1.
Example 2: Content variation
Change the text or resource used by src Attribute in the news article. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 14, topic 2, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the contact page example using src Attribute. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 14, topic 2, example 3.
Example 4: Accessibility review
Read the product description example using the semantics of src Attribute. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 14, topic 2, example 4.
Example 5: Mobile review
Open the profile page markup containing src Attribute 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 14, topic 2, example 5.
Example 6: RTL review
Translate the documentation 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 14, topic 2, example 6.
Example 7: Validation exercise
Run the event page fragment using src Attribute through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 14, topic 2, example 7.
Example 8: Progressive-enhancement check
Use src Attribute in the FAQ page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 14, topic 2, example 8.
Example 9: SEO and semantics review
Inspect how src Attribute contributes to the meaning of the photo story. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 14, topic 2, example 9.
Example 10: Production review
Review src Attribute in the support page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 14, topic 2, example 10.
HTML code example
<section id="src-attribute">
<h2>src Attribute</h2>
<p>This HTML fragment demonstrates the document structure for src Attribute.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for src Attribute.
- 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 src Attribute while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for src Attribute in Chapter 14. 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.
14.3 alt Text
alt Text is part of the HTML structure covered in Chapter 14. 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 alt Text, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In images, the markup should remain understandable as a document before presentation is added.
In Chapter 14, a reliable way to learn alt Text 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
alt Text is part of the HTML structure covered in Chapter 14. 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 contact page example that demonstrates alt Text. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 14, topic 3, example 1.
Example 2: Content variation
Change the text or resource used by alt Text in the product description. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 14, topic 3, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the profile page example using alt Text. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 14, topic 3, example 3.
Example 4: Accessibility review
Read the documentation page example using the semantics of alt Text. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 14, topic 3, example 4.
Example 5: Mobile review
Open the event page markup containing alt Text 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 14, topic 3, example 5.
Example 6: RTL review
Translate the FAQ 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 14, topic 3, example 6.
Example 7: Validation exercise
Run the photo story fragment using alt Text through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 14, topic 3, example 7.
Example 8: Progressive-enhancement check
Use alt Text in the support page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 14, topic 3, example 8.
Example 9: SEO and semantics review
Inspect how alt Text contributes to the meaning of the dashboard shell. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 14, topic 3, example 9.
Example 10: Production review
Review alt Text in the language page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 14, topic 3, example 10.
HTML code example
<img src="/images/course-diagram.webp" alt="Diagram showing the parts of an HTML document" width="800" height="450" loading="lazy" decoding="async">Step-by-step code explanation
- Identify the element or attribute responsible for alt Text.
- 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 alt Text while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for alt Text in Chapter 14. 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.
14.4 width and height
width and height is part of the HTML structure covered in Chapter 14. 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 width and height, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In images, the markup should remain understandable as a document before presentation is added.
In Chapter 14, a reliable way to learn width and height 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
width and height is part of the HTML structure covered in Chapter 14. 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 profile page example that demonstrates width and height. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 14, topic 4, example 1.
Example 2: Content variation
Change the text or resource used by width and height in the documentation page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 14, topic 4, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the event page example using width and height. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 14, topic 4, example 3.
Example 4: Accessibility review
Read the FAQ page example using the semantics of width and height. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 14, topic 4, example 4.
Example 5: Mobile review
Open the photo story markup containing width and height 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 14, topic 4, example 5.
Example 6: RTL review
Translate the support 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 14, topic 4, example 6.
Example 7: Validation exercise
Run the dashboard shell fragment using width and height through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 14, topic 4, example 7.
Example 8: Progressive-enhancement check
Use width and height in the language page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 14, topic 4, example 8.
Example 9: SEO and semantics review
Inspect how width and height contributes to the meaning of the booking page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 14, topic 4, example 9.
Example 10: Production review
Review width and height in the media page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 14, topic 4, example 10.
HTML code example
<section id="width-and-height">
<h2>width and height</h2>
<p>This HTML fragment demonstrates the document structure for width and height.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for width and height.
- 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 width and height while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for width and height in Chapter 14. 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.
14.5 loading and decoding
loading and decoding is part of the HTML structure covered in Chapter 14. 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 loading and decoding, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In images, the markup should remain understandable as a document before presentation is added.
In Chapter 14, a reliable way to learn loading and decoding 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
loading and decoding is part of the HTML structure covered in Chapter 14. 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 loading and decoding. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 14, topic 5, example 1.
Example 2: Content variation
Change the text or resource used by loading and decoding in the FAQ page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 14, topic 5, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the photo story example using loading and decoding. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 14, topic 5, example 3.
Example 4: Accessibility review
Read the support page example using the semantics of loading and decoding. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 14, topic 5, example 4.
Example 5: Mobile review
Open the dashboard shell markup containing loading and decoding 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 14, topic 5, 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 14, topic 5, example 6.
Example 7: Validation exercise
Run the booking page fragment using loading and decoding through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 14, topic 5, example 7.
Example 8: Progressive-enhancement check
Use loading and decoding 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 14, topic 5, example 8.
Example 9: SEO and semantics review
Inspect how loading and decoding 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 14, topic 5, example 9.
Example 10: Production review
Review loading and decoding in the course lesson for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 14, topic 5, example 10.
HTML code example
<img src="/images/course-diagram.webp" alt="Diagram showing the parts of an HTML document" width="800" height="450" loading="lazy" decoding="async">Step-by-step code explanation
- Identify the element or attribute responsible for loading and decoding.
- 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 loading and decoding while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for loading and decoding in Chapter 14. 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 14 review — 10 questions and answers
1. What should you check first when using img Element?
Answer: Check that the markup for img 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 img Element before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that img Element adds real document meaning or browser behavior.
3. What should you check first when using src Attribute?
Answer: Check that the markup for src Attribute 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 src Attribute before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that src Attribute adds real document meaning or browser behavior.
5. What should you check first when using alt Text?
Answer: Check that the markup for alt Text 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 alt Text before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that alt Text adds real document meaning or browser behavior.
7. What should you check first when using width and height?
Answer: Check that the markup for width and height 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 width and height before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that width and height adds real document meaning or browser behavior.
9. What should you check first when using loading and decoding?
Answer: Check that the markup for loading and decoding 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 loading and decoding before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that loading and decoding adds real document meaning or browser behavior.