Accessible EPUB Tables: How to Structure Complex Headers, Captions and QA

Accessible EPUB Tables: Headers, Captions & QA

Tables are a core part of academic, scientific, educational, and professional publishing. They help readers compare results, follow trends, and understand relationships that may be difficult to explain in continuous text.

But when a publication moves from print or PDF to EPUB, a table cannot rely only on its visual design.

A sighted reader may understand a table through position, borders, shading, bold text, or spacing. A reader using a screen reader needs those relationships to exist in the EPUB structure itself.

That is the real purpose of accessible EPUB tables: to make the meaning of the table clear even when the visual layout is not available.

What makes an EPUB table accessible?

An accessible EPUB table clearly shows the relationship between its headers and data cells.

A reader should be able to understand what each value means, which heading applies to it, and how the information fits together.

For a simple table, this may only require correct use of header and data cells. More complex tables may need row and column relationships, grouped headers, or stronger links between headers and values.

Captions also play an important role. They help readers understand what the table is about before they begin moving through the data.

A useful test is simple:

If the visual grid disappeared, would the table still make sense?

If the answer is no, the EPUB structure needs more work.

Start with the purpose of the table

Before applying accessibility markup, confirm that the content is actually a data table.

Some Word, PDF, and InDesign files use tables only to arrange content on the page. For example, a designer may use a table to create two columns, position labels, or build a callout box.

That does not make it a true data table.

A data table contains information that depends on row and column relationships.

Consider this example:

The value £3.6M only makes sense when the reader knows that it belongs to Europe and 2026 Sales.

Those relationships must remain available in the EPUB.

If a grid exists only for layout, it is often better to rebuild the content with standard HTML and CSS.

That first decision can prevent many accessibility problems later.

Give header cells real meaning

One of the most common mistakes is treating visual styling as structure.

A header may be bold, centred, or shaded. That makes its purpose obvious to a sighted reader.

But visual styling alone does not tell a screen reader that the cell is a header.

In EPUB table markup, <th> is used for header cells and <td> for data cells.

That distinction matters because assistive technology uses the structure to provide context while the reader moves through the table.

A table can therefore look correct and still be difficult to understand.

For publishers, visual QA should always be supported by structural QA.

Make row and column relationships clear

Many tables have headers across the top. Some also use headers down the first column.

Take this example:

The value 350 needs two pieces of context:

EPUB and February.

If the table structure does not preserve both relationships, a screen-reader user may hear only the number.

That is why attributes such as scope="col" and scope="row" can be useful. They help show whether a header applies to a column or a row.

The better QA question is not:

“Does this table contain <th> elements?”

It is:

“When the reader reaches a value, can they understand what that value represents?”

Use captions to give readers context

A clear caption helps readers understand a table before they enter it.

Compare:

Table 4

with:

Table 4. Average monthly rainfall by region, 2024–2026

The second version provides immediate context.

This is especially useful in academic books, reports, and reference works where several tables may appear close together.

A good caption should be short, specific, and meaningful.

It should tell the reader what the table contains without forcing them to inspect the whole grid first.

Complex headers need more planning

Simple tables are usually straightforward.

The difficulty increases when a table uses grouped or multi-level headers.

For example, a table may place 2025 above four quarter columns, followed by 2026 above another four.

A sighted reader can understand that grouping from the visual layout.

In an EPUB, the same relationship needs to be represented through structure.

Some tables may use row groups or column groups. Others may need explicit links between header cells and data cells.

This is where fully automatic conversion becomes less reliable.

Software may recognise rows and columns, but it may not understand the meaning behind the table.

A production specialist still needs to interpret the relationships before deciding how the table should be marked up.

Multi-level tables may need explicit associations

More complex tables can contain several levels of context.

A value may belong to:

Europe → United Kingdom → 2026 → Q2 → £4.8M

In that case, simple row and column relationships may not be enough.

The production team may need to connect the data cell with several relevant headers.

This can be done through explicit header associations where appropriate.

The important point is not the markup technique itself.

The important point is that the EPUB must preserve the same meaning that a sighted reader gets from the visual table.

That requires judgement.

Do not copy the print table blindly

An accessible EPUB does not always need to reproduce the print table exactly.

