November 16, 2026

How to Review a Pricing or Plan Comparison Table

Keep a plan or pricing table that a visitor can compare without losing the headers or the relationship between columns.

Three white enamel blocks with blue, white, and pink caps standing side by side on an aluminum base, with a chrome ruler running straight across all three, on a violet background.
In this guide

A visitor at the fictional music school Reed & Meter is already comparing three lesson memberships: Private, Group, and Online. They pick one attribute, “make-up lessons,” and try to follow it across the row. At a narrow width, the Group column has lost its header, so they can no longer tell which plan a yes or no belongs to. The Online price is also on a different line from its qualifier, so the visitor cannot tell whether “$18” is per class, week, or month.

Reed & Meter is a teaching example, not a test result. The useful question is whether someone can understand the differences between these plans without losing track of the comparison.

This guide is about reviewing an existing plan or pricing table. If the table may be the wrong format, use Comparison or “Vs” Pages: When a Table Helps, When It Overwhelms.

Use these questions as a way to think, not as a score:

  • Can I identify each plan?
  • Can I find the same attribute for each plan?
  • Are the descriptions genuinely comparable?
  • Can I understand the price and its qualification together, at each width?

Keep Headers and Prices Visible as Someone Compares

In 2024 guidance on comparison tables, Nielsen Norman Group defined a comparison table as a table that uses columns for products or services and rows for the attributes, so a visitor can compare features and characteristics. It advises sticking to that standard layout: options as columns, attributes as rows, with row labels on the left and column labels above, and consistent text alignment in each column.

The same guidance says comparison-table values are not a good place to showcase personality, because equivalent values are easier to scan for differences. It also says, above all, to do the work for the visitor, and not to slow them down with nonstandard or overly long tables that repeat the same information.

If two plans use different wording for the same idea, or if a cell restates a marketing line instead of the attribute, the comparison is harder than it needs to be.

Nielsen Norman Group also notes that sticky column headers help when a list of attributes occupies several screenfuls. In a preview, you can observe whether a header appears to stay visible as you scroll. That observation is not proof that sticky headers work for every visitor or in every browser.

There is no sourced best number of plans, and no rule in this guide for a “most popular” badge. Those choices stay with the marketer.

Check the Table at Each Width

Paste the pricing page address into Online Website Previewer and press Preview. That address opens in all three frames: phone 390 by 844, tablet 820 by 1180, and desktop 1920 by 1080 CSS pixels. A table that is easy to follow on a desktop can lose its headers on a phone. The previewer is a visual check of layout in your current browser, not a test of a particular device.

On small screens, Nielsen Norman Group’s 2024 guidance says it is unlikely you will be able to show more than two items at a time in a comparison table, and that many sites remove comparison on small screens, but that some level of comparison is still worth keeping. Use that as a prompt, not as a two-column requirement.

Follow one attribute across the plans at each width. If a header disappears, if a price separates from its qualifier, or if a column can be mistaken for another, the table is no longer doing the comparison job.

WCAG 2.2 Reflow, at Level AA, exempts data tables, not individual cells, and says two-dimensional scrolling is acceptable for those parts of the content. A wide plan table that scrolls sideways at 390 CSS pixels is not automatically a reflow failure. Whether the table still lets a visitor compare is the review question. A visual preview does not settle heading-cell markup or captions. If that comes up, send it to the team.

Review the Layout, Not the Format Choice

If the table mostly repeats the same paragraph in every column, or the plans are not really alternatives to one another, the format question comes first. Send that to Comparison or “Vs” Pages: When a Table Helps, When It Overwhelms.

If plan actions compete visually, use Button Hierarchy: Primary vs Secondary Buttons. If the issue is what draws the eye first on the page, use How to Review a Website’s Visual Hierarchy. If detailed terms are being hidden in collapsed sections, Should That Content Go in an Accordion? is the relevant check. Sitewide purpose, including whether a visitor is meant to choose a plan or only to learn about the school, belongs in Brochure Site or Task-Led Site?.

Send a Keep or Rework Note

A useful note might say: “At [address], I checked the phone, tablet, and desktop previews at 390 by 844, 820 by 1180, and 1920 by 1080 CSS pixels, respectively. In the phone preview, I tried to follow ‘make-up lessons’ across Private, Group, and Online. The Group header was no longer visible, and the Online price sat apart from the word that tells me whether it is a class or a month. Please keep plan names visible while someone compares, and keep each price with its qualifier.”

For how to phrase the note, see How to Give Useful Feedback on a Website Design.