Restore heading and table semantics in handbook chapters
Every source block becomes a styled div. Readers cannot navigate by heading, and table cells expose no header relationships.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Semantic HTML · Document models · Accessibility
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Headings preserve validated source hierarchy in semantic elements.
- Tables retain captions and source-model header associations.
- Unsupported blocks show a clear fallback rather than silently disappearing.
Implementation constraints
- Validate the structured model; this ticket does not infer semantics from arbitrary visual formatting.
Verification to include
- Navigate by headings and inspect a table with row and column headers.
- Supply an unsupported block and invalid hierarchy; content is not silently lost and validation identifies the issue.
Deliverables
- Semantic block renderer and document-model fixtures
Rollout and recovery
Enable for validated documents; retain the accessible source view when model validation fails.
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.