Contents beside the sheet — reviewed, live, current
Three hierarchies are in use at once S4, and the reporting team rebuilds its own every quarter S7. A fourth was mentioned once and never produced S12 (source not found).
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
The rail is held to the window and scrolls inside itself, so a contents list of
seventy-eight sections reaches its last entry. The current entry is aria-current="location";
a long heading is held to two lines with the rest in its title. Reviewed marks are the caller's
keys, so a mark can lapse when the section is rewritten. Below 1100px the rail goes above the sheet.
Rewritten in this run is a small dot, not a tick: the review box draws the tick. Where an entry is reviewed the dot is left out and the screen-reader words stay (compare 2.4 above, reviewed, with 2.4 in the plain list below).
Contents — plain
Contents — arriving
Source card — in a hover card on a citation
S4Internal Ops Meetings — Running Notes.docx
Page 3
“We have the ledger hierarchy, the reporting one, and whatever sales ops keeps in their sheet — and they all disagree about who rolls up to whom…”Open at Passage
S7Reporting Team Interview — 14 Oct.m4a
S12Q3 Hierarchy Review.xlsx
This source is not in the corpus, so the passage cannot be shown.
The markers live in sanitised HTML, so the card is opened by
useDelegatedHoverCard: delegated events on the container, the same dwell, grace,
Escape and placement as HoverCard. A missing source is a dashed marker that says so,
never a link to a page that will not load.
Drawer with a head — stepping through sources
Attendees: finance operations, reporting, sales operations.
Discussion of the month-end variance. Reporting traced it to a reclassification in the ledger that had not reached the sales operations sheet.
We have the ledger hierarchy, the reporting one, and whatever sales ops keeps in their sheet — and they all disagree about who rolls up to whom.
Action: reporting to propose a single owner for the hierarchy before the next close.
Drawer header size="lg": the head is pinned and the body scrolls
beneath it. PagerChip steps with its buttons, or with ← and → when
arrowKeys is on — never from inside a field.
Keys
Press J and K to move through findings, Enter to open one.
Shortcut help — every key the page binds, and the off-switch
Inbox
Everywhere
ShortcutHelp lists what each screen registered with
useShortcuts, grouped by screen, and the switch WCAG 2.1.4 asks for. The switch is
stored per person by ShortcutsProvider. Put it behind a visible "?" button as well as
the ? key — with single keys off, the key no longer opens it.
useListKeys moves real focus through a list: J and K from anywhere,
the arrows, Home and End once in the list, Enter to open, and any single key the page binds. Never
while typing in a field, and never under a dialog that does not hold the list.
Contents in a scrolling pane — --paper-aside-viewport-offset
Scroll to the end of the page: the frame pins to the top of the window, so it stands in for an app. A 64px bar, then a pane that scrolls. The rail is capped at the window height less the pane's offset (64px), its sticky gap and a bottom gap, so its last entry stops inside the window. Scroll the pane: the rail stays put and keeps its bottom gap.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.
Each hierarchy is correct for the team that keeps it. The disagreement surfaces only at month-end, when the board pack rolls them up together.