Keep contents links and footnote returns oriented
Contents links scroll to sections but leave focus in the sidebar. Following a footnote returns to the document top.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Focus management · Deep links · Navigation
Estimated field mix
- Accessibility60%
- Frontend40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
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.
Project context
The fictional Plainview handbook reader serves versioned HTML documents with headings, tables, footnotes, and annotations. Scope is accessible HTML rendering from a structured model; OCR and arbitrary PDF remediation are excluded.
Setup prerequisites
- Versioned synthetic documents with stable section IDs
- Annotation and document-access API contracts to stub
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Contents navigation updates the URL and focuses the destination heading without obscuring it.
- Footnotes offer a named return action to the originating reference.
- Back restores the preceding meaningful reading anchor.
Implementation constraints
- Use stable source IDs and respect reduced motion for scrolling.
Verification to include
- Navigate by contents, follow a footnote, and return using only the keyboard.
- Open a missing section link and use Back; show a useful fallback without trapping focus.
Deliverables
- Anchor/focus coordinator and footnote walkthrough
Rollout and recovery
Ship stable anchors before custom scrolling; disable scroll effects if focus and visual position diverge.
Value of the work
For the engineer: Practice semantic structure, accessible navigation, safe annotations, and stable reading positions.
For the team: Inspect how an engineer makes information usable while protecting document integrity and access boundaries.
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.