A wide table may work well across a printed page but become difficult to use on a phone, a small tablet, or under screen magnification.

It may also be tiring to navigate with a screen reader if it contains too many columns or several layers of headers.

In some cases, splitting one large table into two or three focused tables can improve usability.

The key is to preserve:

• all important data;
• the relationships between values;
• notes and units;
• editorial meaning.

Simplification should improve access, not remove information.

Keep notes, units, and symbols with the data

Correct markup is only part of the job.

The reader also needs the context around each value.

Consider the number:

125

Without more information, it could mean £125, 125%, 125 units, or an index value.

During EPUB conversion, publishers should check that units, symbols, abbreviations, footnotes, and source notes are still clear.

A table can have technically correct structure and still communicate the wrong meaning if this information is lost.

This is especially important in academic, scientific, medical, legal, and financial publishing.

Scanned tables need an extra QA stage

Scanned backlists create another challenge.

OCR can recover text from a scanned table, but it does not automatically rebuild the table correctly.

Common problems include:

• missing decimal points;
• numbers placed in the wrong column;
• lost minus signs;
• broken superscripts;
• missing row labels.

For table-heavy scanned content, the workflow should not jump directly from OCR to EPUB.

A safer sequence is:

Scan → OCR → Verify Content → Rebuild Structure → Validate → Human QA → Retest

OCR recovers the text.

Table reconstruction restores the relationships.

Accessibility QA checks whether those relationships work for readers.

These are different stages.

Automated tools are important, but they are not enough

EPUBCheck is essential for checking EPUB conformance.

Ace by DAISY can identify many accessibility issues.

Both are useful during production.

But neither can fully judge whether a complex table is easy to understand.

A table may pass automated checks and still have weak header relationships, unclear captions, or a confusing reading experience.

That is why a stronger QA process combines:

technical validation + accessibility checking + manual review + human testing

Each step finds a different type of problem.

Why human accessibility QA matters

Automated tools can check markup.

Human testers can check whether that markup actually works.

For complex tables, a tester may discover that the correct headers are present but difficult to follow. They may find that a caption lacks context or that moving through a large table becomes confusing.

Human QA should answer questions such as:

• Can the reader understand the purpose of the table?
• Are row and column relationships clear?
• Does each value have enough context?
• Are notes and units understandable?
• Can the reader move through the table without losing their place?

That is a much stronger measure of accessibility than simply confirming that the file passes validation.

A practical workflow for publishers

The most efficient way to manage table-heavy EPUB production is to classify tables before conversion begins.

This approach helps publishers estimate effort more accurately.

It also avoids treating every page as equal.

A 300-page novel and a 300-page academic title with 100 complex tables do not require the same production effort.

Table complexity affects conversion time, QA effort, specialist review, and correction cycles.

What should publishers expect from an EPUB accessibility partner?

A capable production partner should be able to explain more than which tools they use.

Publishers should understand how the team:

• identifies real data tables;
• handles grouped and multi-level headers;
• rebuilds scanned tables;
• verifies values against the source;
• performs automated checks;
• carries out manual and human QA;
• corrects and retests defects.

The goal is not simply to receive a file labelled “accessible.”

The goal is to understand the process used to make it accessible.

How Gentize supports accessible EPUB production

Gentize Innovations supports EPUB 2, EPUB 3, accessible EPUB, OCR, XML conversion, complex publishing content, screen-reader testing, keyboard testing, and human accessibility QA.

For complex tables, these activities work together.

A scanned academic table may first need OCR and content verification. It may then require semantic reconstruction, technical validation, and accessibility review.

Gentize also has 50+ accessibility testers with visual impairments supporting human-led accessibility QA.

That human review helps move the process beyond technical compliance and toward real usability.

Final takeaway

Accessible EPUB tables are not mainly a visual design problem.

They are an information structure problem.

The table must preserve the relationship between headers, values, notes, and context even when the visual grid is no longer available.

A reliable workflow is:

Understand → Structure → Verify → Validate → Human Test → Retest

Simple tables may only need clean semantic markup.

Complex tables may require grouped headers, explicit relationships, source checking, and human accessibility QA.

For publishers, the final question should be:

Can a reader understand the table's information without depending on the visual layout?

If the answer is yes, the table is doing what accessible publishing is meant to do.