Nodus Design System
A design system you can audit.
The accessibility assessment is published criterion by criterion — eight criteria passing at AA, two partial, with the gaps under the partials named rather than summarised. You do not have to take any of it from us.
The standard, and what you can check
The system targets WCAG 2.1 Level AA, and the assessment is published as a per-criterion table rather than a badge. Eight criteria pass. Two are partial, and both are named: screen-reader support, where the primitives have full coverage and the pattern components lack detailed state announcements for complex status transitions; and error identification, where input components link errors properly and pattern-level errors still surface raw technical strings. Two gaps are listed at the top priority, including missing live regions for real-time status updates. Contrast is stated as a measured ratio — 15.4:1 on light, 14.7:1 on dark — not as a claim of compliance.
Accessibility is also enforced as a merge gate: a component that breaks contrast fails the build rather than shipping with a note attached. That part you cannot check, because the repository is private, and we would rather say so than let a sentence about CI do work a link should be doing. What is public is the assessment, and the assessment is the one that lists failures.
What is in it
- Tokens, not forks. Brand expression lives in the token layer. A venture changes token values, not components.
- Web and mobile. The same component set across both, with dark mode and right-to-left support throughout.
- Agent-facing primitives. Status, audit trails and structured output — the surfaces an interface needs when state changes without a person touching it.
- Documented in public. Component specs, token reference and the foundation sections are on the docs site, open to anyone.
What this page does not claim
This site is not built on the design system. You are reading a page that makes an auditability claim on a surface that does not yet consume the thing it is claiming for, and you would have found that out in about four minutes, so here it is in the first four seconds.
The system does not check anyone else's output. It is a standard you can audit, published with its own failures attached — not a drift detector, and not a governor of code written somewhere else. And the repository is private, so the merge gate described above is a claim, not a receipt.