A comparison table should reduce the work a reader has to do. It fails when a row mixes several measurements, an abbreviation has no explanation or the mobile version hides the heading that gives a number meaning. These problems matter in football statistics, poker-format explainers and agency publisher shortlists.

Start by writing the decision the table supports. A reader choosing which guide to open needs different information from an analyst comparing a team across seasons. If the table cannot be introduced in one clear sentence, narrow its purpose before adding columns.

Define a row and its units

Give each row one consistent subject: a team-season, a tournament format or an anonymised publishing option. Keep each measurement in its own column. Write the unit in the heading, and put the reporting period beside the table. Do not mix estimated monthly organic visits with total website visits under a common heading such as Traffic.

Use an explicit missing-data label. A dash can mean unavailable, not applicable or zero; those are different statements. Explain the choice once in the caption or an adjacent note. Where a value is an estimate, preserve that qualification rather than making the table look more certain than the underlying evidence.

Give the table a readable structure

W3C's table tutorial explains the roles of captions, header cells and associations between headers and data. For a straightforward comparison, identify column headings and any row headings in the actual HTML. Styling ordinary cells to look bold is not a substitute for structural headings. Complex tables may need a different association method or a simpler design.

The agency handover should describe the row meaning, the headings and the explanatory note. The publisher or developer can then implement the structure. Do not assume that copying a spreadsheet into a publishing system preserves its accessibility.

Illustrative example: three editorial options

Illustrative example: an editor compares a tennis glossary, an NBA statistics explainer and a poker tournament-format guide. Each row has a topic, intended reader, evidence needed and review owner. There is no numerical score pretending to predict rankings. The caption says this is an editorial planning comparison, not a performance forecast.

On a phone, the editor checks whether the headings remain understandable when the table scrolls. With keyboard navigation, the reviewer checks whether any surrounding controls can be reached. A separate accessibility review can test the implemented table with assistive technology; a screenshot alone cannot establish that its semantics are correct.

Keep public comparisons anonymous where needed

For a shortlist from our publisher inventory, use public reference labels rather than private publisher names. Agree which audience figures and prices can appear through the placement service. If the table appears in a clip from the free article-video offer, simplify it for the screen and explain the important comparison aloud. A dense table that works in an article may need a different visual treatment in a short video.

Sources

Sources checked 3 November 2026.