Press release tables need more than aligned columns. Readers must be able to connect each value to its row, heading, unit and qualification after publication. Keep a small, clearly labeled table in the announcement, preserve its structural markup and check the version readers receive. A screenshot of a spreadsheet answers a different accessibility question.
A release team usually controls the approved source document, while each publisher controls its own page. Treat that handoff as part of the review. The facts can survive a copy-and-paste while the relationships between them disappear.
Choose the information that belongs together
Start with the question the table answers. A table suits a set of comparable facts with a logical relationship. A short list may work better when each point is independent. W3C’s Tables Tutorial explains why a data grid needs markup identifying header and data cells, rather than visual formatting alone.
For an announcement, keep the qualifier beside the claim it changes. A capacity number needs its unit and stage. An access statement needs the market or eligible account group. A period-on-period comparison needs the period and basis. These are editorial checks on the supplied facts, not permission to fill gaps with assumed values.
Prepare the evidence before fitting the copy into columns. The press release source pack explains how to keep supporting documents with the approved claims.
Give the table a caption and useful headers
W3C’s caption guidance describes a caption as a heading that helps readers identify a table, including people navigating from table to table with a screen reader. Write a short topic label. For a complex structure, explain how the information is arranged in nearby text or an appropriate summary.
A caption and a summary do different work. “Product access by market” names the topic; a separate explanation can tell readers which columns contain access conditions. Repeating the same sentence in both places adds little.
Mark header cells with th and ordinary data cells with td. Making the top row bold or giving it an orange background does not establish those relationships in the document structure.
Keep row and column relationships explicit
A table with both a header row and a header column needs a clear direction for each. In its two-header tutorial, W3C uses scope="col" for a column header and scope="row" for a row header.
Here is a sample editorial checklist, not a product announcement or a report of a client result:
<table> <caption>Sample: context to preserve beside announcement facts</caption> <thead><tr><th scope=“col”>Field</th><th scope=“col”>Reader’s question</th><th scope=“col”>Context to retain</th></tr></thead> <tbody> <tr><th scope=“row”>Access</th><td>Who can use it?</td><td>Market, account eligibility and release stage</td></tr> <tr><th scope=“row”>Usage limit</th><td>What does the allowance cover?</td><td>Unit, period and applicable conditions</td></tr> <tr><th scope=“row”>Comparison</th><td>What changed?</td><td>Baseline, measurement period and source</td></tr> </tbody> </table>
The source document and the published HTML need separate checks. A publisher may preserve the words but convert every cell to td, or flatten the table into an image. Ask which output the publishing system supports before treating the source file as the finished deliverable.
For multi-level or irregular headers, the simple row-and-column approach may be insufficient. W3C’s tutorial describes more explicit associations for complex cases. Simplifying the table is often a better editorial starting point than adding another tier of merged headings.
Review the small-screen version
W3C’s table tips recommend keeping tables simple and preserving structural relationships when a responsive table changes format. Separate data belongs in separate cells. Line breaks used to imitate rows can stop lining up when text grows.
For a publishing review, enlarge the text and inspect the narrow layout. Check that the last column remains reachable, headings stay attached to their values and important notes are still available. A wide table clipped by hidden overflow loses information even if its desktop screenshot looked complete.
If the publisher turns rows into cards, review the labels on those cards. A value such as “Available” needs the field and scope it belongs to. Keep decorative layout separate from the data table itself.
Check every format and destination
HTML, PDF and an image are separate outputs. W3C notes that table markup can be lost during format conversion. A readable HTML table therefore does not establish that an exported PDF retains an equivalent structure, or that a third-party copy preserved it.
Keep the approved table with its sources and qualifications, then inspect the public page and each downloadable version. Record the URL, asset revision, review scope and any unresolved issue. For a PDF and HTML released together, use the version-handoff guide.
A table screenshot can be useful as an accompanying illustration, but review its text alternative and provide the underlying information in an accessible form. The press release image accessibility checklist covers that separate image review.
Prepare the publishing handoff
Send the approved facts, their table structure and the supported output requirements together. After publication, check the page readers receive. Send a brief for a distribution request, or get a free AI Shortlist Check for a separate review of what AI says about your company.