Perceivable
Tables
WCAG 1.3.1 Info & Relationships · A
- Automatic
- deterministic fixer, re-verified
- Guarded
- live before/after diff inside the apply
- Decision queue
- human decides, machine applies
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 when the table’s shape is unambiguous: rebuilding flattened tables, promoting header rows, setting header scope, declaring merged cells, clearing structural junk. Anything uncertain goes to the editor. Every repair is re-audited; anything that doesn’t verifiably improve the document is rolled back.
- The built-in Table Editor (first release) 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.
Watch it in 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.
proof.ockem.com
Table editor
table 1 of 2 · page 4
HEADER ROWS: 1 · HEADER COLUMNS: 1 · SCOPE PER CELL
Service
In-network
Out-of-network
Preventive
$0
$45
Specialist
$30
$85
Column
Row
Both
Apply table structure
re-audited before saving · aborts if any rule regresses
Run the full profile on one of yours.
Free, no account: one PDF of up to 10 pages and 50 MB per verified email, remediated file and verification record included. Certify it for $59 when you’re ready.