Explore how description lists (dl) pair terms with their definitions in HTML, perfect for glossaries and term-definition blocks. Learn when to use dl versus ul or ol, and how dt and dd connect to improve readability, accessibility, and semantic structure in web design. This guide also covers practical examples and why this pattern fits clean, semantic content.

Multiple Choice

Which element groups terms and descriptions within a list?

A description list groups terms with their descriptions, pairing each term directly with its definition. This structure is perfect for glossaries or term-definition pairs because it keeps the term and its description tightly connected. In HTML, you’d use a dl element, with dt for the term and dd for its description. The other list types serve different purposes: unordered lists are for bullet points, and ordered lists are for numbered items, neither of which inherently pairs a term with a separate description. Some contexts may use the phrase “definition list,” but the typical name for this pattern is “description list.”

A quick, friendly tour of how we pair terms with their explanations on the web. If you’ve ever built a glossary, a terminology page, or a compact FAQ, you’ve probably bumped into a neat pattern that keeps words and meanings snug together. That pattern lives in a special kind of HTML list—the one that groups a term with its description in a clean, semantic pairing. In the wild of HTML, this is the description list, and it’s the go-to structure when you want a term and its definition to stay tied to one another.

What makes a description list different

Think of the usual bullet list. You have items, plain and simple. Or a numbered list, where order matters and you’re counting steps or items. These are great for sequences or bullet points, but they don’t automatically connect a term with a specific description. That’s where the description list comes in.

A description list is like a tiny caption-and-term system built into HTML. You lay down a term, and right beside it—or just below it—the definition follows. The pairing is immediate, which helps readers scan and digest the content without guessing which description belongs to which term. This tight coupling is invaluable for glossaries, phrase explanations, or any place where terms need short, precise definitions.

The anatomy: dl, dt, and dd

Let me break down the bite-sized pieces. In a description list, you’ll encounter three elements:

  • dl: The container that tells the browser, “this is a description list.”

  • dt: The term itself. This is the word or phrase you’re defining.

  • dd: The description. This is the definition, explanation, or details tied to the term.

Here’s a tiny, straightforward example to visualize it:

Responsive design
A design approach that adapts layout and content to fit different screen sizes and devices.
Typography scale
A system of font sizes and weights that maintain readability and visual hierarchy across breakpoints.
Accessibility (a11y)
Designing so people with disabilities can perceive, understand, and operate the site.

Notice how each term sits with its description, almost like a name tag and a quick bio. The browser doesn’t need extra hints; the relationship is explicit in the markup itself.

Why this structure shines for glossaries and term-definition pairs

  • Clarity by design: the pairing is explicit. Users don’t have to guess which description belongs to which term, especially when there are many items or long definitions.

  • Semantic meaning: dl, dt, and dd carry meaning beyond just how they look. Screen readers announce these elements in a way that signals a list of terms and their explanations, which makes the content more navigable.

  • Flexible layout: you can style the list in different ways—side-by-side columns, a two-column grid, or a vertical stack—without muddying the underlying relationship.

  • Easy for writers and editors: adding a new term is a simple matter of inserting a new dt followed by a dd. The pattern stays consistent, which is a win for long glossaries or technical dictionaries.

Comparing with other list types

Unordered lists (ul) and ordered lists (ol) are fantastic for different jobs, but they don’t inherently link a term with its own description. You could hack something by nesting paragraphs inside list items, but you’d lose the clean, semantic pairing. The description list keeps things tidy and accessible from the get-go.

A quick word on “definition lists”

You’ll hear people call this a definition list, and that’s because it’s the same idea poured through a slightly older naming pattern. The W3C markup uses dl, dt, and dd, but the concept remains the same: a term with its explanation. In practice, most developers and designers stick with “description list” because it communicates the pairing more precisely in modern contexts.

Accessibility: making the pair practical for everyone

