FREE TUTORIALS · Learn from zero to expertBusiness DirectoryPut Your Business Ad Here — Free
Independent course disclaimer · expand / collapse

These are independently developed tutorials. Technology names belong to their respective owners; no endorsement is implied. Examples are educational, not guarantees. Verify commands, costs, security, browser support, and framework versions before production use. Google Translate requires internet and can make mistakes. Terms · Privacy · Legal.

Fundamentals → Mastery guide · Six levels, practical projects, topic checklist, worked code and results.
Level 5 of 6 · Chapter 103 of 145

Custom Elements and Semantic HTML Contracts

Let’s learn this together, starting with what the words mean. We’ll read a little, change actual code or a design, and see the result. You can also narrate the lesson on YouTube.

Beginner-friendly wordingVisible output20 answered questionsVertical code layout
  1. 1. Understand the idea
  2. 2. Read and edit the code
  3. 3. See the output
  4. 4. Practice and explain

Chapter opening: what we are doing

Imagine you want to build a small piece of a real website. Today the useful skill is Custom Elements and Semantic HTML Contracts. You do not need to memorize the entire language before trying it. Start with a working example, watch the result, and then make one small change that you can explain.

Keep the source (the instructions you write) separate from the output (what the browser actually displays). When a feature depends on a real framework application or a design tool, use the original project instructions to run the actual technology. This page also includes an isolated visual demonstration for learning and recording.

Technical words, explained simply

HTML (a language that describes what is on a web page)
element (a piece of a page written with tags)
attribute (extra information placed in an opening tag)
semantic (having a clear meaning for people and browsers)
DOM (the structure the browser builds from HTML)

See the code and its output

First read a short piece. Then use Run / Refresh Output. The display below is a real browser frame, not a sentence describing the result.

Step 1 · HTML source
Step 2 · Live browser output

Real output: the browser renders the exact HTML code shown in the editor. Edit the source and click Run / Refresh Output.

Learn it like a book: practical subchapters

Read the ideas in order, then return to the example above. Use your own words: a new learner should understand what each line changes and why the output is different.

103.01 · Custom element naming rules

Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The browser groups the heading, text, and image in a main region.

Try it yourself: Find the part of the sample related to custom element naming rules. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.02 · Autonomous versus customized built-in elements

Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The browser groups the heading, text, and image in a main region.

Try it yourself: Find the part of the sample related to autonomous versus customized built-in elements. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.03 · When native elements are preferable

Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The browser groups the heading, text, and image in a main region.

Try it yourself: Find the part of the sample related to when native elements are preferable. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.04 · Attributes as component inputs

A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The link navigates; the checkbox has a label and is required when used in a form.

Try it yourself: Find the part of the sample related to attributes as component inputs. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.05 · Light-DOM semantic content

An HTML parser constructs a DOM tree, sometimes correcting mistakes. Reading the DOM in developer tools reveals what browser rules actually produced.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe Assistive technology can identify the page structure and main content.

Try it yourself: Find the part of the sample related to light-dom semantic content. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.06 · Upgrade timing and fallback markup

Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The form has useful native behavior without a custom JavaScript framework.

Try it yourself: Find the part of the sample related to upgrade timing and fallback markup. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.07 · Accessible labels in custom components

A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The browser groups the heading, text, and image in a main region.

Try it yourself: Find the part of the sample related to accessible labels in custom components. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

103.08 · What JavaScript must provide

Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls.

Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer tools, inspect DOM or network behavior, and verify which part is native and which requires scripting or server configuration.

What you should observe The browser groups the heading, text, and image in a main region.

Try it yourself: Find the part of the sample related to what javascript must provide. Change one label, value, or setting that makes sense for this topic. Run the code again, compare the visible result, and explain the difference as though you were helping a friend start from zero.

Ready-to-narrate YouTube lesson

Scene 1 · Welcome: “Today we’ll work through Custom Elements and Semantic HTML Contracts. We’re going to start simply, so you can follow even if this is new.”

Scene 2 · Explain: Introduce a technical word from the glossary, and explain what it means with one familiar comparison.

Scene 3 · Show the source: Point out the relevant code line, the file it belongs in, and what you predict it will do.

Scene 4 · Show the result: Run the example, keep the output visible, and describe precisely what changed on the page.

Scene 5 · Improve it: Change one value or style, rerun, then show a common error and how to correct it.

Scene 6 · Finish: Give the viewer a one-minute challenge and direct them to the answered questions.

