Ticket

A paper pass: what it's for on the main part, the code on a stub across a perforation. Use it and the stub tears off along the perforation and drops away, leaving the torn edge and "Used". For event tickets, boarding passes, coupons, invites and gift cards. The same paper and ink as Receipt; on a narrow screen the stub goes under the main part.

Feel A cinema ticket: the stub tears off along its holes when you go in.

Night Session

Warehouse 9, Leeds

Date: Sat 3 Oct
Doors: 19:30
Entry: B

Admit one

NS-3010-0412

Or let the agent fetch it: get_component("ticket") on the Echo MCP server.

Installation

npx echo-ui-cli add ticket

First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.

At a glance

Version: 0.3.0
Weight: 1.7 KB · 31.1 KB with what it imports · 3.1 KB of CSS (minified and gzipped; React not counted)
Needs: hardware-button (Echo, brought with it), receipt (Echo, brought with it)
Keyboard: Tab reaches the button that uses it; Enter or Space uses the ticket.
Reduced motion: The stub fades where it is instead of dropping away.
Sound: A tap as the stub tears, inside a SoundProvider.

Usage

tsx

import { Ticket } from "@/echo/ticket";

<Ticket title="Night Session" code="NS-3010-0412" />

Composition

Ticket
  the main part: the heading, the subtitle, the details (a description list)
  the perforation
  the stub: its label, a barcode, the code
  HardwareButton (use it, with onUse)

Examples

An event

The details, and a stub to tear at the door.

tsx

<Ticket
  title="Night Session"
  subtitle="Warehouse 9, Leeds"
  details={[
    { label: "Date", value: "Sat 3 Oct" },
    { label: "Doors", value: "19:30" },
    { label: "Entry", value: "B" },
  ]}
  code="NS-3010-0412"
  stubLabel="Admit one"
  onUse={checkIn}
/>

Already used

The stub's gone; the ticket says so.

tsx

<Ticket title="Coffee on us" code="FREE-7731" defaultUsed />

Accessibility

A section named by its heading; the details are a description list, each label read with its value.
The barcode is a picture and is hidden; the code is printed beneath it as text.
Using it is a button, and a used ticket says "Used" in text where the stub was.
The ink is the same as Receipt's, held to AA contrast on the paper under every theme.
Keyboard: Tab reaches the button that uses it; Enter or Space uses the ticket.

Tested against WCAG 2.2 AA on every release:

axe — No axe violations, in the component's own gallery and on its page.
keyboard — Every action is reachable and operable from the keyboard alone.
focus-visible — Focus is visible on every focusable part, in normal and forced-colors mode.
forced-colors — State stays visible when the look's colours are replaced by the system's.
target-size — Every target's real hit area is at least 24×24px, at every density.
reflow — Content reflows into 320px and survives a doubled text size.

Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.

Motion & sound

Motion tokens: flood, pop
Reduced motion: The stub fades where it is instead of dropping away.
Sound: A tap as the stub tears, inside a SoundProvider.

Props

Ticket props
Prop	Type	Default
`title` requiredWhat it's for, printed large, and the ticket's heading.	`string`
`subtitle`Where, or who it's from.	`string`
`details`The facts on the main part: a date, a door, a seat.	`object[]`
`code` requiredThe code on the stub, as a barcode and in text.	`string`
`stubLabel`Printed on the stub over its code: "Admit one", "Boarding".	`string`
`used`Torn off (controlled).	`boolean`
`defaultUsed`Whether the stub starts torn off (uncontrolled). See used.	`boolean`	`false`
`onUse`Called once the stub has dropped away. With it, the ticket shows a key to use it.	`function`
`useLabel`The key's word.	`string`	`"Use ticket"`
`headingLevel`The heading's level.	`2 \| 3 \| 4`	`3`

Anti-patterns

Never make the barcode the only copy of the code: people read codes out and type them in.
Never offer to use a ticket that can't be used yet: disable it, or leave out onUse and say when it opens.

Changelog

