Technology should stay stable and easy to check. Test each change again after release.
X25GO KNOWLEDGE · Website technology and quality
HTML semantics: Basics explained clearly
This guide covers HTML semantics. Use one real case and keep the next step clear.
What matters in practice
Set the goal first. Then use one real case.
A reliable way to work
Name one owner. Record the current state.
Change one point only. Then check the result.
Check the result again later. Keep only what helps the goal.
- Keep the first test small.
- Choose one result that should count.
- State the main question first.
- Keep the starting point visible.
- Check one risk at a time.
- Record what already works.
- Keep the baseline simple.
- Ask when one fact is unclear.
- Record the result right away.
- Keep the next action small.
- Check whether the change helped.
- Return to the start when the result is unclear.
- Use the result in the next decision.
- Keep the final note short and clear.
- Keep only what helps the goal.
- Record the final state.
- Write the goal in one sentence.
- Record the start and one real case.
- Check the key rule.
- Name the owner and approval point.
- Set one measure and one date.
- Starting without a clear goal.
- Changing several points at once.
- Using a result without a final check.
At a glance
Four relevant points to understand and check on this page.
HTML semantics: Mark up landmarks, headings, links, lists and forms according to their actual meaning.
Technology should deliver content reliably, quickly, securely and clearly for people and crawlers.
Start with purpose, terms and limits. This makes clear what belongs to the topic and what does not.
Use one real case for HTML semantics. Record which rule you tested and whether the result meets the goal.