Use the YouTube Recording View button in the toolbar for a simplified reading screen. This is a narration outline, not a recorded audio/video file.

Practice: make it yours

  1. Run the starting example and confirm the output.
  2. Explain Custom Elements and Semantic HTML Contracts in simple language without reading the page word for word.
  3. Change one meaningful input, style, label, event, or component detail.
  4. Show the before and after output; do not substitute a description for the result.
  5. Make a tiny usable feature using the same idea. Check on a narrow phone screen and using a keyboard.
  6. Write down one mistake, the error message you saw, and the fix that worked.

Final challenge: Teach this chapter to someone who has never used HTML. Start with what the code is for, then demonstrate the code and output in order.

20 practice questions and answered explanations

Say the answer aloud first, then open the explanation. Every answer is included so you can check your understanding independently.

Q01. What should you understand about Custom element naming rules?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Check: The browser groups the heading, text, and image in a main region. Watch out: An img element is void: do not write a matching </img> closing tag.

Q02. What should you understand about Autonomous versus customized built-in elements?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Check: The browser groups the heading, text, and image in a main region. Watch out: An img element is void: do not write a matching </img> closing tag.

Q03. What should you understand about When native elements are preferable?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Check: The browser groups the heading, text, and image in a main region. Watch out: An img element is void: do not write a matching </img> closing tag.

Q04. What should you understand about Attributes as component inputs?

Answer: A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear. Check: The link navigates; the checkbox has a label and is required when used in a form. Watch out: A boolean attribute is enabled by its presence, not by the text "false".

Q05. What should you understand about Light-DOM semantic content?

Answer: An HTML parser constructs a DOM tree, sometimes correcting mistakes. Reading the DOM in developer tools reveals what browser rules actually produced. Check: Assistive technology can identify the page structure and main content. Watch out: Use one main element for the primary content; a section normally needs a heading.

Q06. What should you understand about Upgrade timing and fallback markup?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Check: The form has useful native behavior without a custom JavaScript framework. Watch out: Enhancement should add convenience, not erase the core workflow.

Q07. What should you understand about Accessible labels in custom components?

Answer: A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear. Check: The browser groups the heading, text, and image in a main region. Watch out: An img element is void: do not write a matching </img> closing tag.

Q08. What should you understand about What JavaScript must provide?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Check: The browser groups the heading, text, and image in a main region. Watch out: An img element is void: do not write a matching </img> closing tag.

Q09. What must your chapter lab demonstrate?

Answer: Specify an accessible custom course-card element. Keep the finished HTML file and test notes as evidence.

Q10. What should you do when the browser output differs from the source?

Answer: Open developer tools, inspect the resulting DOM, compare file paths and attribute values, then check the HTML with a validator. Change one suspected problem at a time.

Q11. In your own words, what should you know about custom element naming rules?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer.

Q12. In your own words, what should you know about autonomous versus customized built-in elements?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer.

Q13. In your own words, what should you know about when native elements are preferable?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer.

Q14. In your own words, what should you know about attributes as component inputs?

Answer: A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output.

Q15. In your own words, what should you know about light-dom semantic content?

Answer: An HTML parser constructs a DOM tree, sometimes correcting mistakes. Reading the DOM in developer tools reveals what browser rules actually produced. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open.

Q16. In your own words, what should you know about upgrade timing and fallback markup?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer.

Q17. In your own words, what should you know about accessible labels in custom components?

Answer: A form gathers named values and submits them to an endpoint. Each input needs a useful name, visible label, and instructions when the expected format is unclear. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output.

Q18. In your own words, what should you know about what javascript must provide?

Answer: Templates and component APIs divide reusable structure from runtime behavior. Keep semantic and keyboard expectations clear for custom controls. Test this specific point in the context of custom elements and semantic html contracts. Change one relevant value or element, reload, and record how the output changes. Open developer.

Q19. What is the goal of “Custom Elements and Semantic HTML Contracts”?

Answer: Use the chapter example to understand custom elements and semantic html contracts and prove the result with visible browser output.

Q20. Which course introduces this skill?

Answer: HTML. This is chapter 103 of 145, in level 5.

Disclaimer, trademarks and learning guidance

Independent educational material. External names are used solely to identify subjects. These tutorials are not official training or certification. Output may vary by browser and software version. If a framework requires a build tool, the standalone browser demonstration is an illustration, not execution of the framework source. Always test your own code before publication. Legal notice.