Visual review
The identity holds together. The improvements are about making it easier to use: stronger examples, complete guidance and a clearer route from a brand rule to an interface.
Keep the black glass, one amber accent, monochrome wordmark, Space Grotesk and JetBrains Mono. This review does not propose new pillar colours or another logo.
Forms: make the label stay
Section titled “Forms: make the label stay”A placeholder disappears when someone types. A visible label, connected help and a specific error keep the task clear throughout. The form controls now share those patterns.
Native controls work. Demo links and submissions stay inside this specimen. This example scrolls horizontally at this width.
Source markup
<!-- @dsCard group="Inputs" height=640 -->
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Input</title>
<style>
/* Preview layout only; the host supplies tokens.css and bundle.css. */
.demo { display: grid; gap: var(--space-md); padding: var(--space-sm); }
.demo__states {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(min(100%, calc(var(--space-3xl) * 3)), 1fr));
gap: var(--space-md);
align-items: start;
}
.demo__state { display: grid; gap: var(--space-2xs); min-width: 0; }
/* Static copy of .input:focus-visible. Native keyboard focus also works. */
.input.is-focus {
outline: var(--focus-width) solid transparent;
outline-offset: var(--focus-offset);
border-color: var(--color-semantic-border-strong);
box-shadow: var(--shadow-focus-ring);
}
</style>
</head>
<body>
<main class="demo">
<h1 class="t-h3">Input</h1>
<p class="field__help">Static state examples. Editing works; validation and submission are not connected.</p>
<div class="demo__states">
<div class="demo__state">
<p class="t-label">Rest</p>
<div class="field">
<label class="field__label" for="nz-alias">Alias (optional)</label>
<input class="input" id="nz-alias" name="alias" type="text" placeholder="For example, nightjar" aria-describedby="nz-alias-help">
<p class="field__help" id="nz-alias-help">Choose the handle to display beside your message.</p>
</div>
</div>
<div class="demo__state">
<p class="t-label">Valid example</p>
<div class="field">
<label class="field__label" for="nz-email-valid">Email</label>
<input class="input input--valid" id="nz-email-valid" name="email-valid" type="email" value="signal@example.com" aria-describedby="nz-email-valid-help">
<p class="field__success" id="nz-email-valid-help">Valid format example. Delivery has not been checked.</p>
</div>
</div>
<div class="demo__state">
<p class="t-label">Error</p>
<div class="field">
<label class="field__label" for="nz-email-bad">Email (required)</label>
<input class="input input--error" id="nz-email-bad" name="email-bad" type="email" required value="signal@" aria-invalid="true" aria-describedby="nz-email-bad-help nz-email-bad-error">
<p class="field__help" id="nz-email-bad-help">Include the part after the @ sign.</p>
<p class="field__error" id="nz-email-bad-error">Enter a complete email address, such as signal@example.com.</p>
</div>
</div>
<div class="demo__state">
<p class="t-label">Focus visible</p>
<div class="field">
<label class="field__label" for="nz-alias-focus">Alias</label>
<input class="input is-focus" id="nz-alias-focus" name="alias-focus" type="text" value="nightjar" aria-describedby="nz-alias-focus-help">
<p class="field__help" id="nz-alias-focus-help">Tab to a field to inspect its keyboard focus ring.</p>
</div>
</div>
<div class="demo__state">
<p class="t-label">Disabled</p>
<div class="field">
<label class="field__label" for="nz-alias-disabled">Alias</label>
<input class="input" id="nz-alias-disabled" name="alias-disabled" type="text" value="nightjar" disabled aria-describedby="nz-alias-disabled-help">
<p class="field__help" id="nz-alias-disabled-help">Unavailable until an account is selected.</p>
</div>
</div>
<div class="demo__state">
<p class="t-label">Read-only</p>
<div class="field">
<label class="field__label" for="nz-reference">Reference</label>
<input class="input" id="nz-reference" name="reference" type="text" value="DEMO-014" readonly aria-describedby="nz-reference-help">
<p class="field__help" id="nz-reference-help">You can select and copy this reference; it cannot be edited here.</p>
</div>
</div>
</div>
</main>
</body>
</html>
Fill the missing controls
Section titled “Fill the missing controls”Native select and textarea controls cover common needs without inventing a custom dropdown interaction. Each has its own states and usage guidance.
Inspect Select · Inspect Textarea
Empty states: explain the next step
Section titled “Empty states: explain the next step”A blank panel leaves the user guessing. Say what is missing and offer an action that helps.
Native controls work. Demo links and submissions stay inside this specimen. This example scrolls horizontally at this width.
Source markup
<!-- @dsCard group="Feedback" height=700 -->
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Empty state</title>
<style>
.demo { display: grid; gap: var(--space-md); padding: var(--space-sm); }
.demo__states {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(min(100%, calc(var(--space-3xl) * 3)), 1fr));
gap: var(--space-md);
}
/* Static copy of the action's real focus rule. */
.empty-state__actions .btn.is-focus {
outline: var(--focus-width) solid var(--focus-ring);
outline-offset: var(--focus-offset);
box-shadow: var(--shadow-focus-ring);
}
</style>
</head>
<body>
<main class="demo">
<h1 class="t-h3">Empty state</h1>
<p class="field__help">Static examples. These buttons illustrate actions; they do not create records, clear filters or retry a request.</p>
<div class="demo__states">
<section class="empty-state" aria-labelledby="nz-empty-data-title">
<p class="t-label">No data</p>
<h2 class="t-h4" id="nz-empty-data-title">No notes yet</h2>
<p class="empty-state__description">Add a note to start this list.</p>
<div class="empty-state__actions">
<button class="btn btn--primary" type="button">Add a note</button>
</div>
</section>
<section class="empty-state" aria-labelledby="nz-empty-filter-title">
<p class="t-label">No matching results / focus visible</p>
<h2 class="t-h4" id="nz-empty-filter-title">No notes match these filters</h2>
<p class="empty-state__description">Clear the filters to see all notes, or change the search terms.</p>
<div class="empty-state__actions">
<button class="btn btn--ghost is-focus" type="button">Clear filters</button>
</div>
</section>
<section class="empty-state" aria-labelledby="nz-empty-retry-title">
<p class="t-label">Load failure</p>
<h2 class="t-h4" id="nz-empty-retry-title">Notes could not be loaded</h2>
<p class="empty-state__description">Try loading the list again.</p>
<div class="empty-state__actions">
<button class="btn btn--ghost" type="button">Try again</button>
</div>
</section>
<section class="empty-state" aria-labelledby="nz-empty-offline-title">
<p class="t-label">Retry unavailable / disabled</p>
<h2 class="t-h4" id="nz-empty-offline-title">Waiting for a connection</h2>
<p class="empty-state__description" id="nz-empty-offline-help">Reconnect before trying to load the notes again.</p>
<div class="empty-state__actions">
<button class="btn btn--ghost" type="button" disabled aria-describedby="nz-empty-offline-help">Try again</button>
</div>
</section>
</div>
</main>
</body>
</html>
Marks: protect the real artwork
Section titled “Marks: protect the real artwork”The wordmark remains the default. These are comparisons using its actual vector, not replacement logos. The incorrect treatments are shown only to explain the rule.
Original vector. Monochrome, with space around it.
Resize proportionally. Do not compress or widen the mark.
Amber belongs to actions and emphasis. Marks remain monochrome.
Put the phosphor on an amber interface element, never on the mark.
Size and space: approved rules
Section titled “Size and space: approved rules”The full wordmark has an approved digital minimum of 96 CSS pixels. Use the existing compact icon below that width. For standalone placements, option A is approved: at least half the visible letter height kept clear on every side. The study shows both settled rules and a more spacious comparison.
Approved: 96px digital minimum · 0.5H standalone clearance
Same artwork and size in both. The dashed boundary shows the space kept free of other content; it is not part of the logo.
Approved: 96px wide for the full wordmark on screen, with at least 0.5 times its visible letter height kept clear on each side in standalone placements. Use the existing icon below the digital minimum. Print sizes need a proof on the actual material; this screen cannot establish them.
Motion: respond, then stop
Section titled “Motion: respond, then stop”Existing tokens already give the system its timing. Use movement to explain a change after an action; reading a page should not require watching it move.
Compare the existing motion tokens.
duration.fast · 120msduration.base · 240msduration.slow · 480msNothing loops. With reduced motion enabled, the indicator moves immediately.
Imagery: real first
Section titled “Imagery: real first”Prefer real people, places and hardware. Use truthful context and a restrained grade; the subject does not need to be orange to belong to Noiz. AI imagery is an exception: it must meet the highest quality bar and carry a visible “AI-generated image” label, including generated abstract work.
The rest of the system
Section titled “The rest of the system”Element-by-element findings
| Element | Visual judgement | Practical recommendation |
|---|---|---|
| Button and Link | Keep the primary / ghost / text hierarchy. | One primary action per task group. Let focus stay visible even when a control is already amber. |
| Card and Service Card | Keep neutral panels and shared amber emphasis. | Avoid giving every card a glowing edge or making all content look clickable. |
| Glass Panel and CTA Band | The material treatment is distinctive enough. | One focal glow. Use an opaque fallback and test text over the actual backdrop. |
| Hero and Page Header | Keep white headings and monochrome marks. | Prefer a calm composition; let real content determine height and remove decorative motion when it distracts. |
| Icon, Icon Tile and Reticle | Keep the selected vocabulary. | Phosphor for interface meanings, the actual reticle for identity. Never substitute a newly drawn symbol for the logo. |
| Header, Footer and Breadcrumb | Keep consistent navigation and the four-word brand line. | The Header card’s CSS toggle still needs a production interaction implementation that keeps expanded state accurate. |
| Alert, Status Badge and Tag | Keep colour functional and labels explicit. | A status word must survive without colour. Tags categorise; they do not imply live status. |
| Table, Stat and Pricing Row | Keep aligned, readable data and restrained emphasis. | Name units and billing intervals. Preserve table headers and horizontal scrolling on small screens. |
| Accordion and Compare Split | Keep native disclosure and direct comparison. | Use meaningful headings. Do not hide essential errors or instructions inside a collapsed section. |
| Divider and Terminal | Use only where structure or evidence requires them. | A terminal should show useful output. Avoid decorative commands and claims that imply a real check ran. |
What remains open
Section titled “What remains open”- Establish print minimums using physical proofs. The 96px digital minimum and half-height standalone clearance are settled.
- Re-export the legacy dark logo and favicon assets from the current tokens in an explicit asset pass.
- Collect a small, properly credited set of real Noiz photography. This review does not invent photographs or imply stock imagery shows Noiz facilities.
- Test application behaviour in the projects that consume the system. A component specimen is not a working checkout, account or contact service.
The review uses WCAG 2.2 and USWDS component guidance as references. It is not an accessibility certification.