# noCV engineering task library Content version 5 Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs. Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence. ## CTABLE — An accessible reporting workbench Fictional cooperative Quarry reviews synthetic service-volume reports. Build local report fixtures with empty, missing and delayed values. **Field:** Accessibility. **Suggested stack:** React, TypeScript, CSS Modules, Playwright. **Engineer value:** Practice semantic data presentation and robust interaction. **Company value:** Inspect whether reporting decisions remain possible without color or pointer use. **Delivery agreement:** Submit focused report changes with manual checks; no compliance certification is implied. ### Setup prerequisites - Create synthetic report series with explicit missing values. - Stub report loading, sorting and export responses. ### Expose report meaning Define labels and missing values. #### CTABLE-101 — Give report charts a textual trend summary **Story · Medium priority · Foundational** noCV practice brief v5 · CTABLE-101 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Expose report meaning. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A line chart has only an image label reading Chart. Add a concise summary sourced from the displayed series. Acceptance criteria - Summary names metric and period - Missing samples are disclosed - Summary does not invent causation Implementation constraints - Compute facts from fixture data only. Verification - Summarize rising series - Summarize incomplete series Deliverables - Trend summary projection Rollout and recovery: Hide summary if it disagrees with displayed data. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-102 — Preserve table header associations in the reporting workbench **Bug · High priority · Foundational** noCV practice brief v5 · CTABLE-102 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Expose report meaning. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 70% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Sticky styling replaced table headers with generic containers. Restore native table relationships. 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 - Inspect header relationships - Render grouped and empty rows Deliverables - Semantic table markup Rollout and recovery: Remove sticky styling if it breaks semantics. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-103 — Represent missing report observations distinctly from zero **Task · Medium priority · Intermediate** noCV practice brief v5 · CTABLE-103 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Expose report meaning. Depends on: CTABLE-101, CTABLE-102. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 60% · Data engineering 20% · Accessibility 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Missing intervals are graphed at zero and alter the apparent trend. Define equivalent chart and table representations. Acceptance criteria - Zero remains numeric - Missing values have explicit text - Chart gaps match table omissions Implementation constraints - Do not impute values within this ticket. Verification - Compare zero and missing rows - Use all-missing series Deliverables - Missing-value contract and cases Rollout and recovery: Disable chart interpolation if gaps are misrepresented. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Operate report controls Keep sorting, disclosure and export accessible. #### CTABLE-104 — Expose report sorting through semantic header buttons **Story · Medium priority · Intermediate** noCV practice brief v5 · CTABLE-104 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate report controls. Depends on: CTABLE-102, CTABLE-103. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 70% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Column sorting works only by clicking an unlabeled header. Add named buttons and current sort direction. Acceptance criteria - Buttons identify sortable field - Current direction is exposed - Unsortable headers remain plain text Implementation constraints - Preserve native table navigation. Verification - Sort ascending then descending - Activate with keyboard Deliverables - Sort controls and keyboard cases Rollout and recovery: Restore fixed documented ordering if controls fail. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-105 — Keep report filter errors near their controls **Bug · Medium priority · Intermediate** noCV practice brief v5 · CTABLE-105 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate report controls. Depends on: CTABLE-104. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Invalid date ranges produce a toast that disappears before users reach the fields. Add persistent linked errors. Acceptance criteria - Error names affected range - Correction clears the message - Submitted values remain editable Implementation constraints - Do not automatically reset user dates. Verification - Submit reversed range - Correct only end date Deliverables - Date-filter errors and focus checks Rollout and recovery: Fall back to explicit apply with inline errors. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-106 — Provide a keyboard alternative to chart range brushing **Story · High priority · Advanced** noCV practice brief v5 · CTABLE-106 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate report controls. Depends on: CTABLE-101, CTABLE-105. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Frontend 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Selecting a chart interval requires dragging across the plot. Add equivalent start/end interval controls. Acceptance criteria - Controls select the same range - Selection is visible in table - Out-of-range values explain limits Implementation constraints - Keep brushing optional. Verification - Select identical range both ways - Enter range outside data Deliverables - Range selector and equivalence tests Rollout and recovery: Disable brushing if it diverges from controls. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-107 — Keep report details discoverable after virtualized rows leave view **Bug · High priority · Expert** noCV practice brief v5 · CTABLE-107 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate report controls. Depends on: CTABLE-104, CTABLE-106. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 40% · Performance engineering 30% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Expanded row details unmount during scrolling and leave focus nowhere. Bound virtualization around active interaction. Acceptance criteria - Focused details remain mounted - Collapsed rows release retained nodes - Large fixtures stay within documented DOM budget Implementation constraints - Do not pin every previously opened row forever. Verification - Scroll focused detail out of view - Collapse and verify reclamation Deliverables - Focus-aware virtualization policy Rollout and recovery: Disable virtualization for interactive details if focus is lost. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Verify equivalent access Test constrained display and failure feedback. #### CTABLE-108 — Announce reporting export readiness without stealing focus **Story · Medium priority · Intermediate** noCV practice brief v5 · CTABLE-108 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify equivalent access. Depends on: CTABLE-105. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 70% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A completed export opens a modal and interrupts filter editing. Expose a stable download action with a status message. Acceptance criteria - Readiness announces once - Focus stays in active control - Failure exposes retry Implementation constraints - Keep file status outside the table live region. Verification - Complete export while editing - Fail export before completion Deliverables - Export status component Rollout and recovery: Use explicit status refresh if announcements repeat. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-109 — Keep report distinctions visible in forced-color mode **Bug · Medium priority · Advanced** noCV practice brief v5 · CTABLE-109 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify equivalent access. Depends on: CTABLE-103, CTABLE-107. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 70% · Frontend 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Report lines and selected rows vanish under forced colors. Add structural distinctions using patterns and borders. 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 - 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. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CTABLE-110 — Document report equivalence through a narrow assistive audit **Chore · Medium priority · Advanced** noCV practice brief v5 · CTABLE-110 · An accessible reporting workbench Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify equivalent access. Depends on: CTABLE-107, CTABLE-108, CTABLE-109. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 50% · Quality engineering 30% · Data engineering 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. The team cannot verify that the chart alternative carries the same decisions. Execute a defined fixture-based comparison. Acceptance criteria - Audit compares values and gaps - Keyboard sort and export are covered - Unresolved limitations remain explicit Implementation constraints - Record environment and actual observations. Verification - Find highest known interval both ways - Inspect missing data and failed export Deliverables - Audit protocol and findings Rollout and recovery: Block wider report rollout for reproducible information loss. Project prerequisites: Create synthetic report series with explicit missing values. Stub report loading, sorting and export responses. Engineer value: Practice semantic data presentation and robust interaction. Company value: Inspect whether reporting decisions remain possible without color or pointer use. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence.