Preserve table header associations in the reporting workbench
Sticky styling replaced table headers with generic containers. Restore native table relationships.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- HTML · Tables
Estimated field mix
- Accessibility70%
- Frontend30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional cooperative Quarry reviews synthetic service-volume reports. Build local report fixtures with empty, missing and delayed values.
Setup prerequisites
- Create synthetic report series with explicit missing values.
- Stub report loading, sorting and export responses.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Column headers use correct semantics
- Row labels identify rows
- Sticky behavior preserves reading order
Implementation constraints
- Avoid ARIA overrides of native table roles.
Verification to include
- Inspect header relationships
- Render grouped and empty rows
Deliverables
- Semantic table markup
Rollout and recovery
Remove sticky styling if it breaks semantics.
Value of the work
For the engineer: Practice semantic data presentation and robust interaction.
For the team: Inspect whether reporting decisions remain possible without color or pointer use.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.