Practical guide

Keep comparison-table labels attached to their values

A number in a comparison table needs a product, a feature and a unit. Preserve those relationships in the page's HTML and its phone layout so readers can tell what each value means.

A service comparison lists “1” under one package and “3” under another. The column headings identify the packages, while the row heading says the numbers count included locations. Remove either heading and the values become ambiguous. A screenshot can preserve the visual arrangement while losing the table relationships that assistive technology needs.

Build the comparison as a data table with explicit headings, then check that its meaning survives navigation and a narrow screen. This gives an editor a concrete acceptance test: a reader must be able to identify the package and feature associated with any value.

Name the comparison and the counted unit

Begin with a caption that explains the table's subject. W3C's table guidance describes captions as a way to identify a table and help people decide whether to read it. A separate explanation can describe an unusual structure; repeating the caption in a second note adds little. W3C captions and summaries

For a commercial comparison, put the unit where it travels with the value. “Included locations” is more useful than “Coverage.” “Response time, business hours” carries a condition that “Support” does not. If a figure depends on annual billing or another restriction, keep that qualification beside the figure rather than behind a distant link.

Unknown information needs its own wording. A blank cell could mean unavailable, not researched, not applicable or zero. Use the state the source establishes. In an editorial comparison, “not documented” must not become “not offered.”

Associate both row and column headings

The following fictional comparison has a feature in each row and a package in each column. Neither package is a real offer.

Scroll horizontally to read all columns. Use the arrow keys when the table is focused.

Fictional service packages
FeatureCedar packageMaple package
Included locations13
Weekend supportNot includedAvailable by separate agreement

The value “3” belongs to both “Maple package” and “Included locations.” In HTML, use header cells for those labels and identify their direction with scope. W3C recommends explicit scope when header relationships could otherwise be ambiguous. W3C header guidance

<table>
  <caption>Fictional service packages</caption>
  <thead>
    <tr>
      <th scope="col">Feature</th>
      <th scope="col">Cedar package</th>
      <th scope="col">Maple package</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Included locations</th>
      <td>1</td>
      <td>3</td>
    </tr>
  </tbody>
</table>

This excerpt shows the location row only. Add the support row using the same row-header pattern when implementing the complete example. Bold text inside ordinary data cells is not a substitute for identifying header cells.

The value three is associated with the Maple package column and the Included locations row.

Original fictional example. The highlighted cell means “Maple package: three included locations.” It describes no Gist or competitor product.

Simplify a table before adding more header levels

A table that nests country, package, billing term and feature can become difficult to follow even when its markup is valid. W3C describes using unique header IDs and a data cell's headers attribute for complex relationships. It also recommends considering smaller tables that make the structure easier to understand. W3C multi-level headers

Choose the structure around the reader's comparison. If someone needs to compare the same feature across two packages, keep those packages together. If each country has a different offer, separate country tables may make the conditions clearer. Do not merge different units into one column merely to reduce width.

Check the relationships on a phone

Keep the table's text readable. If the table needs horizontal scrolling, make the scroll area reachable and usable from a keyboard, with a visible focus indicator and a short explanation of the available movement. Check the rightmost column rather than stopping at the initial phone screenshot.

If the design instead converts each package into a card, repeat each feature label beside its value. A card containing “3” still needs to say what is counted. Check the rendered accessibility structure after a responsive change; a desktop view alone does not establish that the phone version retains the intended relationships.

Finally, follow a real value back to its current source. Correct HTML can faithfully present an outdated entitlement. Factual verification, table structure and visual usability are separate checks, and the release record should identify which version passed each one.

What these changes establish

Explicit labels give readers and software a defined relationship to inspect. They do not establish that an AI service will fetch, interpret or cite the table. The immediate result to verify is that the comparison remains understandable without relying on its visual position alone.

Gist publishes this guide and sells AI visibility software. W3C guidance was checked November 18, 2026. The example and suggested publishing checks are ours; this is not an accessibility certification or an AI citation experiment. For consistency between a web report and its download, see the separate HTML and PDF guide.