Navigate search matches without breaking document text
Highlighting rewrites innerHTML and removes links around matches. Keyboard users also cannot identify the current match.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Text ranges · Keyboard navigation · Safe rendering
Estimated field mix
- Frontend50%
- Accessibility30%
- Security20%
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
- Highlights preserve source text, links, and semantics.
- Next/previous exposes index and total without rereading the chapter.
- Clearing search restores normal reading at a sensible position.
Implementation constraints
- Treat queries as literal text and use structured ranges; never interpolate search text into HTML.
Verification to include
- Find a phrase spanning emphasis and follow the preserved link around a match.
- Search markup-like text and a no-match query; nothing executes and match navigation is correctly disabled.
Deliverables
- Structured highlight layer and keyboard match-navigation tests
Rollout and recovery
Enable for one renderer; disable highlighting separately while retaining plain results if semantics regress.
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.