Lorixen.
EN

Price tables that work on phones

Short answer: A wide table can't simply shrink onto a phone, so pick a pattern that suits how people read it. Two or three packages work best as stacked cards; a long feature comparison usually needs horizontal scrolling with a pinned first column and a visible hint that there's more; a monthly/annual toggle cuts the number of columns. Whatever you choose, keep a real HTML table underneath where the content is tabular, with proper header cells, and test on an actual phone.

Package tables are everywhere on small business sites: cleaning plans, photography packages, gym memberships, web hosting tiers. They look tidy on a laptop. On a phone, the same table either shrinks to unreadable text or runs off the right edge with no sign that two more columns exist.

Why wide tables break

web.dev's HTML tables guide puts it plainly: tables aren't responsive by default; they size themselves to their content, and extra work is needed to make them behave across devices. A four-column package table with eight feature rows simply has more width than a phone screen offers. Something has to give: the columns, the layout or the amount shown at once.

Five patterns compared

Pattern Best for Strength Watch out for
Stacked cards 2–4 packages with short feature lists Each package reads like its own mini page Harder to compare one feature across packages
Stacked rows (label + value pairs) Tables with many columns but few rows Nothing scrolls sideways Long pages; repeated labels
Horizontal scroll with cues Detailed feature comparisons Keeps the true table intact People may not realise they can scroll
Sticky first column Long comparisons where row labels matter Feature names stay visible while scrolling Pinned column takes width; keep labels short
Toggles and tabs Monthly vs annual, or one package at a time Fewer columns on screen at once Hides information behind a tap

When to use each

Stacked cards

Use cards when you have a handful of packages and each has a short list of what's included. On a phone, each card stacks vertically: name, price, the key inclusions, and a button. Put your most chosen package first or mark it clearly. Keep the features in the same order on every card so people can compare by scrolling.

Stacked rows

When a table has many columns but only a few rows (for example, opening hours by location), each row can become a block of label and value pairs. web.dev warns that if you change the CSS display of table elements to achieve this, you should add ARIA roles back, because changing display can affect how some browsers expose the table to assistive technology. That's a detail for whoever builds it, but worth asking about.

Horizontal scroll with cues

For a real comparison (eight or more features across three or four packages), keep the table and let it scroll sideways inside its own container, not the whole page. Then make the scroll obvious:

  • Let the next column peek in at the edge so it's clearly cut off.
  • Add a short line such as "Swipe to see all packages" above the table.
  • Add a fade or shadow at the edge that disappears when people reach the end.

Sticky first column

Pair horizontal scrolling with a pinned first column holding the feature names, so people always know which row they're reading. This uses CSS sticky positioning, which MDN's position reference describes as an element that scrolls with its container until it reaches a set offset and then stays put. Keep the labels short; a pinned column that takes half the screen leaves little room for the data.

Toggles and tabs

A monthly/annual toggle halves the price information shown at once. Tabs that show one package at a time work when people usually pick a package and then check its details, rather than comparing everything. Avoid tabs when comparison is the point.

Accessibility: keep it a real table

If the content is genuinely a grid of data, it should be marked up as a table, whatever it looks like on a phone. The essentials, from MDN and web.dev:

  • Header cells. Use <th> for column and row headers. MDN's th reference lists scope values of col, row, colgroup and rowgroup to say which cells a header relates to. web.dev notes that header associations still work when the header row or column has scrolled out of view.
  • A caption. The <caption> element gives the table an accessible name, according to MDN. "Cleaning plans compared" is enough.
  • Structure. MDN's table accessibility guide covers <thead>, <tbody> and <tfoot> for grouping rows, plus scope, id and headers for associating cells with headers.
  • Keep it simple. web.dev observes that simpler tables with few or no spanned cells are easier for everyone to understand, not only screen reader users.
  • Don't use tables for layout. A card grid of packages isn't tabular data; it can be ordinary headings and lists.

Ticks and crosses need text alternatives too: a screen reader should hear "included" or "not included", not silence.

Code-free implementation notes

Things to agree with whoever builds or edits the page:

  1. Decide the pattern per table, based on the number of packages and features, before design starts.
  2. Write feature names short. "Weekly visits" beats "Number of scheduled weekly visits included".
  3. Put the price and the button in the same place on every card or column.
  4. Keep prices as text, not images, so they scale and can be read aloud.
  5. Check page builder output. Some pricing-table widgets produce lists or nested boxes rather than tables; fine for cards, not for a full comparison.
  6. Plan the breakpoint. Decide at what width the layout changes, and check the in-between sizes such as small tablets and phones turned sideways.

Testing

  • Check on at least one real small phone, not only a browser's resized window.
  • Turn the phone sideways and back.
  • Increase the phone's text size and see what breaks.
  • Use a screen reader (VoiceOver on iPhone, TalkBack on Android) on the comparison table.
  • Ask someone unfamiliar with the page to find the price of the middle package and what it includes.

FAQ

Can't the table just shrink to fit?

It can, but text becomes too small to read. Shrinking is the failure mode, not a pattern.

Are cards or a table better for packages?

Cards for a few simple packages, a table for detailed feature comparisons. Some sites show cards on phones and a table on larger screens.

Do people scroll tables sideways?

They can, but only if they notice there's more. That's why visible cues matter.

Is a pricing-table plugin enough?

Often, for cards. Check its phone layout and whether it outputs proper table markup if you need a comparison.

Where your packages make sense on a laptop but turn into a squeeze on a phone, we can rework them into a layout that reads well at any size.

Sources

WhatsAppLet’s talk