HTML • Chapter 43 • Foundations to Production
Accessibility Foundations
Each topic contains substantial explanation, ten focused teaching examples, its own HTML code example, code reasoning, expected browser result, and practice.
43.1 Document Language
Document Language is part of the HTML structure covered in Chapter 43. 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 Document Language, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessibility foundations, the markup should remain understandable as a document before presentation is added.
In Chapter 43, a reliable way to learn Document Language 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
Document Language is part of the HTML structure covered in Chapter 43. 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 support page example that demonstrates Document Language. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 43, topic 1, example 1.
Example 2: Content variation
Change the text or resource used by Document Language in the dashboard shell. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 43, topic 1, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the language page example using Document Language. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 43, topic 1, example 3.
Example 4: Accessibility review
Read the booking page example using the semantics of Document Language. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 43, topic 1, example 4.
Example 5: Mobile review
Open the media page markup containing Document Language 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 43, topic 1, example 5.
Example 6: RTL review
Translate the school 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 43, topic 1, example 6.
Example 7: Validation exercise
Run the course lesson fragment using Document Language through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 43, topic 1, example 7.
Example 8: Progressive-enhancement check
Use Document Language in the news article so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 43, topic 1, example 8.
Example 9: SEO and semantics review
Inspect how Document Language contributes to the meaning of the contact page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 43, topic 1, example 9.
Example 10: Production review
Review Document Language in the product description for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 43, topic 1, example 10.
HTML code example
<section id="document-language">
<h2>Document Language</h2>
<p>This HTML fragment demonstrates the document structure for Document Language.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for Document Language.
- 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 Document Language while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Document Language in Chapter 43. 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.
43.2 Landmark Elements
Landmark Elements is part of the HTML structure covered in Chapter 43. 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 Landmark Elements, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessibility foundations, the markup should remain understandable as a document before presentation is added.
In Chapter 43, a reliable way to learn Landmark Elements 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
Landmark Elements is part of the HTML structure covered in Chapter 43. 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 Landmark Elements. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 43, topic 2, example 1.
Example 2: Content variation
Change the text or resource used by Landmark Elements in the booking page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 43, topic 2, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the media page example using Landmark Elements. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 43, topic 2, example 3.
Example 4: Accessibility review
Read the school page example using the semantics of Landmark Elements. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 43, topic 2, example 4.
Example 5: Mobile review
Open the course lesson markup containing Landmark Elements 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 43, topic 2, 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 43, topic 2, example 6.
Example 7: Validation exercise
Run the contact page fragment using Landmark Elements through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 43, topic 2, example 7.
Example 8: Progressive-enhancement check
Use Landmark Elements 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 43, topic 2, example 8.
Example 9: SEO and semantics review
Inspect how Landmark Elements 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 43, topic 2, example 9.
Example 10: Production review
Review Landmark Elements in the documentation page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 43, 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 Landmark Elements.
- 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 Landmark Elements while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Landmark Elements in Chapter 43. 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.
43.3 Accessible Names
Accessible Names is part of the HTML structure covered in Chapter 43. 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 Accessible Names, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessibility foundations, the markup should remain understandable as a document before presentation is added.
In Chapter 43, a reliable way to learn Accessible Names 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
Accessible Names is part of the HTML structure covered in Chapter 43. 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 Accessible Names. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 43, topic 3, example 1.
Example 2: Content variation
Change the text or resource used by Accessible Names in the school page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 43, topic 3, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the course lesson example using Accessible Names. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 43, topic 3, example 3.
Example 4: Accessibility review
Read the news article example using the semantics of Accessible Names. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 43, topic 3, example 4.
Example 5: Mobile review
Open the contact page markup containing Accessible Names 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 43, topic 3, 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 43, topic 3, example 6.
Example 7: Validation exercise
Run the profile page fragment using Accessible Names through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 43, topic 3, example 7.
Example 8: Progressive-enhancement check
Use Accessible Names 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 43, topic 3, example 8.
Example 9: SEO and semantics review
Inspect how Accessible Names 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 43, topic 3, example 9.
Example 10: Production review
Review Accessible Names in the FAQ page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 43, topic 3, example 10.
HTML code example
<section id="accessible-names">
<h2>Accessible Names</h2>
<p>This HTML fragment demonstrates the document structure for Accessible Names.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for Accessible Names.
- 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 Accessible Names while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Accessible Names in Chapter 43. 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.
43.4 Keyboard-Friendly Native Controls
Keyboard-Friendly Native Controls is part of the HTML structure covered in Chapter 43. 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 Keyboard-Friendly Native Controls, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessibility foundations, the markup should remain understandable as a document before presentation is added.
In Chapter 43, a reliable way to learn Keyboard-Friendly Native Controls 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
Keyboard-Friendly Native Controls is part of the HTML structure covered in Chapter 43. 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 Keyboard-Friendly Native Controls. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 43, topic 4, example 1.
Example 2: Content variation
Change the text or resource used by Keyboard-Friendly Native Controls in the news article. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 43, topic 4, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the contact page example using Keyboard-Friendly Native Controls. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 43, topic 4, example 3.
Example 4: Accessibility review
Read the product description example using the semantics of Keyboard-Friendly Native Controls. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 43, topic 4, example 4.
Example 5: Mobile review
Open the profile page markup containing Keyboard-Friendly Native Controls 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 43, topic 4, 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 43, topic 4, example 6.
Example 7: Validation exercise
Run the event page fragment using Keyboard-Friendly Native Controls through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 43, topic 4, example 7.
Example 8: Progressive-enhancement check
Use Keyboard-Friendly Native Controls 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 43, topic 4, example 8.
Example 9: SEO and semantics review
Inspect how Keyboard-Friendly Native Controls 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 43, topic 4, example 9.
Example 10: Production review
Review Keyboard-Friendly Native Controls in the support page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 43, topic 4, example 10.
HTML code example
<section id="keyboard-friendly-native-controls">
<h2>Keyboard-Friendly Native Controls</h2>
<p>This HTML fragment demonstrates the document structure for Keyboard-Friendly Native Controls.</p>
</section>Step-by-step code explanation
- Identify the element or attribute responsible for Keyboard-Friendly Native Controls.
- 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 Keyboard-Friendly Native Controls while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Keyboard-Friendly Native Controls in Chapter 43. 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.
43.5 Meaningful Link Text
Meaningful Link Text is part of the HTML structure covered in Chapter 43. 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 Meaningful Link Text, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In accessibility foundations, the markup should remain understandable as a document before presentation is added.
In Chapter 43, a reliable way to learn Meaningful Link 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
Meaningful Link Text is part of the HTML structure covered in Chapter 43. 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 Meaningful Link Text. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 43, topic 5, example 1.
Example 2: Content variation
Change the text or resource used by Meaningful Link 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 43, topic 5, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the profile page example using Meaningful Link Text. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 43, topic 5, example 3.
Example 4: Accessibility review
Read the documentation page example using the semantics of Meaningful Link Text. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 43, topic 5, example 4.
Example 5: Mobile review
Open the event page markup containing Meaningful Link 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 43, topic 5, 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 43, topic 5, example 6.
Example 7: Validation exercise
Run the photo story fragment using Meaningful Link Text through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 43, topic 5, example 7.
Example 8: Progressive-enhancement check
Use Meaningful Link 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 43, topic 5, example 8.
Example 9: SEO and semantics review
Inspect how Meaningful Link 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 43, topic 5, example 9.
Example 10: Production review
Review Meaningful Link Text in the language page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 43, topic 5, example 10.
HTML code example
<nav aria-label="Course navigation">
<a href="./ch-2.html">Next chapter</a>
<a href="https://example.com/" target="_blank" rel="noopener noreferrer">External reference</a>
</nav>Step-by-step code explanation
- Identify the element or attribute responsible for Meaningful Link 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 Meaningful Link Text while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Meaningful Link Text in Chapter 43. 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 43 review — 10 questions and answers
1. What should you check first when using Document Language?
Answer: Check that the markup for Document Language 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 Document Language before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Document Language adds real document meaning or browser behavior.
3. What should you check first when using Landmark Elements?
Answer: Check that the markup for Landmark Elements 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 Landmark Elements before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Landmark Elements adds real document meaning or browser behavior.
5. What should you check first when using Accessible Names?
Answer: Check that the markup for Accessible Names 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 Accessible Names before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Accessible Names adds real document meaning or browser behavior.
7. What should you check first when using Keyboard-Friendly Native Controls?
Answer: Check that the markup for Keyboard-Friendly Native Controls 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 Keyboard-Friendly Native Controls before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Keyboard-Friendly Native Controls adds real document meaning or browser behavior.
9. What should you check first when using Meaningful Link Text?
Answer: Check that the markup for Meaningful Link Text 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 Meaningful Link Text before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Meaningful Link Text adds real document meaning or browser behavior.