HTML • Chapter 47 • Foundations to Production
Structured Data in HTML
Each topic contains substantial explanation, ten focused teaching examples, its own HTML code example, code reasoning, expected browser result, and practice.
47.1 JSON-LD Script
JSON-LD Script is part of the HTML structure covered in Chapter 47. 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 JSON-LD Script, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In structured data in html, the markup should remain understandable as a document before presentation is added.
In Chapter 47, a reliable way to learn JSON-LD Script 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
JSON-LD Script is part of the HTML structure covered in Chapter 47. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid dashboard shell example that demonstrates JSON-LD Script. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 47, topic 1, example 1.
Example 2: Content variation
Change the text or resource used by JSON-LD Script in the language page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 47, topic 1, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the booking page example using JSON-LD Script. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 47, topic 1, example 3.
Example 4: Accessibility review
Read the media page example using the semantics of JSON-LD Script. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 47, topic 1, example 4.
Example 5: Mobile review
Open the school page markup containing JSON-LD Script 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 47, topic 1, example 5.
Example 6: RTL review
Translate the course lesson into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 47, topic 1, example 6.
Example 7: Validation exercise
Run the news article fragment using JSON-LD Script through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 47, topic 1, example 7.
Example 8: Progressive-enhancement check
Use JSON-LD Script in the contact page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 47, topic 1, example 8.
Example 9: SEO and semantics review
Inspect how JSON-LD Script contributes to the meaning of the product description. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 47, topic 1, example 9.
Example 10: Production review
Review JSON-LD Script in the profile page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 47, topic 1, example 10.
HTML code example
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LearningResource",
"name": "HTML Forms Lesson",
"isAccessibleForFree": true
}
</script>Step-by-step code explanation
- Identify the element or attribute responsible for JSON-LD Script.
- 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 JSON-LD Script while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for JSON-LD Script in Chapter 47. 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.
47.2 Schema Context
Schema Context is part of the HTML structure covered in Chapter 47. 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 Schema Context, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In structured data in html, the markup should remain understandable as a document before presentation is added.
In Chapter 47, a reliable way to learn Schema Context 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
Schema Context is part of the HTML structure covered in Chapter 47. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid booking page example that demonstrates Schema Context. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 47, topic 2, example 1.
Example 2: Content variation
Change the text or resource used by Schema Context in the media page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 47, topic 2, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the school page example using Schema Context. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 47, topic 2, example 3.
Example 4: Accessibility review
Read the course lesson example using the semantics of Schema Context. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 47, topic 2, example 4.
Example 5: Mobile review
Open the news article markup containing Schema Context 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 47, topic 2, example 5.
Example 6: RTL review
Translate the contact page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 47, topic 2, example 6.
Example 7: Validation exercise
Run the product description fragment using Schema Context through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 47, topic 2, example 7.
Example 8: Progressive-enhancement check
Use Schema Context in the profile page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 47, topic 2, example 8.
Example 9: SEO and semantics review
Inspect how Schema Context contributes to the meaning of the documentation page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 47, topic 2, example 9.
Example 10: Production review
Review Schema Context in the event page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 47, topic 2, example 10.
HTML code example
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LearningResource",
"name": "HTML Forms Lesson",
"isAccessibleForFree": true
}
</script>Step-by-step code explanation
- Identify the element or attribute responsible for Schema Context.
- 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 Schema Context while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Schema Context in Chapter 47. 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.
47.3 Article Markup
Article Markup is part of the HTML structure covered in Chapter 47. 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 Article Markup, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In structured data in html, the markup should remain understandable as a document before presentation is added.
In Chapter 47, a reliable way to learn Article Markup 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
Article Markup is part of the HTML structure covered in Chapter 47. HTML communicates meaning and document relationships to browsers, search engines, assistive technology, and other tools, so the choice of element or attribute should match the content rather than only its visual appearance.
10 teaching examples
Example 1: Minimal markup
Create the smallest valid school page example that demonstrates Article Markup. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 47, topic 3, example 1.
Example 2: Content variation
Change the text or resource used by Article Markup in the course lesson. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 47, topic 3, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the news article example using Article Markup. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 47, topic 3, example 3.
Example 4: Accessibility review
Read the contact page example using the semantics of Article Markup. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 47, topic 3, example 4.
Example 5: Mobile review
Open the product description markup containing Article Markup 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 47, topic 3, example 5.
Example 6: RTL review
Translate the profile page into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 47, topic 3, example 6.
Example 7: Validation exercise
Run the documentation page fragment using Article Markup through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 47, topic 3, example 7.
Example 8: Progressive-enhancement check
Use Article Markup in the event page so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 47, topic 3, example 8.
Example 9: SEO and semantics review
Inspect how Article Markup contributes to the meaning of the FAQ page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 47, topic 3, example 9.
Example 10: Production review
Review Article Markup in the photo story for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 47, 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 Article Markup.
- 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 Article Markup while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Article Markup in Chapter 47. 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.
47.4 Breadcrumb Markup
Breadcrumb Markup is part of the HTML structure covered in Chapter 47. 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 Breadcrumb Markup, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In structured data in html, the markup should remain understandable as a document before presentation is added.
In Chapter 47, a reliable way to learn Breadcrumb Markup 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
Breadcrumb Markup is part of the HTML structure covered in Chapter 47. 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 news article example that demonstrates Breadcrumb Markup. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 47, topic 4, example 1.
Example 2: Content variation
Change the text or resource used by Breadcrumb Markup in the contact page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 47, topic 4, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the product description example using Breadcrumb Markup. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 47, topic 4, example 3.
Example 4: Accessibility review
Read the profile page example using the semantics of Breadcrumb Markup. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 47, topic 4, example 4.
Example 5: Mobile review
Open the documentation page markup containing Breadcrumb Markup 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 47, topic 4, example 5.
Example 6: RTL review
Translate the event 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 47, topic 4, example 6.
Example 7: Validation exercise
Run the FAQ page fragment using Breadcrumb Markup through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 47, topic 4, example 7.
Example 8: Progressive-enhancement check
Use Breadcrumb Markup in the photo story so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 47, topic 4, example 8.
Example 9: SEO and semantics review
Inspect how Breadcrumb Markup contributes to the meaning of the support page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 47, topic 4, example 9.
Example 10: Production review
Review Breadcrumb Markup in the dashboard shell for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 47, 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 Breadcrumb Markup.
- 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 Breadcrumb Markup while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Breadcrumb Markup in Chapter 47. 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.
47.5 Validating Structured Data
Validating Structured Data is part of the HTML structure covered in Chapter 47. 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 Validating Structured Data, examine the element's permitted content, relevant attributes, semantic meaning, accessibility effect, and how it behaves when CSS or JavaScript is unavailable. In structured data in html, the markup should remain understandable as a document before presentation is added.
In Chapter 47, a reliable way to learn Validating Structured Data 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
Validating Structured Data is part of the HTML structure covered in Chapter 47. 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 product description example that demonstrates Validating Structured Data. Identify which part carries meaning and which parts are only supporting structure. This is Chapter 47, topic 5, example 1.
Example 2: Content variation
Change the text or resource used by Validating Structured Data in the profile page. Confirm that the markup still describes the new content correctly instead of depending on the old wording. This is Chapter 47, topic 5, example 2.
Example 3: Missing-information test
Remove one important attribute or related element from the documentation page example using Validating Structured Data. Explain what meaning, accessibility, navigation, or browser behavior is lost. This is Chapter 47, topic 5, example 3.
Example 4: Accessibility review
Read the event page example using the semantics of Validating Structured Data. Check names, labels, landmarks, alternatives, focus behavior, and whether the content still makes sense without styling. This is Chapter 47, topic 5, example 4.
Example 5: Mobile review
Open the FAQ page markup containing Validating Structured Data 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 47, topic 5, example 5.
Example 6: RTL review
Translate the photo story into Arabic or Persian. Keep document text RTL where appropriate while URLs, code samples, numbers, and intentionally LTR fragments remain readable. This is Chapter 47, topic 5, example 6.
Example 7: Validation exercise
Run the support page fragment using Validating Structured Data through an HTML validator. Fix invalid nesting, duplicate IDs, missing required attributes, or obsolete markup before adding extra features. This is Chapter 47, topic 5, example 7.
Example 8: Progressive-enhancement check
Use Validating Structured Data in the dashboard shell so the core content remains useful before CSS and JavaScript load. Add enhancement only after the document structure is complete. This is Chapter 47, topic 5, example 8.
Example 9: SEO and semantics review
Inspect how Validating Structured Data contributes to the meaning of the language page. Keep headings, links, metadata, and document regions consistent so crawlers and users receive the same primary content. This is Chapter 47, topic 5, example 9.
Example 10: Production review
Review Validating Structured Data in the booking page for validity, accessibility, security-related attributes, performance hints, responsive behavior, localization, and maintainability. This is Chapter 47, topic 5, example 10.
HTML code example
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LearningResource",
"name": "HTML Forms Lesson",
"isAccessibleForFree": true
}
</script>Step-by-step code explanation
- Identify the element or attribute responsible for Validating Structured Data.
- 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 Validating Structured Data while preserving the semantic relationships expressed by the markup.
Practice exercise
Write a fresh HTML fragment for Validating Structured Data in Chapter 47. 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 47 review — 10 questions and answers
1. What should you check first when using JSON-LD Script?
Answer: Check that the markup for JSON-LD Script 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 JSON-LD Script before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that JSON-LD Script adds real document meaning or browser behavior.
3. What should you check first when using Schema Context?
Answer: Check that the markup for Schema Context 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 Schema Context before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Schema Context adds real document meaning or browser behavior.
5. What should you check first when using Article Markup?
Answer: Check that the markup for Article Markup 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 Article Markup before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Article Markup adds real document meaning or browser behavior.
7. What should you check first when using Breadcrumb Markup?
Answer: Check that the markup for Breadcrumb Markup 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 Breadcrumb Markup before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Breadcrumb Markup adds real document meaning or browser behavior.
9. What should you check first when using Validating Structured Data?
Answer: Check that the markup for Validating Structured Data 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 Validating Structured Data before publishing?
Answer: Validate the HTML, inspect accessibility and keyboard behavior where relevant, test narrow screens and translated text, and confirm that Validating Structured Data adds real document meaning or browser behavior.