Skip to main content
Full Stack Radio

118: Aaron Gustafson - Semantic HTML: The Hard Parts

69 min episode · 2 min read
·

Episode

69 min

Read time

2 min

AI-Generated Summary

Key Takeaways

  • Heading hierarchy: Use single h1 per page as most important element, followed by h2s and h3s in proper order. HTML5 sectioning elements never implemented automatic outline algorithm, so sequential heading levels remain critical for screen readers navigating document structure and assistive technology understanding page organization.
  • Article element definition: Think of articles as individual items that stand alone independently, like articles of clothing rather than publication articles. Each Airbnb listing card, tweet, or blog post qualifies as an article element. Pages can contain unlimited articles without confusing screen readers or creating accessibility issues.
  • Hidden heading strategy: Major sites like Facebook use visually hidden headings to create proper document outlines separate from visual design. Each section receives an h2 title even when not displayed, allowing screen readers to navigate while designers maintain visual flexibility without compromising semantic structure or accessibility requirements.
  • Form label requirement: Always use label elements with for attributes to associate text with form fields. This creates accessible names for assistive technology, expands clickable areas for checkboxes and radio buttons, automatically focuses fields when labels are clicked, and represents the easiest accessibility improvement developers can implement immediately.
  • Description lists for metadata: Use dl, dt, and dd elements for key-value pairs like price per night, location, or post metadata instead of generic divs. Description lists provide semantic structure for data relationships, remain underutilized despite broad applicability, and offer better accessibility than paragraph or span alternatives for structured information.

What It Covers

Aaron Gustafson from Microsoft Edge explains semantic HTML for web applications, covering heading hierarchies, sectioning elements like article and aside, navigation patterns, form labels, and how proper markup enables screen readers and digital assistants to parse content.

Key Questions Answered

  • Heading hierarchy: Use single h1 per page as most important element, followed by h2s and h3s in proper order. HTML5 sectioning elements never implemented automatic outline algorithm, so sequential heading levels remain critical for screen readers navigating document structure and assistive technology understanding page organization.
  • Article element definition: Think of articles as individual items that stand alone independently, like articles of clothing rather than publication articles. Each Airbnb listing card, tweet, or blog post qualifies as an article element. Pages can contain unlimited articles without confusing screen readers or creating accessibility issues.
  • Hidden heading strategy: Major sites like Facebook use visually hidden headings to create proper document outlines separate from visual design. Each section receives an h2 title even when not displayed, allowing screen readers to navigate while designers maintain visual flexibility without compromising semantic structure or accessibility requirements.
  • Form label requirement: Always use label elements with for attributes to associate text with form fields. This creates accessible names for assistive technology, expands clickable areas for checkboxes and radio buttons, automatically focuses fields when labels are clicked, and represents the easiest accessibility improvement developers can implement immediately.
  • Description lists for metadata: Use dl, dt, and dd elements for key-value pairs like price per night, location, or post metadata instead of generic divs. Description lists provide semantic structure for data relationships, remain underutilized despite broad applicability, and offer better accessibility than paragraph or span alternatives for structured information.

Notable Moment

Gustafson reveals that proper semantic HTML enables digital assistants to execute complex commands like searching specific sites for products or reading top headlines from news pages, demonstrating how accessibility features benefit all users beyond traditional screen reader applications and creating machine-readable formats for emerging technologies.

Know someone who'd find this useful?

You just read a 3-minute summary of a 66-minute episode.

Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Full Stack Radio

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

You're clearly into Full Stack Radio.

Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime