HTML • Chapter 44 • Foundations to Production
Accessible Images and Media
Each topic contains substantial explanation, ten focused teaching examples, its own HTML code example, code reasoning, expected browser result, and practice.
44.1 Informative Alt Text
Informative Alt Text is part of the HTML structure covered in Chapter 44. 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 Informative 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 accessible images and media, the markup should remain understandable as a document before presentation is added.
In Chapter 44, a reliable way to learn Informative 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
Informative Alt Text is part of the HTML structure covered in Chapter 44. 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 Informative Alt Text. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 44, topic 1, example 1.
Example 2: Content variation
Change the text or resource used by Informative Alt Text in the school page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 44, topic 1, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the course lesson example using Informative Alt Text. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 44, topic 1, example 3.
Example 4: Accessibility review
Read the news article example using the semantics of Informative Alt Text. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 44, topic 1, example 4.
Example 5: Mobile review
Open the contact page markup containing Informative 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 44, 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 44, topic 1, example 6.
Example 7: Validation exercise
Run the profile page fragment using Informative Alt Text through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 44, topic 1, example 7.
Example 8: Progressive-enhancement check
Use Informative Alt Text 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 44, topic 1, example 8.
Example 9: SEO and semantics review
Inspect how Informative Alt Text 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 44, topic 1, example 9.
Example 10: Production review
Review Informative Alt Text in the FAQ page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 44, 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 Informative 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 Informative Alt Text while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Informative Alt Text in Chapter 44. 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.
44.2 Decorative Images
Decorative Images is part of the HTML structure covered in Chapter 44. 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 Decorative Images, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessible images and media, the markup should remain understandable as a document before presentation is added.
In Chapter 44, a reliable way to learn Decorative Images 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
Decorative Images is part of the HTML structure covered in Chapter 44. 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 Decorative Images. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 44, topic 2, example 1.
Example 2: Content variation
Change the text or resource used by Decorative Images in the news article. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 44, topic 2, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the contact page example using Decorative Images. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 44, topic 2, example 3.
Example 4: Accessibility review
Read the product description example using the semantics of Decorative Images. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 44, topic 2, example 4.
Example 5: Mobile review
Open the profile page markup containing Decorative Images 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 44, 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 44, topic 2, example 6.
Example 7: Validation exercise
Run the event page fragment using Decorative Images through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 44, topic 2, example 7.
Example 8: Progressive-enhancement check
Use Decorative Images 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 44, topic 2, example 8.
Example 9: SEO and semantics review
Inspect how Decorative Images 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 44, topic 2, example 9.
Example 10: Production review
Review Decorative Images in the support page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 44, topic 2, example 10.
HTML code example
<section id="decorative-images">
<h2>Decorative Images</h2>
<p>This HTML fragment demonstrates the document structure for Decorative Images.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for Decorative Images.
- 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 Decorative Images while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Decorative Images in Chapter 44. 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.
44.3 Captions and Subtitles
Captions and Subtitles is part of the HTML structure covered in Chapter 44. 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 Captions and Subtitles, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessible images and media, the markup should remain understandable as a document before presentation is added.
In Chapter 44, a reliable way to learn Captions and Subtitles 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
Captions and Subtitles is part of the HTML structure covered in Chapter 44. 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 Captions and Subtitles. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 44, topic 3, example 1.
Example 2: Content variation
Change the text or resource used by Captions and Subtitles in the product description. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 44, topic 3, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the profile page example using Captions and Subtitles. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 44, topic 3, example 3.
Example 4: Accessibility review
Read the documentation page example using the semantics of Captions and Subtitles. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 44, topic 3, example 4.
Example 5: Mobile review
Open the event page markup containing Captions and Subtitles 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 44, 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 44, topic 3, example 6.
Example 7: Validation exercise
Run the photo story fragment using Captions and Subtitles through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 44, topic 3, example 7.
Example 8: Progressive-enhancement check
Use Captions and Subtitles 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 44, topic 3, example 8.
Example 9: SEO and semantics review
Inspect how Captions and Subtitles 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 44, topic 3, example 9.
Example 10: Production review
Review Captions and Subtitles in the language page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 44, 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 Captions and Subtitles.
- 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 Captions and Subtitles while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Captions and Subtitles in Chapter 44. 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.
44.4 Audio Alternatives
Audio Alternatives is part of the HTML structure covered in Chapter 44. 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 Audio Alternatives, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessible images and media, the markup should remain understandable as a document before presentation is added.
In Chapter 44, a reliable way to learn Audio Alternatives 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
Audio Alternatives is part of the HTML structure covered in Chapter 44. 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 Audio Alternatives. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 44, topic 4, example 1.
Example 2: Content variation
Change the text or resource used by Audio Alternatives in the documentation page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 44, topic 4, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the event page example using Audio Alternatives. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 44, topic 4, example 3.
Example 4: Accessibility review
Read the FAQ page example using the semantics of Audio Alternatives. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 44, topic 4, example 4.
Example 5: Mobile review
Open the photo story markup containing Audio Alternatives 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 44, 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 44, topic 4, example 6.
Example 7: Validation exercise
Run the dashboard shell fragment using Audio Alternatives through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 44, topic 4, example 7.
Example 8: Progressive-enhancement check
Use Audio Alternatives 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 44, topic 4, example 8.
Example 9: SEO and semantics review
Inspect how Audio Alternatives 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 44, topic 4, example 9.
Example 10: Production review
Review Audio Alternatives in the media page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 44, topic 4, 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 Audio Alternatives.
- 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 Audio Alternatives while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Audio Alternatives in Chapter 44. 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.
44.5 Avoiding Text inside Images
Avoiding Text inside Images is part of the HTML structure covered in Chapter 44. 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 Avoiding Text inside Images, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessible images and media, the markup should remain understandable as a document before presentation is added.
In Chapter 44, a reliable way to learn Avoiding Text inside Images 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
Avoiding Text inside Images is part of the HTML structure covered in Chapter 44. 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 Avoiding Text inside Images. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 44, topic 5, example 1.
Example 2: Content variation
Change the text or resource used by Avoiding Text inside Images in the FAQ page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 44, topic 5, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the photo story example using Avoiding Text inside Images. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 44, topic 5, example 3.
Example 4: Accessibility review
Read the support page example using the semantics of Avoiding Text inside Images. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 44, topic 5, example 4.
Example 5: Mobile review
Open the dashboard shell markup containing Avoiding Text inside Images 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 44, 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 44, topic 5, example 6.
Example 7: Validation exercise
Run the booking page fragment using Avoiding Text inside Images through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 44, topic 5, example 7.
Example 8: Progressive-enhancement check
Use Avoiding Text inside Images 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 44, topic 5, example 8.
Example 9: SEO and semantics review
Inspect how Avoiding Text inside Images 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 44, topic 5, example 9.
Example 10: Production review
Review Avoiding Text inside Images in the course lesson for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 44, topic 5, example 10.
HTML code example
<section id="avoiding-text-inside-images">
<h2>Avoiding Text inside Images</h2>
<p>This HTML fragment demonstrates the document structure for Avoiding Text inside Images.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for Avoiding Text inside Images.
- 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 Avoiding Text inside Images while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Avoiding Text inside Images in Chapter 44. 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 44 review — 10 questions and answers
1. What should you check first when using Informative Alt Text?
Answer: Check that the markup for Informative Alt Text 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 Informative Alt Text before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Informative Alt Text adds real document meaning or browser behavior.
3. What should you check first when using Decorative Images?
Answer: Check that the markup for Decorative Images 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 Decorative Images before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Decorative Images adds real document meaning or browser behavior.
5. What should you check first when using Captions and Subtitles?
Answer: Check that the markup for Captions and Subtitles 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 Captions and Subtitles before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Captions and Subtitles adds real document meaning or browser behavior.
7. What should you check first when using Audio Alternatives?
Answer: Check that the markup for Audio Alternatives 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 Audio Alternatives before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Audio Alternatives adds real document meaning or browser behavior.
9. What should you check first when using Avoiding Text inside Images?
Answer: Check that the markup for Avoiding Text inside Images 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 Avoiding Text inside Images before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Avoiding Text inside Images adds real document meaning or browser behavior.