Skip to content
Interface language: English
Design / Signal

Comparing services on a phone: how to keep the meaning readable

Help customers compare service options on a phone. Choose a table, cards or a short list of differences, then check that each value has enough context.

Article language: English

A woman in a light suit with one hand on a small stone door beside a glowing lamp.
In this article

The table fits on a phone. Unfortunately, the meaning of the comparison is three screens away, together with the column heading. When comparing services, a reader should be able to check a specific condition: who prepares the content, what the option includes and who approves the result. If they have to remember a key or decipher symbols, the layout is not helping. Keep the meaning of the data instead of merely squeezing the table to fit the screen.

First choose criteria that distinguish the options. Only then decide whether you need a scrolling table, separate cards or a short list of differences. No single layout suits every number of services. The example below uses a hypothetical offer, without invented sales results or an attempt to cram every condition into one row.

Start with the customer's decision, not a list of features

Imagine a studio offering a consultation, a design, and a design with implementation. The customer does not need to be told that the company is professional in all three options. They need to know what result they will receive, what they must do themselves and how much participation the work requires. These are possible comparison axes. Base such criteria on the customer's actual activities and time, rather than simply comparing claims that working together is easy. The guide to a customer's time and effort (in Polish) helps identify that work.

Separate shared elements from differences. Common conditions can be explained before the comparison. Repeating them in every column makes the page longer and hides the important differences among repeated confirmations. Keep the features that affect the choice or need checking before an order.

If you cannot describe a difference in a simple sentence, the offer itself may need work. An 'extended quality standard' is hard to compare honestly with an 'enhanced quality standard'. Describe the scope instead: preparing text, number of view types, publication system configuration and how documentation will be handed over. The guide to structuring a B2B service page (in Polish) places that scope in the wider offer.

A useful check is: which decision would this row change? If none, move the information to the common description or remove it. A comparison should help people choose a scope, not prove that the most elaborate column uses the most ink.

Name criteria so the values make sense

'Content' is a broad heading. It does not say whether it means writing, editing, entering text into a system or the number of pages. Split it into suitable criteria or give it a more precise name. 'Yes' only helps once the question is clear. If comparisons are generated from a catalogue, prepare a content model with separate fields and vocabularies rather than extracting meaning from a free-form description every time. The guide to product-catalogue content models (in Polish) explains how to structure those fields.

In the hypothetical offer, 'Enter supplied text' and 'Write text from scratch' should be separate items. A customer may not distinguish those activities professionally, but will notice the difference when asked to write the entire website. The comparison should prevent such misunderstandings rather than decorate them with a check mark.

Do not mix activities, promises and judgments on one axis. 'Analytics', 'Complete security' and 'Highest quality' are not comparable scope items. Each important point should describe something that can be checked: what will be done, within which boundaries and how it will be accepted.

For prices and ranges, state which scope they apply to. 'From' does not remove the need to explain the basis. A guide to presenting B2B service prices on a website (in Polish) discusses other ways to present this. Agree the comparison content against the sales offer before refining visual shorthand.

Choose a layout for what must be compared at the same time

A table helps when readers compare the same feature across several options. Cards work when each option needs a short, self-contained description. A list of differences is enough when the choice turns on two or three points. Sketch each with real content and try the same task in each layout.

For example, ask a participant to find the option that includes implementation while leaving text preparation to them. Then ask who will handle later updates. Finding the first answer quickly is not enough if the layout obscures the second, equally important boundary.

Do not automatically turn a table into cards just to remove horizontal scrolling. With many criteria, customers must then remember values from earlier cards. An orderly scrolling region may be clearer than a very long list of three nearly identical descriptions. The decision depends on the real task, not an aesthetic dislike of scrollbars.

If you offer a control that selects two options for comparison, check its interaction cost. It can make sense for a larger catalogue. For three simple services, it may merely add work before the answer.

Preserve data relationships in the actual structure

A website table should not be just a visual grid. The W3C tables tutorial explains why headers must be marked up and associated with data cells. This helps a person using assistive technology identify the option and criterion for a value being read.

In the specification, record axis names and relationships as well as colours and widths. A simple table with row and column headers is easier to understand than one with many merged cells. If the design needs several header levels, check whether that complexity helps the customer or simply mirrors the company's internal structure.

Be careful when rearranging elements for mobile. A visual change should not lose the relationship between a value and what it describes. An individual card may need to repeat a criterion name that appears only once on a wide screen. Do not assume visual and reading order will always remain the same.

