Verify a complete reading-and-annotation session
Component checks miss interactions among search, resizing, bookmarks, and drafts. Add a short reader acceptance script to the release checklist.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Acceptance testing · Accessibility · Release handoff
Estimated field mix
- Accessibility60%
- Quality engineering40%
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.
- READ-101 · Restore heading and table semantics in handbook chapters
- READ-103 · Navigate search matches without breaking document text
- READ-102 · Let readers adjust text without losing their place
- READ-104 · Keep contents links and footnote returns oriented
- READ-105 · Recover bookmarks after a handbook correction
- READ-106 · Render annotations safely and expose their controls
- READ-107 · Load long handbooks without losing reading order
- READ-108 · Keep annotation review stable through collaborator updates
- READ-109 · Handle access loss without an empty-reader trap
Acceptance criteria
- The script follows contents, changes text settings, searches, annotates, bookmarks, and reopens.
- Keyboard-only and one documented screen-reader pass record observed limitations.
- Version correction and denied annotation save are recovery branches.
Implementation constraints
- Record the environment and observations; automated checks do not establish complete accessibility.
Verification to include
- Run the ordinary synthetic session and verify final bookmark and annotation identities.
- Reject saving and replace the version; the draft stays explicit and ambiguous bookmarks require resolution.
Deliverables
- Reader acceptance script and reproducible barrier notes
Rollout and recovery
Use for navigation/annotation changes; pause the affected feature on identity loss or unrecoverable keyboard failure.
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.