CCAL-101 · Read the schedule

Name staffing shifts independently of calendar color

Practice briefBugFoundational

Shift type is conveyed only by blue or green blocks. Add visible labels and complete accessible names.

Focused work estimate: 1h + prerequisites
Priority in the scenario: High
Engineering practice: Semantics · Accessible names

Estimated field mix

Accessibility80%
Frontend20%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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.

Use in my work board View project and downloads

Project context

Fictional studio Loom assigns editorial shifts. Build synthetic shifts and a local scheduling adapter; no real staff records are used.

Setup prerequisites

Create synthetic shifts including overlaps and daylight-saving boundaries.
Implement a local schedule revision adapter.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

Type appears as text
Names include date and duration
Color remains optional reinforcement

Implementation constraints

Do not concatenate decorative icon names.

Verification to include

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.

Value of the work

For the engineer: Practice focus models and accessible alternatives for spatial interfaces.

For the team: Inspect whether scheduling remains usable across input methods and failure states.

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.