Interface Core C · Industry convention

Timeline

A timeline puts events, states, or milestones in time order along one visible path.

See how it works

You might call it event historyactivity timeline

See how it works

Original worked exampleTimeline

CHRONOLOGICAL SEQUENCETimeline<ol> + <time>

08 JulResearch synthesisFive patterns agreed
15 JulPrototype reviewKeyboard path revised
22 JulAccessibility auditTwo issues in progress
30 JulRelease candidatePending evidence review

<ol> + <time>▦

TimelineINTERFACE COLLECTION

Another example

A delivery timeline shows the exact dates for order placed, packed, sent, delayed, and delivered.

Main parts

01Trigger or task context
02Primary control surface
03Feedback, focus, and dismissal

Use it when

Use it when time and order help people understand progress or history.

Do not use it when

Never draw connecting lines only for decoration when the events have no meaningful time order.

Name used in code

<ol> + <time>

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Timeline to solve this user need without losing the current context. User context: A delivery timeline shows the exact dates for order placed, packed, sent, delayed, and delivered. Recommended pattern: Timeline. Why it fits: Use it when time and order help people understand progress or history. Do not use it when: Never draw connecting lines only for decoration when the events have no meaningful time order. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Timeline. Definition: A timeline puts events, states, or milestones in time order along one visible path. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

How official is this term?

Industry convention

How evidence levels work How this page was made

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope: Content-presentation convention
Document status: not applicable
Checked on: 2026-07-30

Evidence sources & scope

Background sourceNo single authoritative definitionPeople use this name at work, but no one official source defines all of it. Vibulary wrote this meaning and example as learning help.