# 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. ## A11Y — A civic appointment flow people can complete The fictional Riverside desk books appointments for permit paperwork and library assistance. Its browser flow was assembled from separate forms and dialogs. Work uses synthetic availability and booking adapters; actual appointments and personal records are excluded. **Field:** Accessibility. **Suggested stack:** TypeScript, Semantic HTML, CSS Modules, Playwright, axe-core. **Engineer value:** Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. **Company value:** Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. **Delivery agreement:** Choose a bounded issue and record automated and manual checks separately. A passing scanner does not establish complete accessibility. ### Setup prerequisites - Synthetic services, slots, and booking API contract - Keyboard and screen-reader access for a documented manual check ### Enter the flow Make service selection and entry understandable. #### A11Y-101 — Replace clickable service tiles with a named selection group **Bug · High priority · Foundational** noCV practice brief v5 · A11Y-101 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Enter the flow. Depends on: No preceding ticket. 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. Service choices are clickable divs. Keyboard users cannot reach them, and a screen reader announces no selected service. Repair selection without changing the taxonomy. Acceptance criteria - Every service belongs to a semantic single-choice group with a visible label. - Selected value is announced and included in the form value. - Unavailable services explain their status and cannot be selected by keyboard or pointer. Implementation constraints - Prefer native radio inputs and associated labels over a custom interaction model. Verification - Choose Library assistance using only the keyboard and inspect the form value. - Try selecting an unavailable service through pointer and keyboard; selection remains unchanged and its reason is readable. Deliverables - Semantic service chooser and keyboard regression case Rollout and recovery: Release independently; restore native unstyled controls if decoration hides focus or selection. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-102 — Keep contact-field help and errors understandable together **Task · Medium priority · Foundational** noCV practice brief v5 · A11Y-102 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Enter the flow. 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. A phone-field error replaces the format hint, then disappears on the first keystroke while the value remains invalid. Give help and validation a coherent lifecycle. Acceptance criteria - Persistent help and current errors are associated with their field. - Submitted errors remain until correction or the next documented validation point. - Invalid submission provides a focusable summary linked to every invalid field. Implementation constraints - Do not announce errors on every keystroke; document validation timing. Verification - Submit an invalid phone and navigate from summary to field; hear both hint and error. - Correct one of two invalid fields and resubmit; only the remaining error appears and values persist. Deliverables - Contact validation semantics and assistive-technology notes Rollout and recovery: Apply to contact fields first; retain plain inline errors if enhanced summary behavior loses focus. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. ### Choose an appointment Handle date navigation and changing slots. #### A11Y-103 — Make month navigation work without a pointer **Story · High priority · Intermediate** noCV practice brief v5 · A11Y-103 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Choose an appointment. Depends on: A11Y-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. The calendar exposes 42 unnamed buttons and moves focus to the page top on month changes. Add a deliberate keyboard model and plain date-entry alternative. Acceptance criteria - Date controls announce full date, availability, and selection. - Changing month retains focus at a predictable date or documented month control. - Manual date entry uses the same availability validation and reports invalid dates clearly. Implementation constraints - Document the calendar keyboard model; shortcuts must not conflict with text entry. Verification - Select an available date across a month boundary by keyboard. - Enter an impossible date and navigate to an unavailable date; neither becomes selected and focus remains recoverable. Deliverables - Accessible date selection and month-boundary walkthrough Rollout and recovery: Keep manual entry during rollout; disable the custom calendar on keyboard-navigation regression. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-104 — Keep the booking action visible at high zoom **Bug · High priority · Intermediate** noCV practice brief v5 · A11Y-104 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Choose an appointment. Depends on: A11Y-102, A11Y-103. Difficulty: Intermediate. Estimated focused work: 90 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 400% zoom the fixed step header and cookie banner cover the selected time and Continue button. Repair reflow across booking steps. Acceptance criteria - At the documented desktop viewport and 400% zoom, essential content reflows without horizontal page scrolling. - Fixed UI never covers focused fields, error links, or booking actions. - Long service names and expanded text spacing do not clip labels or values. Implementation constraints - Use normal flow where fixed positioning provides no user benefit. Verification - Complete service and slot selection at 400% zoom by keyboard. - Apply expanded text spacing and a long service name with an error summary; check clipping and focus obstruction. Deliverables - Reflow corrections and viewport/zoom evidence notes Rollout and recovery: Check every step before shared layout release; revert sticky behavior first if actions become obscured. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-105 — Recover when another visitor takes the chosen slot **Bug · High priority · Advanced** noCV practice brief v5 · A11Y-105 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Choose an appointment. Depends on: A11Y-103. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 50% · Frontend 30% · API design 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 last 10:30 appointment is taken while a visitor enters contact details. Submission reports Slot unavailable and resets the entire flow. Acceptance criteria - Conflict preserves contact values and service while clearing the unavailable slot. - The conflict is announced once and focus moves to a useful recovery heading with alternatives. - A replacement needs explicit confirmation and current availability revision data. Implementation constraints - Never automatically book a different time; availability remains server-authoritative. Verification - Conflict the slot, choose 11:00, and finish without re-entering contact details. - Return no alternatives and fail refresh; explain the state without trapping focus or inventing availability. Deliverables - Slot-conflict recovery and accessible failure scenario Rollout and recovery: Exercise synthetic capacity conflicts before pilot; pause booking if contact recovery or slot identity is unreliable. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. ### Preserve progress Recover focus, drafts, and session interruptions. #### A11Y-106 — Announce availability changes without reading the whole page again **Task · Medium priority · Advanced** noCV practice brief v5 · A11Y-106 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Preserve progress. Depends on: A11Y-105. Difficulty: Advanced. Estimated focused work: 135 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. Each refresh rewrites a large live region. A screen reader repeats all slots and interrupts contact entry even when nothing changed. Acceptance criteria - Unchanged slot lists generate no routine announcements. - Meaningful changes produce a short status without moving focus. - Loss of a selected slot takes priority over routine counts; stale request messages are ignored. Implementation constraints - Use a small status region and coalesce bursts; never mark the entire form live. Verification - Refresh identical data three times while typing; no repeated list announcement occurs. - Remove the selected slot while delayed old data arrives; announce loss once and retain current focus. Deliverables - Announcement coordinator and manual speech-output log Rollout and recovery: Pilot with routine announcements disabled; retain only actionable notices if speech becomes noisy. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-107 — Handle expiry without an inaccessible countdown trap **Story · High priority · Expert** noCV practice brief v5 · A11Y-107 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Preserve progress. Depends on: A11Y-102, A11Y-105, A11Y-106. Difficulty: Expert. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 50% · Frontend 30% · Backend 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. A slow form session expires after details are entered. The countdown steals focus every second, and Extend reports success after the server session has ended. Acceptance criteria - Advance warning offers an accessible extension action without announcing each second. - Extension success requires server confirmation and preserves the active form location. - Expiry or uncertain extension preserves a scoped draft but requires session recovery and fresh slot validation before booking. Implementation constraints - Use a fake clock and session adapter; do not weaken expiry or record contact data in analytics. Verification - Extend before expiry by keyboard and verify confirmed continuation with focus restoration. - Race expiry and a lost extension response; expired authority cannot book, and recovery revalidates the slot. Deliverables - Session continuity state machine and expiry-race walkthrough Rollout and recovery: Pilot against short synthetic sessions; disable booking under ambiguous session authority while preserving recoverable drafts. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-108 — Return focus correctly after reviewing contact details **Bug · Medium priority · Advanced** noCV practice brief v5 · A11Y-108 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Preserve progress. Depends on: A11Y-104, A11Y-107. Difficulty: Advanced. 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. Edit contact opens a dialog from review. Closing returns focus to a control removed by session refresh, stranding keyboard users. Acceptance criteria - The dialog has a name, contained focus, and visible close action. - Closing restores the invoking control or a documented visible fallback if the step changed. - Recovery and dialog close cannot race focus into hidden or inert content. Implementation constraints - Use an accessible primitive with local styling and coordinate focus ownership across states. Verification - Edit and close normally; focus returns to Edit contact with revised details visible. - Expire the session while editing and close during recovery; focus lands on the current recovery heading. Deliverables - Dialog focus ownership fix and interleaved-state keyboard test Rollout and recovery: Enable only on review; switch to inline editing if dialog focus ownership regresses. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. ### Complete and verify Make confirmation and release evidence usable. #### A11Y-109 — Make confirmation usable on screen and in print **Story · Medium priority · Intermediate** noCV practice brief v5 · A11Y-109 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Complete and verify. Depends on: A11Y-105, A11Y-108. 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. The screenshot-style confirmation cannot be selected, print cuts off the address, and appointment time omits the time zone. Acceptance criteria - Service, date, time zone, location, and reference are selectable semantic text. - Print includes all appointment details without navigation chrome or clipping. - Only confirmed bookings show confirmation, with an accessible copy-reference action. Implementation constraints - An HTML print view is sufficient; PDF generation is excluded. Verification - Confirm a synthetic appointment, copy its reference, and inspect print preview. - Return an uncertain result and use a long location; no false confirmation appears and reconciled print details remain complete. Deliverables - Semantic confirmation and print stylesheet Rollout and recovery: Release styling after booking-identity checks; retain plain-text details if print styling fails. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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. #### A11Y-110 — Build a barrier-focused release check for booking **Chore · High priority · Advanced** noCV practice brief v5 · A11Y-110 · A civic appointment flow people can complete Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Complete and verify. Depends on: A11Y-106, A11Y-107, A11Y-109. Difficulty: Advanced. Estimated focused work: 150 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. Scanners pass while keyboard testers still lose drafts after conflicts. Add a release check covering actual booking and recovery. Acceptance criteria - Checks cover keyboard completion, zoom, named controls, slot conflicts, and session recovery. - Automated assertions and manual observations are recorded separately with browser/tool versions. - Unresolved barriers name affected steps and usable fallbacks without claiming universal accessibility. Implementation constraints - Bound the manual matrix to agreed combinations and include a reproduction script per barrier. Verification - Run normal booking plus slot-conflict and session-expiry scenarios and record outcomes. - Introduce a missing dialog name or broken return focus in a local fixture; the relevant check detects it. Deliverables - Booking accessibility regression matrix and release decision note Rollout and recovery: Use before pilot expansion; block steps with unrecoverable barriers and retain the documented alternative flow. Project prerequisites: Synthetic services, slots, and booking API contract Keyboard and screen-reader access for a documented manual check Engineer value: Practice accessibility as complete interaction behavior, including recovery and asynchronous updates. Company value: Inspect whether an engineer removes concrete barriers while preserving appointment integrity and supportability. 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.