Tables
What the rule requires
A table must expose its structure — rows, header cells, and merged-cell layout — so a screen-reader user can navigate it and always know which header each number belongs to. A table without marked headers is a wall of disconnected values.
How Proof clears it
Seven automatic repairs handle the common export damage: rebuilding flattened tables, promoting header rows, setting header scope, declaring merged cells, clearing structural junk. Every repair is re-audited; anything that doesn’t verifiably improve the document is rolled back.
The built-in Table Editor handles the rest: confirm or draw the table region, toggle any cell between header and data, set scope and spans — the job that used to force remediators out to Acrobat, now inside Proof.
What to expect
Proof never guesses on ambiguous tables — a spacer grid mislabeled as headers would be worse than no fix, so uncertain cases route to the editor instead of being auto-“fixed.” Multi-row headers and header columns are an editor task by design.