Task library READ Accessibility · Phased project A document reader that keeps people oriented 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.
Practice brief · Version 5
Project scope 10 tickets / 4 phases
Total focused work estimate 21h 15m + setup
Suggested stack React · TypeScript · CSS Modules · Testing Library · Playwright Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with READ-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice semantic structure, accessible navigation, safe annotations, and stable reading positions.
What the team gains Inspect how an engineer makes information usable while protecting document integrity and access boundaries.
Before you start Versioned synthetic documents with stable section IDs Annotation and document-access API contracts to stub Delivery agreement Each ticket targets one reader behavior. Use synthetic documents and record assumptions about the source model.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Preserve semantics and text preferences.
PHASE 2 Make search, contents, and bookmarks predictable.
PHASE 3 Add annotations and long-document loading without breaking reading flow.
PHASE 4 Check interruptions and document the release boundary.
Make content readable Preserve semantics and text preferences.
READ-101 Entry ticket; project setup still required Estimated field mix
Accessibility 60% Frontend 40% READ-102 Depends on READ-101 Estimated field mix
Accessibility 50% Frontend 50% Keep the reader oriented Make search, contents, and bookmarks predictable.
READ-103 Depends on READ-101 Estimated field mix
Frontend 50% Accessibility 30% Security 20% READ-104 Depends on READ-101, READ-102 Estimated field mix
Accessibility 60% Frontend 40% READ-105 Depends on READ-103, READ-104 Estimated field mix
Frontend 70% Accessibility 30% Support richer reading Add annotations and long-document loading without breaking reading flow.
READ-106 Depends on READ-103, READ-104 Estimated field mix
Security 40% Accessibility 30% Frontend 30% READ-107 Depends on READ-102, READ-104 Estimated field mix
Performance engineering 40% Accessibility 40% Frontend 20% READ-108 Depends on READ-105, READ-106, READ-107 Estimated field mix
Frontend 50% Accessibility 30% Real-time systems 20% Verify access and recovery Check interruptions and document the release boundary.
READ-109 Depends on READ-107, READ-108 Estimated field mix
Security 40% Accessibility 30% Frontend 30% READ-110 Depends on READ-105, READ-108, READ-109 Estimated field mix
Accessibility 60% Quality engineering 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.