# Cards: Grouping One Subject's Content and Actions Into a Reusable Unit

> A card is a contained box for one subject. Here is how a design system defines its parts, variants, states, and rules so every team builds it the same way.

**In short:** A card is a contained box that groups one subject's content and actions, and a design system defines its parts, variants, states and rules so every team builds it the same way.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/cards

## What you will learn

A card is a small, boxed surface that holds content and actions about one subject, such as a product, an article, or a person. In a design system, a card is not drawn from scratch each time. A team defines it once, with clear rules, so every screen uses the same parts.

This lesson shows you how to name a card's parts, tell required parts from optional ones, plan layouts and states, and set simple rules for grids, clicking, and accessibility. The Airbnb listing card is our worked example.

- **Design system:** A shared set of parts, rules, and guidance that a team uses to build its products.
- **Reusable part:** A piece that is built once and used again on many screens.
- **Card:** A contained box that groups content and actions about one subject.
- **Container:** The outer box that holds all the other parts of a card.
- **Variant:** A planned version of the same part, such as a side-by-side layout.
- **State:** How a part looks at one moment, such as when a pointer hovers over it or when it is disabled.
- **Token:** A named design decision, such as a corner size or a spacing amount, stored once and reused everywhere.
- **Focus:** The visible outline that shows which item a keyboard user has reached.
- **Heading:** A title tag that gives a page or a card its outline for screen reader users.
- **Hit area:** The part of an item that responds when someone taps or clicks.
- **Responsive grid:** A layout that changes how many columns fit as the screen gets wider or narrower.
- **Overflow menu:** A hidden list of extra actions that opens from one button.

## What is a card?

Google's Material Design describes a card as a surface that holds content and actions about a single subject. Other public design systems describe cards in a similar way. The subject can be a product, an article, a person, or an event.

The one-subject rule matters most. If one box holds a product and a news story, a reader cannot tell what it is about. Cards also work best beside similar cards, so a reader can scan them one after another.

Define a card once because, without a shared rule, each team builds its own box. One screen uses rounded corners, another uses sharp ones, and a third adds a heavy shadow.

> **Tip:** Before you design a card, write down the one subject it describes. If you cannot name that subject in a few words, the content probably needs a different shape.

## What is the anatomy of a card?

Anatomy means the named parts that make up a card. Systems use slightly different names, but the same ideas come back again and again.

- **Container:** The outer box. It holds every other part, and its size comes from what sits inside it. Material Design treats it as the only required element.
- **Media:** A picture, illustration, or video, usually at the top or the side. It is optional.
- **Title:** The short headline about the subject. Most cards have one, and it should be marked as a heading.
- **Supporting text:** A few lines that add detail about the subject. It is optional.
- **Metadata:** Small facts such as a date, a location, a count, or a category. It is optional.
- **Actions:** Buttons or links the reader can use. Keep one main action easy to find, and move extra actions somewhere else.

A required part must be present for the card to work. An optional part can be left out on some cards. Material Design says the container is the only required element. Fluent says all of its card slots are optional.

### Team rules for required parts

A design system can add its own rules. Many teams decide that every card needs a title, because a card with no title tells a reader very little. Write that as a team rule, not as a law of design.

1. **Mark the container as required:** Every card has one, so it never goes missing.
2. **Mark the title as required by team rule:** Only do this if your team agrees that readers need it.
3. **Keep the same parts across a group:** The GC Design System advises that if one card in a section has an image, all of the cards in that section should have one.

## What are the variants, layouts and styles?

A variant is a planned version of the same card. Plan two kinds. Layout variants change how the parts are arranged. Style variants change how the box looks.

### Layout variants

- **Vertical:** The media sits on top, and the title and text stack below it. Fluent describes vertical cards as having slots for a header, a body, and a footer.
- **Horizontal:** The media and text sit side by side and read from left to right. The U.S. Web Design System calls a similar option a flag layout.
- **Compact:** A smaller version with fewer parts and tighter spacing, useful in dense lists. Your team decides which parts stay.

