# 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. ## CCAL — An accessible staffing calendar Fictional studio Loom assigns editorial shifts. Build synthetic shifts and a local scheduling adapter; no real staff records are used. **Field:** Accessibility. **Suggested stack:** React, TypeScript, CSS Modules, Playwright. **Engineer value:** Practice focus models and accessible alternatives for spatial interfaces. **Company value:** Inspect whether scheduling remains usable across input methods and failure states. **Delivery agreement:** Record automated checks and a manual protocol; do not claim accessibility certification. ### Setup prerequisites - Create synthetic shifts including overlaps and daylight-saving boundaries. - Implement a local schedule revision adapter. ### Read the schedule Provide meaningful structure and labels. #### CCAL-101 — Name staffing shifts independently of calendar color **Bug · High priority · Foundational** noCV practice brief v5 · CCAL-101 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Read the schedule. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 80% · Frontend 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. Shift type is conveyed only by blue or green blocks. Add visible labels and complete accessible names. Acceptance criteria - Type appears as text - Names include date and duration - Color remains optional reinforcement Implementation constraints - Do not concatenate decorative icon names. Verification - Inspect two shift types - Disable color and distinguish them Deliverables - Shift label component and checks Rollout and recovery: Restore text-only blocks if labels become ambiguous. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-102 — Provide a chronological agenda beside the staffing grid **Story · Medium priority · Intermediate** noCV practice brief v5 · CCAL-102 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Read the schedule. Depends on: CCAL-101. 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. Screen-reader users must traverse many empty calendar cells to find shifts. Offer an equivalent agenda view. Acceptance criteria - Agenda lists all visible shifts - Dates are headings - View switch retains selected date Implementation constraints - Both views use one data projection. Verification - Compare grid and agenda identities - Render an empty week Deliverables - Agenda view and equivalence checks Rollout and recovery: Keep agenda available if grid navigation is withdrawn. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-103 — Describe staffing time-zone changes explicitly **Task · Medium priority · Foundational** noCV practice brief v5 · CCAL-103 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Read the schedule. Depends on: CCAL-101. 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. The calendar silently changes times when the display zone changes. Show zone context without announcing every cell. Acceptance criteria - Header identifies display zone - Shift detail exposes full date/time - Zone change has one status announcement Implementation constraints - Store instants independently from labels. Verification - Change zone and inspect detail - Use ambiguous clock time fixture Deliverables - Zone labels and manual reading protocol Rollout and recovery: Fix display to documented UTC if conversion fails. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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 shifts Support alternatives and stable focus. #### CCAL-104 — Move staffing shifts through a keyboard form **Story · High priority · Intermediate** noCV practice brief v5 · CCAL-104 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate shifts. Depends on: CCAL-102, CCAL-103. Difficulty: Intermediate. Estimated focused work: 150 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. Dragging is the only way to move a shift. Add date/time controls with equivalent validation. Acceptance criteria - Every draggable shift has Move action - Form and drag share validation - Cancel preserves the shift Implementation constraints - The form must not require pointer gestures. Verification - Move using keyboard - Submit overlapping invalid shift Deliverables - Move form and equivalence cases Rollout and recovery: Disable dragging if it diverges from the form contract. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-105 — Restore staffing focus after a shift is deleted **Bug · High priority · Advanced** noCV practice brief v5 · CCAL-105 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate shifts. Depends on: CCAL-104. Difficulty: Advanced. Estimated focused work: 165 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. Deleting a selected block sends focus to the document body. Choose a predictable surviving target. Acceptance criteria - Next chronological shift receives focus - Empty day focuses its heading control - Failed deletion retains original focus Implementation constraints - Resolve targets after committed DOM updates. Verification - Delete middle shift - Reject deletion and inspect focus Deliverables - Focus resolver and deletion checks Rollout and recovery: Keep deleted-row placeholder temporarily if focus restoration fails. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-106 — Announce staffing conflicts without repeating the entire calendar **Bug · Medium priority · Intermediate** noCV practice brief v5 · CCAL-106 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate shifts. Depends on: CCAL-104. Difficulty: Intermediate. Estimated focused work: 120 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 revision conflict rerenders the grid and reads dozens of cells. Isolate a concise conflict message and resolution controls. Acceptance criteria - Conflict identifies affected shift - Draft remains available - Calendar content is not a live region Implementation constraints - Announcements must not reveal unrelated staff data. Verification - Trigger one conflict - Retry failure and check announcement count Deliverables - Conflict status region Rollout and recovery: Disable auto-refresh announcements if they repeat. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-107 — Support calendar navigation across removed and disabled shifts **Task · High priority · Expert** noCV practice brief v5 · CCAL-107 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate shifts. Depends on: CCAL-105, CCAL-106. Difficulty: Expert. Estimated focused work: 240 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. Roving focus points at a disabled shift after refresh. Define deterministic navigation across changing eligible targets. Acceptance criteria - Only one navigation tab stop exists - Disabled targets are skipped - Removed focus resolves predictably Implementation constraints - Document arrow-key behavior without overriding text inputs. Verification - Navigate mixed availability - Remove current target during refresh Deliverables - Navigation model and transition cases Rollout and recovery: Switch to ordinary tab stops while repairing the model. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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 adaptive use Handle zoom, motion and assistive feedback. #### CCAL-108 — Reflow staffing controls at high text zoom **Bug · Medium priority · Intermediate** noCV practice brief v5 · CCAL-108 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify adaptive use. Depends on: CCAL-102, CCAL-107. Difficulty: Intermediate. Estimated focused work: 120 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. At 200 percent text size the week selector hides Add shift. Reflow controls while keeping date context. Acceptance criteria - Controls wrap without clipping - Agenda avoids horizontal document overflow - Focus remains visible Implementation constraints - Horizontal grid scrolling may remain within a labeled region. Verification - Check enlarged text in agenda - Check long synthetic shift labels Deliverables - CSS changes and viewport evidence Rollout and recovery: Prefer agenda on constrained layouts if grid controls fail. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-109 — Remove nonessential motion from staffing date transitions **Chore · Low priority · Foundational** noCV practice brief v5 · CCAL-109 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify adaptive use. Depends on: CCAL-103. Difficulty: Foundational. Estimated focused work: 60 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. Animated week slides make date navigation uncomfortable for some users. Respect reduced motion while preserving orientation. Acceptance criteria - Reduced motion skips sliding - Date heading still updates - Focus and selection remain stable Implementation constraints - Do not use animation completion as business logic. Verification - Toggle reduced-motion preference - Navigate rapidly during transition Deliverables - Motion styles and interaction case Rollout and recovery: Disable transitions globally if state depends on them. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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. #### CCAL-110 — Audit staffing calendar semantics in a reproducible manual walkthrough **Chore · Medium priority · Advanced** noCV practice brief v5 · CCAL-110 · An accessible staffing calendar Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Verify adaptive use. Depends on: CCAL-107, CCAL-108, CCAL-109. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Quality engineering 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. Automated checks pass but the team lacks a repeatable reading and editing protocol. Write and execute a bounded walkthrough. Acceptance criteria - Protocol covers agenda and grid - Keyboard outcomes are recorded - Failures include concrete reproduction steps Implementation constraints - Report tested browser and assistive tool versions, not certification. Verification - Complete one shift move - Exercise conflict and empty-week paths Deliverables - Manual audit record with unresolved findings Rollout and recovery: Reopen failed behaviors before widening the calendar pilot. Project prerequisites: Create synthetic shifts including overlaps and daylight-saving boundaries. Implement a local schedule revision adapter. Engineer value: Practice focus models and accessible alternatives for spatial interfaces. Company value: Inspect whether scheduling remains usable across input methods and failure states. 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.