Link
Native controls work. Demo links and submissions stay inside this specimen. This example scrolls horizontally at this width.
Source markup
<!-- @dsCard group="Actions" height=120 -->
<!doctype html>
<html lang="en-GB">
<head>
<meta charset="utf-8">
<title>Link</title>
<style>
/* Layout of the demo states only. Colour, type and motion come from bundle.css. */
.demo {
max-width: 960px;
padding: var(--space-2xs);
display: grid;
grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
gap: var(--space-md);
align-items: start;
}
.demo__state { display: grid; gap: var(--space-3xs); align-content: start; }
.demo__grid {
display: grid;
grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
gap: var(--space-2xs) var(--space-sm);
}
/* Copied from bundle.css so both interaction states read without a pointer:
the .link--underline:hover / :focus-visible pair, plus the :focus-visible floor. */
.link--underline.is-hover,
.link--underline.is-focus { color: var(--color-semantic-accent-primary); text-decoration: none; }
.link--underline.is-hover::after,
.link--underline.is-focus::after { transform: scaleX(1); }
.link--underline.is-focus { outline: var(--focus-width) solid var(--focus-ring); outline-offset: var(--focus-offset); }
</style>
</head>
<body>
<div class="demo">
<div class="demo__state">
<p class="t-label">.content-block a</p>
<div class="content-block">
<p>If you want help moving your team to Signal, or a broader review of how your business communicates and where that creates exposure, <a href="#contact">get in touch</a>.</p>
</div>
</div>
<div class="demo__grid">
<div class="demo__state">
<p class="t-label">Base a</p>
<p><a href="#security">Security statement</a></p>
</div>
<div class="demo__state">
<p class="t-label">.link</p>
<p><a class="link" href="#send">Noiz < Send</a></p>
</div>
<div class="demo__state">
<p class="t-label">.link--underline, hover</p>
<p><a class="link--underline is-hover" href="#cybersecurity">Cybersecurity</a></p>
</div>
<div class="demo__state">
<p class="t-label">.link--underline, focus</p>
<p><a class="link--underline is-focus" href="#hosting">Hosting</a></p>
</div>
</div>
</div>
</body>
</html>
Link is the inline text action: amber text carrying a click inside running copy, navigation and card footers. Use it for any call to action that is a sentence, because the site ships two styled buttons only. Use .btn instead when the action is the page’s primary one or sits in a form’s actions row.
What the consumer provides
Section titled “What the consumer provides”An <a> with a real href and a label that reads as language. Prose inside .content-block needs no class: .content-block a:not(.btn) sets color-semantic-accent-primary and underlines it. Outside prose the base a rule already paints the accent, so .link names that result explicitly, and .link--underline is the mono navigation link. There is no pillar tint to apply. Product names keep the Noiz separator, written < in markup: Noiz < Send.
States
Section titled “States”Rest. Outside prose, the base a rule and .link give color-semantic-accent-primary with no underline. Inside .content-block prose the link is always underlined. .link--underline is color-semantic-text-secondary in font-family-mono with its border-width-hairline rule at scaleX(0).
Hover. .link and the base a add an underline. .link--underline moves to color-semantic-accent-primary and grows the hairline to scaleX(1) over duration-base on easing-standard.
Focus. Links take the base :focus-visible outline: focus-width solid focus-ring, offset by focus-offset. .link--underline pairs that outline with its hover appearance. Do not swap in shadow-focus-ring, which belongs to .btn and .input.
Accessibility
Section titled “Accessibility”- Role: a native
<a>with a realhref. No ARIA role is needed;.linkon a<span>or<button>is wrong. - Accessible name: the visible label text. Keep it readable out of context, never “here”; an icon-only link needs
.sr-onlytext. - Keyboard: Tab reaches it and Enter follows it. Space, Escape and the arrow keys do nothing.
- Target size: bundle.css sets no box on
.linkor.link--underline, so inline prose links rely on the SC 2.5.8 inline exception; give a standalone.link--underlinecontainer padding so the hit area clears 24px. - Announcement: none. No link state here is a live region.
Do and do not
Section titled “Do and do not”Do leave prose links underlined, since colour alone is not a link cue. Do keep the :not(.btn) guard on the .content-block rule: without it a CTA button inside prose loses contrast against its own fill. Do not set color-semantic-text-faint on a link label, and do not add text-decoration to .link--underline, whose line is the ::after hairline.
Hand-written from themes/noiz/assets/css/components.css (.link, .link–underline, the base a rule).