### Style variants

Material Design lists three style variants: elevated, filled, and outlined. Elevated cards have a drop shadow. Filled cards have a subtle surface color that differs from the background. Outlined cards have a visible border. The Material Android documentation says all three give the same legibility and function, so the choice comes down to style.

> **Tip:** Keep the number of variants small. Each variant needs its own rules, its own tests, and its own documentation.

## How does a card respond in each state?

A state is how a card looks at one moment, often because of what a person did or what the system is doing. Plan these before the screens are built.

- **Default:** The card at rest, with no one touching it.
- **Hover:** A small change, such as a shadow lift, that shows the card can be pressed. It only helps mouse or pointer users, so the meaning must also be clear another way.
- **Focus:** A visible outline that appears when a keyboard user moves to the card. Figr calls this critical for accessibility.
- **Selected:** The card has been chosen, such as one option among several. Your team picks the look, for example a stronger border.
- **Loading:** The content is not ready yet. Your team defines a placeholder so the layout does not jump when the content arrives.
- **Disabled:** A greyed-out look that tells the reader the card is not available right now.

Depth can also change between states. One design analysis reports that Material cards rest at a small elevation and rise on hover. The exact values belong in your team's rules, so check the source before you copy them.

## Built on tokens

A card should not hold loose numbers typed in on each screen. Instead, it points to tokens. The padding inside a card and the gaps between its parts use spacing tokens. Its corners use a radius token. Its shadow uses an elevation token. Its surface, border, and text colors use color tokens.

When a team changes one token, every card that uses it changes together. A team can change the corner size of all cards in one edit instead of hunting through screens.

One analysis of Airbnb's design lists 16px for the padding of a property card's meta block, and 24px for its host and reservation cards. In a real system, each value has a name and a place in the rules, not a number typed by hand.

> **Tip:** Record which token each part uses. The naming and creation of tokens is covered in the Token lesson.

## Worked example: the Airbnb listing card

Airbnb's listing card pairs a photo carousel with a title, a location, a rating, and a price, and it repeats across search results. The sources we read are third-party analyses of Airbnb's screens, not Airbnb's own rulebook. Where they disagree, we say so.

1. **Read the photo:** The photo sits at the top with rounded corners. One analysis describes it as a swipeable carousel, so a guest can move through several pictures. A heart icon at the top-right is a separate save control, so a guest can save a listing without opening it.
2. **Check the optional badge:** Some cards show a Guest favorite label at the top-left. It is optional and has its own rules, covered in another lesson.
3. **Read the text block:** Below the photo comes the title, then the location. One analysis describes the block as title, location, dates, and price, with the price often right-aligned as a per-night amount. Another lists the order as title, a grey meta line, then price and rating.
4. **See the grid:** On search pages the same card repeats in a multi-column grid. Each card keeps the same parts in the same order.

The analyses do not agree on every detail. One reports 14px corners on a square photo. Another reports 20px corners. A design system solves this by choosing one value and recording it as a token, not by copying a screenshot.

What would a design system define as rules? Here is how the Airbnb card breaks down.

- **Structure rule:** Photo, optional badge, save control, title, location, dates, price, and rating appear in a fixed order on every listing card.
- **Part rule:** The photo is its own part. One analysis says it is kept separate because some pages, such as wishlists, reuse only the photo.
- **Variant rule:** A taller 4:5 version exists for experience listings. The system names it as its own variant.
- **Style rule:** The listing card has no border or shadow, so the photo edge defines the card. A team wanting a different look would write a different rule.
- **Behavior rule:** The save control stays separate from the main link. The team decides where a tap on the card goes.
- **Grid rule:** Cards in one grid share the same parts and spacing, so search results look calm and even.

## Should you use a card, list, or table?

