Let readers adjust text without losing their place
Increasing font size resets the chapter to the top, while dark theme leaves footnotes unreadable. Add preferences that preserve position and cover every content type.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- CSS variables · User preferences · Reading UX
Estimated field mix
- Accessibility50%
- Frontend50%
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
- Font size, spacing, and theme apply to body, footnotes, tables, and annotations.
- Preference changes preserve the current section anchor.
- System theme is the initial default and invalid stored preferences recover safely.
Implementation constraints
- Use semantic CSS variables and avoid fixed content heights.
Verification to include
- Resize text midway through a chapter; the current section stays in view.
- Load corrupt preference data and test dark/system themes; content stays readable and defaults recover.
Deliverables
- Reader preferences and theme/content fixture page
Rollout and recovery
Release session-local preferences first; disable persistence if stored values break rendering.
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.