Generated reference · Design & accessibility

Design system & accessibility

The authored design-system and accessibility references, indexed at their canonical homes — not minted as a fake unified surface.

8design28a11y

On this page

The design-system and accessibility references (§6) are authored per product and per surface — there is no single token-generated source to render as one canonical page, and minting one would over-claim a unified design system the repo does not have. This surface indexes the real authored design and accessibility docs at their canonical homes, linking each rendered page (or its raw source where it lives beside the code).

8Design-system docs
28Accessibility docs
1Localization reference

Design system#

Tokens, components, variants, and design language — from V1’s design system and the Studio design tree. Each keeps its one canonical home; this only links them.

Accessibility#

A11y requirements and as-built status per surface. The deepest source is the 21-doc V*/docs/accessibility tree (preset profiles, colorblind palettes, screen-reader bridge, photosensitivity, captions, …), kept beside the code and linked here; the per-product accessibility feature pages render in the center.

Per-product accessibility pages

As-built accessibility detail (source tree)

Localization#

The third §6 design-discipline type (locale coverage, VO/subtitle tiers, RTL) has its own generated home — see the generated localization reference, built per-product from each committed locale manifest.

Why an index, not a generated surface: a token-generated design system or a unified a11y matrix would invent a single source the repo does not have (the no-stub-for-docs rule, §11). Indexing the real authored docs is the honest home for both §6 types.