A card is not always the right choice. Material Design says a quickly scannable list suits similar content with few actions. It also says cards are unnecessary in a gallery of images, where the pictures already carry the content. The U.S. Web Design System adds that when readers move through items in order, a list or plain text with headings may fit better.

- **Choose a card when:** Each item has a picture or a strong visual, a few facts, and one main action, and readers scan the items side by side.
- **Choose a list when:** Items are mostly plain text, there are many of them, or they carry little or no action.
- **Choose a table when:** Readers need to compare the same fields, such as price, size, and date, across many items.

> **Tip:** Ask one question: will the reader scan by picture, read in order, or compare by number? The answer usually points to the right choice.

## Cards in a responsive grid

Cards usually sit in a responsive grid, which changes its column count as the screen width changes. Material Design advises fluid dimensions, so cards stretch to fit the space instead of staying one fixed size. It also says a card should never push other elements out of the way.

1. **Start with one column:** Stan recommends designing mobile first, with a single column of cards.
2. **Add columns as the width grows:** Stan suggests two columns on tablet and three or four on desktop. The GC Design System uses one card per row on mobile and two or three on desktop. Systems differ, so your team picks its own numbers and writes them down.
3. **Keep row heights even:** Stan warns that uneven heights look like a staircase. Shorten long text or change the layout to fix it.
4. **Let the width flex:** Set each card to fill its column, so it grows and shrinks with the screen.

## Should the whole card be clickable?

A card can be clickable in three main ways. The whole card can be one target. Only the title can act as the link. Or only a button inside the card can act. Each choice has trade-offs.

- **Whole card:** Best when the card has one job, such as opening one article. The U.S. Web Design System says that for single-action cards, the hit area wraps the entire card.
- **Title or main button:** Best when the card holds more than one control. Material Design offers a primary-action region that can cover most of a card when most of it should act.
- **Button only:** Best for cards with several controls, such as a save icon. The rest of the card stays still.

The risk with a whole-card link is that it can hide other controls. A link cannot contain another link. Ciello's guide on accessible cards makes this point, and one audit-based article calls the whole-card-as-link pattern the most common card accessibility failure it sees.

> **Tip:** Keep the heart, the menu, and other controls outside the main link. If a card has more than two extra actions, Material Design suggests an overflow menu.

## Accessibility basics for cards

Cards can confuse keyboard users and screen reader users if they are built carelessly. These basics belong in every card rule.

### Heading structure

The title of a card should be a heading tag. A screen reader user can then jump from card to card by heading and hear the main idea of each one. Figr calls this non-negotiable. Choose a heading level that fits the page outline, so headings do not jump around.

### Focus and reading order

A keyboard user must be able to reach every card and every button by pressing the Tab key. Each interactive part needs a visible focus outline. The order of reaching the parts should make sense. Ciello's guide ties this to Meaningful Sequence, criterion 1.3.2 at Level A of the accessibility standard. Put the save control in the order a reader would meet it, not after the whole page.

### Images and text on photos

Images need descriptions for screen readers. If text sits on a photo, the photo must leave enough contrast for the text to be read. Material Design also says the content inside a card should not scroll, so keep cards short and let the page scroll instead.

> **Tip:** Test with the keyboard only. Press Tab through your grid, and check that you can always see where the focus is and that the order makes sense.

## Check your understanding

Try these short scenarios. Each one needs the ideas from this lesson to answer.

**Quick check:** Your team's product page shows items on three screens. Each uses a differently styled card, with different corner radii, padding, and button placement. What should the team do first?

A. Ask the designer of the most popular screen to pick one style and copy it to the other two screens.
B. Compare the three cards, then define one card pattern with its parts, variants, and tokens for radius, padding, and button placement before changing any screen.
C. Add a heavy shadow to all three cards so they look alike at a glance.
D. Turn every card into a plain list so the differences disappear.