Here’s a practical note that matters. When you’re building content that pairs terms with explanations, you’re not just styling a neat block—you’re shaping how someone accessing the page experiences it.

  • Screen readers: the natural rhythm of dt then dd helps screen readers announce a term followed by its definition. That predictability makes navigation smoother for users who rely on audio output.

  • Keyboard users: keep focus order logical. Typically, users will tab through terms and descriptions in a linear, readable flow. A clean dl structure aids this flow.

  • Contrast and readability: the visual pairing should be obvious even if someone isn’t reading line by line. Consider a subtle rhythm—bold terms with lighter descriptions or a gentle indent that guides the eye.

Styling tips that feel natural

You don’t need a full redesign to make a description list look polished. Here are a few approachable tricks:

  • Make the term stand out but not shout. A bold dt with a bit more margin can cue the eye that a new item has started.

  • Tie descriptions to their terms with a small indentation or a left margin on dd. It’s a gentle cue that the description belongs to the term above.

  • Use grid layouts for a compact glossary. For instance, two-column grids where terms align on the left and descriptions on the right can look modern and readable.

  • Don’t overdo it with fonts. A clean sans-serif for the body and a slightly larger size for the terms keeps things legible across devices.

A few practical patterns

If you’re assembling a neat glossary or a small dictionary of terms, you can keep the markup minimal and flexible. Here are two common layouts you’ll see in real sites:

  • Classic vertical glossary:
Frontend
The part of a website users interact with directly—the visuals, the interactions, the feel.
Backend
Where data lives and logic runs. It powers what users don’t see but experience through results.
  • Split-column glossary for a reference page:
API
A set of rules that lets software talk to each other—think of it as a menu for developers.
CSS Grid
A layout system that creates two-dimensional grids, making complex designs easier to manage.

If you’re feeling playful, you can pair dl with definition lists inside a more expansive topic page—like a “Terms you’ll see in web design” section within a bigger tutorial or knowledge hub. It’s a great way to anchor terminology in real-world usage.

Real-world instincts: when to reach for a description list

  • Glossaries: a straightforward win. You’ll keep terms and their explanations tight, which readers will appreciate.

  • Technical dictionaries: for describing acronyms, jargon, or specialized terms in a compact way.

  • FAQ sections where questions are terms and the answers are succinct explanations. While not every FAQ uses dd, when the need is tight definition, dl shines.

  • UI help panels: tooltips or inline help that define a term or concept right where it’s used.

Beyond the basics: accessibility-driven enhancements

If you want to push the experience further without losing simplicity, consider:

  • ARIA roles only when necessary. For most pages, the semantic dl, dt, and dd are enough. Only add ARIA labels if you’re hand-rolling a custom component that needs extra context.

  • Keyboard shortcuts to jump between terms. A tiny JS touch can let power users skim a long glossary by jumping from one dt to the next.

  • Responsive tweaks. On narrow screens, you might stack dt and dd with a subtle visual separator so the definitions don’t feel cramped.

A practical mindset for designers and developers

When you’re structuring content that pairs terms with explanations, you’re not just writing code; you’re shaping how knowledge is absorbed. The description list isn’t a fancy add-on. It’s a thoughtful, accessible pattern that preserves the relationship between a term and its meaning in a way that’s durable across devices and assistive tech.

If you’ve ever wrestled with making a glossary feel quick to scan, you’re already halfway there. The description list gives you the clarity you want without fuss. It’s the kind of small, purposeful choice that adds up—like picking a dependable font or choosing a color that actually helps readers see what matters.

A final nudge: think in terms of reader flow

As you draft content, imagine someone skimming down the page. They spot a term, pause for a moment, and immediately get the definition. The rhythm feels natural, almost conversational. That’s the magic of a well-structured description list. It respects the reader’s time, keeps meaning near, and invites exploration—one term, one definition, at a steady, readable pace.

If you’re curious to experiment, try turning a short glossary into a two-column layout on a landing page or blog post. You’ll likely notice how the content breathes better, how the eye glides from term to definition, and how the overall readability perks up without you having to tinker with the core text. It’s a small tweak, but it can make a big difference in how information lands and sticks.

In the end, the description list is a quiet workhorse of web design. It isn’t flashy, but it’s incredibly practical. It helps ideas transfer cleanly from the author’s mind to the reader’s understanding, with terms and their meanings holding hands all the way. And that, in web design, is a pretty solid win.