Tables must have a consistent column count

PDF/UA check TABLE_REGULARITY · Tables · severity Medium · PDF/UA 8.2.5.26 Table

↩ Back to the rules index · WCAG cross-reference

Why it matters#

Irregular tables with overlapping cells or gaps break screen reader navigation. Users may hear cells in wrong order or miss content entirely.

What you will see#

Rows resolve to different numbers of columns once row and column spans are accounted for, leaving holes or overlaps.

How to fix#

Adjust ColSpan and RowSpan attributes, or add the missing TD cells, so every row spans the same number of logical columns. Ensure no cell spans across THead, TBody, or TFoot boundaries.

Step-by-step guide#

1. Establish the table's intended logical column count by counting the columns in the widest, most complete row of the visual table.
2. Open All tools > Prepare for accessibility > Fix reading order (the Reading Order tool), right-click the table, and choose Table Editor; right-click inside it and enable Table Editor Options > Show cell type, which color-codes cells and makes gaps and overlaps visible.
3. For every visually merged cell, right-click it, choose Table Cell Properties, and set Row Span and Column Span to the exact number of rows and columns it covers.
4. For rows that come up short of the column total, add placeholder cells: in the Accessibility tags panel, right-click the TR, choose New Tag > Table Data Cell (TD), and position it where the empty cell belongs; an empty TD is valid and preserves the grid.
5. Remove or unmerge spans that overshoot: a RowSpan must not extend past the last row, a ColSpan must not push a row beyond the column total.
6. If the table uses THead, TBody, or TFoot, confirm no cell's RowSpan crosses a row-group boundary; split the cell into per-group cells or move the boundary if it does.
7. Recount every row: the sum of ColSpans in each row, plus cells carried down by RowSpan from earlier rows, must equal the same logical column count in every row.

Verify: Re-run the EQChecker scan and confirm TABLE_REGULARITY passes. The Table Editor overlay should show a complete grid with no uncovered regions.

Note: Per PDF/UA-2 8.2.5.26, regularity means the number of logical cells is equal in each row after accounting for RowSpan and ColSpan (NOTE 1), and row groups formed by THead/TBody/TFoot must each be regular with no cells spanning across groups (NOTE 2). Visually blank positions still need a TD in the structure; deleting empty cells is the most common cause of this error.

WCAG success criteria#

1.3.1 Info and Relationships — Level A#

Structure and relationships conveyed visually (headings, lists, tables, labels, groups) must also be available programmatically.

Understanding 1.3.1

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549