Carry out these checks alongside a broader assessment of the company website's accessibility. The guide to assessing website accessibility (in Polish) explains the wider scope. One working comparison does not establish conformance for the whole site, but it can remove a specific barrier to a decision. Repeat the check after content changes: a longer name or a new condition may reveal a problem absent from the first data set. A recognisable relationship between header and value matters as much as legible type.

Aeneia conceptual photography

If the table scrolls, make that apparent

Horizontal scrolling within a region can be justified. The WCAG 2.2 explanation of Reflow allows an exception for content requiring a two-dimensional layout, including data tables. This does not make every layout acceptable across the whole page. Content within an individual cell must still meet Reflow unless that content itself requires a two-dimensional layout for use or meaning.

Clearly distinguish the scrolling region from the rest of the page and show that more columns exist. A visible part of the next column and a short instruction can help. Do not rely on a barely visible shadow alone. Check keyboard operation too, including whether a user can leave the region without searching for a way out.

A sticky first column can preserve context, but consumes considerable width on a small screen. Try the longest criterion name and enlarged text. If the values are left with a narrow strip, the mechanism solves one problem by creating another. A shorter name and a clear explanation above the table may work better.

Do not shrink every letter to footnote size. This apparent space saving transfers effort to the reader. A guide to website typography (in Polish) discusses scale and readability. A sense of quality also comes from not having to pinch-zoom for every answer.

Replace unexplained symbols with information

A check mark and a dash look concise, but a dash might mean absent, not applicable, undecided or available for an extra fee. These are four different business situations. Agree a consistent vocabulary and show it where readers can actually use it. For important items, plain 'Not included' may be better than elegant ambiguity.

The same applies to colour. Explain a highlighted recommended option: who it suits and in what circumstances. The most expensive column does not become best merely because it has a gold background. If the recommendation applies to a particular customer profile, name it rather than implying a universal choice.

Explanations should not require hovering over a tiny icon. That mechanism may be awkward on a phone and inaccessible by keyboard. Put an important condition in the text or provide an ordinary accessible disclosure control. This particularly applies to limits, customer responsibilities and additional costs.

Run a separate check with a person who reads only the option names and values. Can they distinguish 'Optional', 'By agreement' and 'Included'? If not, do not just improve the key. The services themselves may need clearer boundaries before publication.

Test the design with awkward content

Insert a long service name, a condition several sentences long and a missing value in one item. Add another language if the site supports one. These are not mischievous scenarios invented for sport. Offers change after publication, and a design should withstand more than an ideal set of short words.

Also change the number of options. What happens when one service is withdrawn? Can an editor reorder them without manually repairing the entire layout? Does the shared description still apply to every column? The answers affect the data model and editorial work, not just the initial appearance.

If customers will download the comparison, plan a print version or a properly prepared file. A picture of the table is not enough. See the article comparing PDF and ordinary web pages (in Polish) for the format choice. Conditions should not disappear merely because they no longer fit inside a screenshot.

Connect the comparison to a next step without secretly changing scope

Buttons under options should say what happens: go to a description, start an enquiry or choose a scope to discuss. 'I choose' can imply an order even when the form only collects preliminary information. Match the label to the actual effect. If the price requires confirmation, do not imply that clicking settles the terms.

Preserve the selected option in the form if the site supports it. A customer should not need to find its name again or reconstruct selected items. At the same time, show what has been passed to the enquiry and how to change it. An automatically populated hidden field does not help if the employee later reads a different scope from the one the customer remembers.

Try two scenarios. In one, the customer knows the option and only wants to ask about availability. In the other, they do not yet know whether implementation is needed and want to discuss the choice. Does each person have a natural next step? If the second must make a firm choice before contact, the table may create false certainty instead of helping them decide.

Allow an enquiry about a scope outside the comparison if the company actually considers one. Do not make readers pick a random column merely to start a conversation. A clear 'Help me choose the scope' option may be more honest than another universal package. See the guide to B2B website contact forms (in Polish) for this continuation.

During maintenance, compare the message received by the team with the current option description. A form name can remain outdated after an editorial change to the table. Add this dependency to the publication task and repeat the test after an update. The customer sees one offer; internal divisions between content, form and notification should not change its meaning.

Check the answers the comparison was meant to make easier

Before publication, choose several real offer questions and ask people to find the answers on a phone. Record not only time but also mistakes: choosing the wrong option, missing a condition or assuming an extra is included in the price. This is material for improving specific information, not a ranking of participants' dexterity.

Include enlarged text, a keyboard check and comparison with the current sales offer in website acceptance. The website acceptance checklist (in Polish) covers related checks. The service owner should be responsible for the content. A designer can organise conditions but should not independently decide which commitments the company accepts.

If you want to organise options and their presentation, see the scope of Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear