StopTimeline

No Base UI part, so nothing from Base UI here: the timeline is read, not operated. It takes no focus, and no key does anything.

A next stop reads "Nørreport, Next stop, 08:14, 3 min late", and a passed one "Forum, Passed, 08:10, On time". With an expected time it reads "Nørreport, Next stop, 08:14, Expected 08:17, 3 min late": the word "Expected" tells the ear what the "~" tells the eye, as the state's word does for DepartureRow's "~". A cancelled call reads "Vesterport, Cancelled, 08:16": "Cancelled", read before the time, tells the ear what the line through it tells the eye, as in DepartureRow's "5C, Husum Torv, Cancelled, 4 min, 08:14".

The next stop's list item carries aria-current="step" beside its "Next stop" words: it is the attribute ARIA gives for the current step in a sequence, so a screen reader names the stop as current when it lands on it from anywhere in the list, while the words say why.

What axe won't catch, from the contract, each with how this component meets it:

• Everything the eye is told, the ear is told, for every shape each prop accepts: the filled marker and the "Next stop" words say which stop is next, heard as "Next stop" and aria-current="step"; the set-back colour of a passed stop is heard as "Passed"; a cancelled call's danger colour and struck-through times are heard as "Cancelled", before the times (CR-14); the "~" before an expected time is heard as "Expected", with the time (CR-15); the rail and the line's colour are decoration, the line named in words by the panel around the timeline; each Delay says its delay in words; a stop with no time or delay shows and says nothing for it; with no nextStopIndex, nothing is set back or marked, and nothing is said
• Every landmark and named region has an accessible name: none here; the root is a list, not a region, and takes the caller's aria-labelledby when the panel names it
• Every default label can be overridden: nextStopLabel, passedLabel, cancelledLabel and expectedTimeLabel, and Delay's five, minutesUnitLabel, minutesLateLabel, minutesEarlyLabel, onTimeLabel and delayUnknownLabel
• Every shape the type accepts renders, in every variant: an empty stops renders an empty list; one stop renders with no rail; each stop with and without time, expected and delay, and delay as a number and null; a stop with only an expected, and an empty expected, which shows nothing; cancelled true and false, on a passed, a next and an upcoming stop, with and without an expected; a trip with no expected keeps no column for one; nextStopIndex left out, at the first stop, in the middle, at the last stop and past it, negative or not a whole number (CR-2); every line value and none; a long name wraps under itself
• A hidden copy kept for animation is aria-hidden, and a collapsed region is inert: none here; nothing animates or collapses. The rail and marker are aria-hidden because they are decoration, not copies
• Native semantics first: <ol> and <li> for the ordered stops, <time> for each time and each expected time, aria-current the one attribute ARIA adds, and aria-hidden on the decoration and the "~". A cancelled call's times are struck through by CSS, not wrapped in <s> or <del>; the word "Cancelled" carries it
• Focus moves in reading order and returns on close: the timeline takes no focus
• Every target is at least size.target-min square: no target; the stops are not pressed (CR-8)
• Loops stop when the system asks for less motion: none here; nothing moves

The stop names, times, expected times and delays are the caller's data; the words of a stop's place in the trip, "Cancelled" and "Expected" are the pattern's own, and Delay's words are Delay's, overridable here through the props above. Each word is a text run of its own, so expectOwnedStrings reads it as a dictionary value, and the heard expected time is one template filled with the time, which expectOwnedStrings matches against the template.

nextStop and passed are new, each with a JSDoc line like its neighbours in en.ts, and agents write their Danish, Swedish and Norwegian. Neither is a data-state, delay or disruption word, so neither joins content design's table.

cancelled is DepartureRow's key, "Cancelled", already in content design's table, whose JSDoc names a trip's stop as well as a departure: a cancelled call and a cancelled departure say the same word on every screen. expectedTime came with the expected time, "Expected {time}", with the Danish "Forventet {time}", the Swedish "Beräknad {time}" and the Norwegian "Forventet {time}": a template filled by interpolate, never the word set beside the time in code, as the contract's Words asks of a string that wraps the caller's words, so a locale can put the time where its grammar needs it. It is named for what it says, as DisruptionCard's fromTime and untilTime are. It is its own word, not the data state's "Estimated": "Estimated" says how a vehicle was placed, and an expected time can come from a live vehicle. Like passed it is heard and never seen, since the "~" says it to the eye, and it is not a data-state, delay or disruption word, so it does not join content design's table.

The next stop shows "Next stop" in words under its name, as well as its filled marker, and a passed stop says "Passed" to the ear only: StationIcon's spec asks that a filled stop's meaning be said in words beside it, and a sighted rider learns the filled marker from the words; a passed stop's set-back colour is plain to the eye in its place in the list, so "Passed" in every passed row would only crowd it, while the ear, which can't see the colour, hears it.

For a caller using the pattern, with the reason. Each row is a rule: a must row's Don't is never right, a should row's needs a reason, and Checked by says what catches the Don't in a caller's code.