Build a local-history timeline readers can follow without color
· Practical guide · Hillhouse archive editorial team
A school-history display can look clear in a planning meeting and become difficult to follow when printed in black and white. If blue means a documented date and orange means an estimate, someone who cannot distinguish those colors loses part of the evidence. Keep the color if it helps the design, but write the distinction beside the event.
This guide turns three fictional practice records into a small, text-first timeline. You can reuse the printable HTML template and CSV record sheet for your own local-history project. The examples are not events from Hillhouse, student work, or records held by a school.
1. Write what each visual distinction means
Start with a plain list of the information the design encodes: date, event, category, source and uncertainty. If a visitor needs a legend to know that a yellow box means “date uncertain,” put “Date uncertain” in the box itself. A colored dot can remain as an extra cue.
W3C's explanation of the use-of-color criterion calls for information beyond color when color conveys meaning. For a timeline, short labels are often easier to maintain than a separate set of symbols. Replacing red and green with two other colors does not solve the underlying reliance on color.
Use the same category wording in the worksheet, display and downloadable version. “Documented date” and “Approximate date” describe the evidence more clearly than “good” and “bad.” A record with an approximate date can still be useful.
2. Keep dates and uncertainty in words
Copy the date supported by the source before assigning a position on a graphic. “Spring 2011” is not the same claim as “1 March 2011.” Do not choose an exact day merely because a design tool requires one. For a source with no established date, provide an “Undated” section rather than placing it at the beginning of the chronology as though it happened first.
The practice display below uses a list for its two dated entries and a separate paragraph for the undated record. Dates, categories and uncertainty remain readable without the colored borders.
Practice timeline — fictional records
- 1 September 2010 — Practice session A
Documented date in this fictional example. Practice record DEMO-01, page 1. This label does not represent a real event.
- Spring 2011 — Practice display B
Approximate date in this fictional example. Practice record DEMO-02, cover note. A month and day have not been supplied.
Undated material
Date unknown — Practice photograph C. Practice record DEMO-03, reverse blank. No date is inferred from its place in this example.
3. Make the reading order explicit
A visitor should be able to follow the sequence without following a line across a wide screen. Keep the dated entries in the order you intend them to be read. In HTML, an ordered list can make that sequence explicit; headings and paragraphs explain each entry. W3C's content-structure tutorial describes using meaningful markup for the content being presented.
Avoid rearranging the visible events into a different order from the underlying text just to make two columns fit. If two records share an uncertain period, say that their relative order is unresolved. A timeline can show what is known without manufacturing a complete sequence.
The template downloads as an HTML file from a plain-text source. If your browser opens its source instead, save it with an .html filename. It uses one column and no script. You can edit the text in a text editor, open the file in a browser, and print it. It is a starting point for a small display, not an accessible diagram generator or a substitute for checking a larger exhibit.
4. Carry source locators into the display
For each entry, retain the record title or ID, a page or item locator, and a short note explaining any uncertainty. A general “sources available on request” label makes it harder to check one event. Do not publish private names, contact information or restricted material merely to make a source note more detailed.
The existing field-notes and community-learning guide helps separate an observation from an interpretation before you turn it into a display entry. If an entry comes from an interview, the oral-history question guide addresses how the account was elicited; the permissions and proposed public use still need their own review.
In the CSV, the date-as-written and date-status columns are separate. Keep that separation when replacing the fictional examples. DEMO-01 to DEMO-03 are practice locators only. They are not citations you can reuse as evidence for real local history.
5. Check the narrow and printed versions
- Remove the color cue. Read a grayscale print preview. Can you still distinguish documented, approximate and undated entries from their text?
- Read from top to bottom. Confirm that the sequence and undated section make sense without moving around a two-dimensional chart.
- Use a narrow view. Check the longest title and source locator for clipping or horizontal scrolling. Shorten a label only if its meaning survives.
- Reopen a source. Choose one real entry in your own project and use its locator to find the supporting passage. The fictional practice rows cannot pass this real-source check.
- Ask for feedback in the intended format. A usable browser page does not establish that a printed wall display is readable at its actual viewing distance.
For this template, the editorial checks cover a narrow browser viewport, retained text in print/grayscale styling, source labels and reading order. They do not constitute a screen-reader user study, a physical-exhibit trial or full WCAG conformance assessment. Fonts, contrast, magnification, keyboard behavior and the rest of the surrounding site still matter.
Sources and editorial scope
Primary guidance checked 17 November 2026: W3C WAI, Understanding Use of Color and Content Structure, linked above. The display, template and CSV are original teaching materials with explicitly fictional records. This independent archive team does not represent the former school, and no classroom results or participant feedback are claimed.