**Answer:** B. The fix starts with one shared definition. The team names the parts, sets the rules for corners, padding, and buttons, and then moves each screen to that definition. Copying one screen only moves the problem to another screen.

**Quick check:** A new event card holds a photo, a title, a ticket button, a share icon, and a save heart. A developer proposes making the whole card one link, with all the buttons placed inside it. What should the design rule say?

A. Make the whole card one link and keep the buttons inside it, so every tap works the same way.
B. Remove the title, so the card has fewer controls to place.
C. Keep one main action on the card, and place the share and save controls outside the main link or in an overflow menu.
D. Hide the focus outline so the card looks cleaner when someone taps it.

**Answer:** C. A link should not hold another link, and nested controls confuse keyboard and screen reader users. The main target stays clear, and the extra controls move out of it.

**Quick check:** A travel app must show 40 flights so people can compare departure time, fare, and number of stops. A designer proposes one card per flight in a sideways carousel. Which option is the better choice?

A. Keep the carousel, but make each card a little taller so more details fit.
B. Put all 40 flights inside one large card that scrolls inside itself.
C. Use a carousel of cards, and show the fare only when someone hovers.
D. Use a table with one row per flight and one column each for departure time, fare, and stops.

**Answer:** D. Cards suit items that people scan by picture. Comparing the same fields across many items is easier in a table. Card content should also not scroll inside the card, which rules out the scrolling option.

## Key takeaways

A card groups content and actions about one subject. Define it once, with its required parts, optional parts, layout and style variants, and states. Build those looks on tokens so one change reaches every card. Use cards for items people scan by picture, and use lists or tables when readers read in order or compare numbers. In a grid, keep parts and heights consistent. Keep one clear main action, and make sure focus, headings, and reading order work for every person.

## Sources

- [Cards - Material Design 3 guidelines](https://m3.material.io/components/cards/guidelines)
- [Cards - Material Design (v2 guidance)](https://m2.material.io/components/cards)
- [Cards - Material Design (earlier guidance)](https://material.google.com/components/cards.html)
- [Material Components for Android - Card documentation](https://github.com/material-components/material-components-android/blob/master/docs/components/Card.md)
- [Cards - Material Design 1 components](https://www.mdui.org/en/design/1/components/cards.html)
- [React Card - Fluent 2 Design System](https://fluent2.microsoft.design/components/web/react/core/card/usage)
- [Card - GC Design System (Canada.ca)](https://design-system.canada.ca/en/components/card/design/)
- [Card - U.S. Web Design System (USWDS)](https://designsystem.digital.gov/components/card/)
- [Card UI Design Pattern: When and How to Use Cards (Figr)](https://figr.design/blog/card-ui-design-pattern)
- [UI Card Design: Examples, Best Practices and Common Patterns (Stan)](https://www.stan.vision/journal/ui-card-design-examples-best-practices-and-common-patterns)
- [How to Design Card UI and Why They Matter (UXPin)](https://www.uxpin.com/studio/blog/card-design-ui/)
- [Accessible cards by design (Chiara Ciello, Medium)](https://medium.com/@chiaracielo/accessible-cards-by-design-4741e2158bb4)
- [Angular Material Card overview](https://material.angular.dev/components/card/overview)
- [How Airbnb Designs Their UI: A Design System Breakdown (Superdesign)](https://superdesign.dev/blog/airbnb-design-system)
- [Airbnb DESIGN.md (getdesign.md)](https://getdesign.md/airbnb/design-md)
- [Design System Analysis of Airbnb (getdesign.md preview)](https://getdesign.md/design-md/airbnb/preview)
- [Airbnb Design System (Everyone's Design)](https://everyonesdesign.pages.dev/companies/airbnb)
- [Airbnb Design System (Design Extractor)](https://www.design-extractor.com/gallery/airbnb)
- [airbnb.ca website design: fonts, colors and UI patterns (Fudge)](https://design.withfudge.com/share/airbnb.ca-design)
