A plan: requirements, milestones, the statement of work
Requirements by capability2 uncovered
Month-end close
Reporting1 uncovered
Access1 uncovered
Milestones in sequence
Press A to pick up, then choose where it goes and press Enter.
Each layer is a list of real buttons — a grouped layer a list of lists, an ordered one
an ol — and the lines are a drawing hidden from assistive technology. Every node's name
says what covers it, so a screen reader hears what a sighted reader sees. Milestone 2 is open, so it
is pressed and its lines are lit; hovering or focusing a node lights its lines the same way.
Drag a requirement onto a milestone to put it there. From the keyboard, A picks
a requirement up, Enter on a milestone puts it down and
Esc puts it back, each step said aloud. The statement of work is where the
sequence ends: dashed, and never a place to drop.
Uncovered, brought forward
Requirements by capability2 uncovered
Month-end close
Reporting1 uncovered
Access1 uncovered
Milestones in sequence
highlight="uncovered" rings what nothing covers; a list of ids does the same
for a search. Uncovered is a dashed edge as well as a tint, and a count in the layer's head and its
group's. This one is read only: nothing drags.
Three layers, and in a narrow pane
Risks1 uncovered
Controls
Release
Below 30rem of its own width — a container query, so a side pane counts as a phone —
the layers stack, the drawing goes and each node says in words what the lines said:
In C1, Not covered.
Three layers, side by side
Risks1 uncovered
Controls
Release