HTML address: identify contact details for the right owner

When the element earns its place

A claims decision includes the team responsible for its content. Place that team's contact details in the article, where their ownership is clear. A delivery destination in the claim record is ordinary data and should not be marked as the article author's address. The link below is an internal contact route so the example works without exposing a person's email address in page source.

<article>
  <h1>Claim C-47 decision</h1>
  <p>The review team requested one more document.</p>
  <address>
    Decision owner: Claims Review Team.
    <a href="/support/claims">Contact the claims team</a>.
  </address>
</article>

Behavior boundary

The local contact route needs a real handler. Address does not certify a person's identity, update a case, or create a postal address; it describes who can be contacted about this content.

Cost and operational limits

Semantic markup costs almost nothing to load. The maintenance cost is accuracy: review ownership and contact routes when teams or case responsibilities change.

Common Mistakes

• Do not use address for every postal location shown in an article.
• Do not put an unrelated corporate footer inside a case article's address.
• Do not publish a contact route that leads nowhere.

Connected lessons

• HTML article and section: mark standalone content and named subdivisions
• HTML landmarks: give navigation, main content, and page edges clear owners
• HTML anchors: use href for navigation and stable fragment targets

Continue with HTML br and hr: separate a line from a change of subject.