Keep report distinctions visible in forced-color mode
Report lines and selected rows vanish under forced colors. Add structural distinctions using patterns and borders.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Forced colors · CSS
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CTABLE-101 · Give report charts a textual trend summary
- CTABLE-102 · Preserve table header associations in the reporting workbench
- CTABLE-103 · Represent missing report observations distinctly from zero
- CTABLE-104 · Expose report sorting through semantic header buttons
- CTABLE-105 · Keep report filter errors near their controls
- CTABLE-106 · Provide a keyboard alternative to chart range brushing
- CTABLE-107 · Keep report details discoverable after virtualized rows leave view
Acceptance criteria
- Series have non-color identifiers
- Selected rows retain visible state
- Focus outline remains discernible
Implementation constraints
- Honor system colors instead of forcing brand fills.
Verification to include
- Inspect forced-color rendering
- Check selected row on empty refresh
Deliverables
- Styles and captured verification notes
Rollout and recovery
Use the data table as the default constrained view.
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.