Repair an HTML report’s structure, links, table and diagram alternative so it remains understandable without visual styling.
A fictional project report contains a heading hierarchy, a two-row status table and a diagram showing draft → review → approved. The initial draft relies on red and green labels and click here links. The task is to make the same information explicit in text and structure.
| Work item | Status | Next action |
|---|---|---|
| Registration form | Needs review | Check error messages |
| Attendance export | Approved | Retain reviewed version |
A document may be read visually, with assistive technology, at high zoom or without its original styling. Organize meaning before decoration. Use a clear title and logical headings, and keep essential explanations in text. The exercise repairs an HTML report rather than claiming a fully tagged PDF or Word file.
Outline the report and assign heading levels.
Semantic outline
Record your result and evidence here or in a separate file.
Heading order expresses the actual section hierarchy.
Change styles for appearance instead of skipping structural levels.
An alternative should communicate the image’s role in the document. A process diagram needs its sequence and any decision condition, not a list of colors and shapes. Complex information can use a concise alt plus a nearby detailed explanation. Decorative images may need empty alternatives, but this diagram carries meaning.
Write an alt and a text equivalent for draft → review → approved.
Diagram alternative
Record your result and evidence here or in a separate file.
The approval condition is available without seeing the arrows.
Describe the relationship and condition instead of the drawing style.
Use table headers for the dimensions a reader needs to interpret each cell. Keep the table small and avoid using it only for page layout. Link text should remain meaningful when encountered outside a paragraph. Preserve the actual destination and avoid invented download links in a local prototype.
Build the status table and replace two vague links with descriptive labels.
Structured report section
Record your result and evidence here or in a separate file.
Each row status is explicit text and headers identify the columns.
Add a caption and header cells before styling the table.
Color can reinforce meaning but cannot carry it alone. Check text contrast and inspect the report at high zoom. A last-minute edit can break heading order, links or alternatives, so include accessibility in the revision checklist. Automated checks help, but they do not prove the entire reading experience is accessible.
Review the report at 200% zoom and without color cues.
Accessibility review log
Record your result and evidence here or in a separate file.
Status and navigation remain understandable without red/green distinction.
Add words or symbols with text equivalents rather than only stronger colors.
A reusable report template should preserve semantic defaults and explain how to add new sections correctly. Record what was reviewed and what remains untested. This package does not claim screen-reader testing unless actually performed. Give the next editor a short checklist tied to the document’s real components.
Create the final HTML report and editor checklist.
Accessible report template
Record your result and evidence here or in a separate file.
The handoff distinguishes automated inspection from human assistive-technology testing.
Remove blanket accessibility-compliant claims unsupported by the review.
Deliver the revised HTML report, heading outline, table, descriptive links, diagram alternative and review log. Add one new section and show that the hierarchy remains coherent.
Essential meaning does not depend on color, visual position or an image alone.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The diagram’s meaning is: a draft enters review and becomes approved only after the reviewer accepts that version. The status table explicitly says Needs review or Approved, so meaning survives removal of red and green styling.
This is an accessible-document practice template, not a certified PDF/Word artifact or a complete conformance audit.