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