Accessible Document Design
Project workbook · Path 95

Repair an HTML report’s structure, links, table and diagram alternative so it remains understandable without visual styling.

The case

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 itemStatusNext action
Registration formNeeds reviewCheck error messages
Attendance exportApprovedRetain reviewed version
STAGE 1

Design for varied reading needs

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.

Your task

Outline the report and assign heading levels.

Required output

Semantic outline

Record your result and evidence here or in a separate file.

Review gate

Heading order expresses the actual section hierarchy.

If the gate is not met

Change styles for appearance instead of skipping structural levels.

STAGE 2

Write useful alternatives

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.

Your task

Write an alt and a text equivalent for draft → review → approved.

Required output

Diagram alternative

Record your result and evidence here or in a separate file.

Review gate

The approval condition is available without seeing the arrows.

If the gate is not met

Describe the relationship and condition instead of the drawing style.

STAGE 3

Repair tables and links

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.

Your task

Build the status table and replace two vague links with descriptive labels.

Required output

Structured report section

Record your result and evidence here or in a separate file.

Review gate

Each row status is explicit text and headers identify the columns.

If the gate is not met

Add a caption and header cells before styling the table.

STAGE 4

Review contrast and editing pitfalls

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.

Your task

Review the report at 200% zoom and without color cues.

Required output

Accessibility review log

Record your result and evidence here or in a separate file.

Review gate

Status and navigation remain understandable without red/green distinction.

If the gate is not met

Add words or symbols with text equivalents rather than only stronger colors.

STAGE 5

Prepare a maintainable document

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.

Your task

Create the final HTML report and editor checklist.

Required output

Accessible report template

Record your result and evidence here or in a separate file.

Review gate

The handoff distinguishes automated inspection from human assistive-technology testing.

If the gate is not met

Remove blanket accessibility-compliant claims unsupported by the review.

Final project

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.

Critical condition

Essential meaning does not depend on color, visual position or an image alone.

CriterionPointsEvidence
Evidence and correctness30Calculations, source use and results match the supplied case; limitations are honest.
Required artifacts30All five stage outputs and the capstone handoff are present and inspectable.
Reasoning and decisions20Choices, assumptions, alternatives and the case-specific critical condition are explained.
Reproducibility10A reviewer can follow the stated steps and distinguish expected from observed results.
Clear communication10Labels, 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.

Worked reference

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.

Boundaries

This is an accessible-document practice template, not a certified PDF/Word artifact or a complete conformance audit.