Registry 4.45 and later. The values on this page are the owner’s ruling of 19 November 2026,
and they ship in the registry from version 4.45.
What the floor is
Nothing readable is smaller than 14px. Nothing interactive has a hit region smaller than its
tier’s minimum: 45px on touch, 24px on a desktop. The drawn size of a control is set separately,
and a hit region is a floor under it, not a size for it.
The numbers live in one place in the registry,
BUNDU_FLOOR in lib/tokens/roles.source.ts,
with the desktop tier under pointerFine. The token generators, the contract runner, the Rust
evaluator and the registry’s tests all read it.
How the floor has moved
Body text has been 17px on touch and 15px on a desktop since the desktop tier, and the owner’s
19 November ruling does not change it.
Tiers
The layers are defined once in the token layer and emitted as media queries on the size variables. A component never branches on screen size.
The control sizes on the rule are 28, 33, 36, 41, 48, 49 and 56px. On a desktop a control is drawn at
one of the smaller sizes, from 28 to 41px. A field is 36px on a desktop, and 33px in its compact
form. A standard button on touch is drawn at 49px, and the large button at 56px. The 45px touch floor
is a hit region, not a drawn size.
On a desktop, large body text (
text-body-lg) is 17px, and a caption stays 14px. Only display and
heading sizes step down as screens grow, and body text steps down once, at the desktop tier. A
touchscreen laptop reports a coarse pointer (any-pointer: coarse), so the desktop layer does not
apply to it, and neither does it apply to a tablet.
Density is about visual size only. Screen size is never used to guess network quality, and the
gaps between targets are spacing tokens that density does not change.
How a control keeps its hit region
On touch, a control keeps a 45px hit region even where it is drawn smaller. The token layer’shit-area rule gives every button, summary, [role="button"], [role="tab"],
[role="switch"] and any .hit-area element a transparent ::after of
max(100%, var(--target-floor)). --target-floor is 2.8125rem (45px) on touch, and only the
desktop density layer lowers it, to 1.5rem (24px) and not below. On a desktop a control is drawn at no less than 28px, and its hit region is at least 24px. Its drawn
box is its hit region when it is drawn at least 24px, and it needs no pseudo-element.
The rule steps aside on purpose for an element that draws its own after: pseudo-element
(checkbox, switch, radio group, the tabs line variant), for menu and listbox rows (they take
min-height: var(--target-floor) instead), for a calendar day, and for an element with
overflow: hidden, which would clip it. Three consequences matter when you build:
- A native
input,selectortextareacannot carry a pseudo-element, so the field roles (h-field,h-field-sm) are drawn at their component height, 49px on touch, which is above the 45px hit floor, and on a desktop 36px (33px in the compact form). Their drawn box is the hit region. - A standalone link that is a target is drawn at 45px on touch and 24px on a desktop at least, or
takes the
hit-areaclass. An inline link in running text is exempt, as in WCAG 2.5.8. - Where two covered controls sit closer than 45px apart on touch, their overlays overlap and the later sibling wins the overlap, so keep gaps from the spacing tokens.
Contrast beside the floor
The floor’s contrast numbers are WCAG 2 minimums: 7:1 for body text, 4.5:1 for non-body text and 3:1 for UI parts. The registry’s token build fails when a default role is under its minimum, and the APCA bars still apply. Five button-label roles hold 4.5:1 rather than 7:1, an owner-confirmed exception:primary-foreground, brand-accent-foreground,
app-accent-foreground, sidebar-primary-foreground and destructive-foreground. The thresholds,
the reason for the exception and how to test a pairing are on
accessibility.
Migrating
The 19 November ruling changes the hit regions, the spacing and the control heights. Body text, captions, line height and contrast do not change.
The size roles set on 1 November 2026 moved again on 3 and 12 November. An app that still uses
the 1 November sizes can use this table to see what it has to change:
In an app:
- Take the registry version (or
@bundu/uibuilt from it) and re-runpnpm tokens:syncor re-copymzizi-tokens-globals.css. - Replace
h-12,h-14andmin-h-[44px]on a control with a size role (h-control,h-field,min-h-touch-min). On a desktop a control is drawn at 28 to 41px, and its drawn box is the hit region, which is at least 24px. On touch a control never goes under 45px. - Replace any
text-[Npx]under 14 withtext-sm, and write body copy astext-body. - If a layout breaks and cannot move yet, set the legacy alias (below) and plan the move.
The legacy alias
To take the version and keep the earlier sizes for a while, put the attribute on the root element:text-xs and text-body follow the same variables, so they step out
with it.
One class name to avoid
Write body copy astext-body, not text-base. The token layer registers --text-base (17px),
but a theme that also defines a colour named base (--color-base) can make text-base
ambiguous. The registry has not yet decided how to settle it; text-body, text-sm and text-xs
work meanwhile.
What fails the build
The registry’sbundu-floor test fails when a default type step is under its floor in any layer,
when a floored size role is under its tier’s minimum (45px on touch), when the desktop layer
lowers --target-floor below 24px or the hit-area rule is gone, when a desktop control is drawn under its 28px drawn minimum or its hit region is under 24px, when a copy of the floor disagrees with BUNDU_FLOOR, or when a registry component
names an arbitrary text size under 14px. The contract runner and the Rust evaluator fail a density
row whose interactive control has a hit region under 45px on a coarse pointer or 24px on a fine
one. Rows that predate the floor are pinned, so a new one cannot join them unseen; see
the Dashboard Standard’s density table.
The Bundu Order
The Bundu Order draws on biblical mathematical patterns and prime numbers (owner, 2 November 2026). This section states only what the registry’s code holds, in itsbrand-guidelines
doctrine page.
- The unit is 7px (
--radius-unit). The radii are 4, 7, 12, 14 and 17px and a pill, and they do not change. - P7 and P17 are prime steps of the surface-elevation ladder (
surfaceis P7,raisedis P17), and the seven experimental colour families are a heptagon of hues offset 17 degrees. - The floors derive from the same numbers. Body text is 17px on touch, a prime and Apple’s iOS default, and 15px on a desktop (the owner’s number). Captions are 14px (2 × 7). Every control keeps a hit region of 45px on touch (3 × 15, the nearest Mzizi number above Apple’s 44 pt) and 24px on a desktop (3 × 8, WCAG 2.5.8), never smaller.
Sources
- The owner’s rulings of 2 November 2026 (touch 49px), 12 November 2026 (desktop 28px, #660) and 19 November 2026 (touch 45px, desktop 24px, layered spacing).
- The registry’s
sizes-and-density.md(the migration guide) and itscontent/doctrine/documentation/brand-guidelines.mdx. - Registry 4.45 and later, through the MCP operations
get_tokens(family=floors) andget_doctrine(topic=bundu-floor), once the MCP server is repinned to that release. - The other systems: the standards comparison, which lists WCAG 2.2, Apple’s Human Interface Guidelines, Material 3 and Anthropic’s brand guidelines.