v0.3.0 · 2026-10-12 · ChangedEvery item needs echo-ui-core 0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declares echo-ui-core >=0.3.0 <0.4.0. Update core with the items: npm install echo-ui-core@^0.3.0 (or your package manager's), then npx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published.
v0.2.0 · 2026-10-04 · AddedThe light device (echo-ui-core, echo-ui-cli). Echo can be light: a pale chassis makes a device molded in light plastic, like a white calculator or a cream radio, and a dark one makes the device Echo has always been. There's no setting and no mode to switch; the chassis decides (devicePolarity, and values.polarity on the theme). On a light device the page is light: its ground, the well, is the body barely set in. Caps get their own ladder, a step lighter than the body with a lit rim that stops short of white, so they keep their bevel; undersides and seams are shaded darker; dim text moves toward the ground by the same step as on a dark device, and reads about 6:1 on it. Screens are paper glass printed in ink, because a glow on a pale body is a smudge. What's lit (an LED, the current rail) is still the accent, held to 3:1 on every ground, so on is brighter than off; the text it prints (a readout, a count, a current tab) and the focus ring are the accent's ink, a step deeper and held to AA, in the new accent-ink role. The primary cap is the same cap as a dark device's, the accent with a light label: its label is the new primary-cap-ink role, and progress cells, loader dots and a meter's fill, the same plastic, read 3:1 on the page. A neutral cap or a slider that fills with it under its own dark label fills with the new pour-* roles, the accent's pale stops. Shadows are drawn at half their weight, in a deep colour of the body's own hue (--echo-cast-ink) instead of black. Every guarantee holds as it does on a dark device, and the contrast sweep now runs on light bodies too. A dark seed makes exactly the theme it did before, and the new roles equal the ones they stand for there. The components that mixed a recess toward black, painted paper in the text colour or lit a pillow of light with it read the theme's new --echo-shade-ink, --echo-paper-stock and --echo-paper-ink instead, with the old value as the fallback, and a reflective screen reads --echo-screen-*; the components that print a lit label read --echo-primary-cap-ink and --echo-accent-ink the same way; every rail is drawn in the glow, and every focus ring, the ring recipes included, in the ink. style use wears a light style now, and style check says which device a style makes. A dark screen tint on a light body is still refused: one text colour can't serve both, and the theme says so.
v0.2.0 · 2026-10-04 · AddedTicket: a paper pass with a stub. What it's for on the main part, the code as a barcode on a stub across a perforation; use it and the stub tears off and drops away, leaving "Used". The same paper and ink as Receipt; on a narrow screen the stub goes under.
v0.2.0 · 2026-10-04 · ChangedComments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (HardwareButton's engraved/caption checks and StatusDot's missing-label check) also dropped the ticket code at the end of the message. echo-ui diff will show changes in most items; none of them are to code.
v0.2.0 · 2026-10-04 · ChangedAn item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "Menu and Sheet are unchanged here" filed itself as a change to Menu and Sheet — which it really had.
v0.2.0 · 2026-10-04 · ChangedThe agent brief says Echo has not shipped. llms.txt and the MCP server's instructions led with npx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affects all components only in what the brief says about installing them; no item's props, CSS or rendered semantics change.
v0.2.0 · 2026-10-04 · ChangedEcho's home is echo-ui.com. The registry, the docs and the packages all move to it from echo.nawwara.studio. Nothing was published under the old host, so no echo.json anywhere points at it and there is nothing to migrate — this is the last release where that is true.
v0.2.0 · 2026-10-04 · ChangedWeights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in all components, with the old value as a fallback, so components keep working with echo-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19).
v0.2.0 · 2026-10-04 · FixedA light device's recesses keep the body's hue in Chromium (echo-ui-core, BUG-166). Chromium drops the hue of a colour under 0.02 chroma when it mixes in oklch, and draws the mix at hue 0, a rose. A light device's plastic is that grey, so on a lilac body every field, track and rail was pink. A mix made only of greys is made in oklab now, which has no hue to lose; a mix with an accent in it stays in oklch. On a dark device nothing you can see changes.
v0.2.0 · 2026-10-04 · FixedContent now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across all components. Select's 180px floor, NumberField's readout, Segmented and Steps as flex items, EmptyState's grid columns, and Avatar's fixed-pixel disc all gave way; Panel counts its padding inside a width you set (box-sizing: border-box), so a <Panel style={{ width: 220 }}> is now 220px wide overall rather than 260px.

Preview