Start with one real case for HTML semantics. Record the start and the goal.
Technology should stay stable and easy to check. Test each change again after release.
X25GO KNOWLEDGE · Website technology and quality
HTML semantics: Risks and limits to know
This guide covers HTML semantics. Use one real case and keep the next step clear.
What matters in practice
Key rule: Mark up landmarks, headings, links, lists and forms according to their actual meaning.
Mark clear risks. Define when a person must review the result.
A reliable way to work
Set one question before the test. Decide what result should count.
Name one owner. Record the current state.
Change one point only. Then check the result.
If money, customers or public claims are involved, add a human review.
Check the result again later. Keep only what helps the goal.
Set the goal
- Use one real case.
- Record the current state.
- Name the person who owns the task.
- Keep the first test small.
Check the starting point
- Write down open points.
- Keep the source easy to find.
- Mark unclear data before the change.
- Check one risk at a time.
Change one point
- Let a person review important claims.
- Keep the test easy to repeat.
- Use the same measure as before.
- Record the result right away.
Secure the result
- Share the result with the right person.
- Keep open points visible.
- End the test when the goal is met.
- Use the result in the next decision.
Practical checklist
- 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.
Common mistakes
- Starting without a clear goal.
- Changing several points at once.
- Using a result without a final check.
Concrete example
Example: An SME tests HTML semantics with one real case. The team records the start, changes one point and checks the result. Then it plans the next step.
Related guides
At a glance
Four relevant points to understand and check on this page.
What this subject covers
HTML semantics: Mark up landmarks, headings, links, lists and forms according to their actual meaning.
The rule for this area
Technology should deliver content reliably, quickly, securely and clearly for people and crawlers.
What this perspective checks
Mark points with legal, financial, technical or reputational impact and add controls there.
Check it in practice
Use one real case for HTML semantics. Record which rule you tested and whether the result meets the goal.