# Keep the headers attached when the table leaves your screen

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Keep the headers attached when the table leaves your screen

ID: MHC-D-RESEARCH-1109 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-the-headers-attached-when-the-table-leaves-your-screen

Bold text is not a relationship.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A table is readable visually but confusing with assistive technology or after export.

### Avoid when

- Complex tables may need a simpler alternative. A correct source document does not guarantee that an export preserves its structure.

### Explanation

Identify the row and column headers that give each value its meaning. Represent those associations semantically in the chosen format, and check the exported result separately. Keep complex headings only when the task genuinely needs them.

### Steps

1. Name what a reader must know to interpret a data cell.
2. Use appropriate header associations and a useful table description or caption.
3. Inspect representative cells in the delivered format, including cells under grouped headings.

### Example

A status table must preserve both the business unit and reporting period for each value, not merely bold the top row.

### Check

Can a non-visual reader recover the relevant headers while moving through the table?

### Limits

- Complex tables may need a simpler alternative. A correct source document does not guarantee that an export preserves its structure.

### Evidence and sources

- supports: WAI table guidance uses semantic header and data-cell relationships so table structure is available beyond visual presentation. — RS-4952EB9FEE9EB4C3. Complex tables and exports need format-specific verification; bold text is not a semantic header. (Table structure and header associations.)
- RS-4952EB9FEE9EB4C3: Tables Tutorial — https://www.w3.org/WAI/tutorials/tables/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-colour-a-second-way-to-speak
