Link

From the browser's native link and Base UI's useRender, which adds no behaviour. "From" says who does it. The Default story's play presses every key in this table.

What axe won't catch, from the contract, each with how this component meets it:

• Everything the eye is told, the ear is told, for every shape each prop accepts: the underline tells the eye it is a link and the link role tells the ear; its words are its name; its colour is the text's, so it tells nothing the text doesn't.
• Every landmark and named region has an accessible name: none here; a link is neither.
• Every default label can be overridden: none here; Link owns no strings.
• Every shape the type accepts renders, in every variant: children renders a string, an element and a list alike, in every State, alone or in running text, over one line or several.
• A hidden copy kept for animation is aria-hidden, and a collapsed region is inert: none here; Link keeps no hidden copy and collapses nothing.
• Native semantics first: a native <a href>, never role="button" and never Base UI's Button (CR-1); a render element renders an <a> too.
• Focus moves in reading order and returns on close: the link is one tab stop where it sits in the text, and opens nothing of its own to return from.
• Every target is at least size.target-min square: Link adds no padding or minimum height of its own, so in running text it meets WCAG 2.2's target size (2.5.8) by its inline exception, and standing alone by its spacing exception, the caller giving it size.target-min of room as Accessibility allows. Padding on an inline run would overlap the lines above and below it, and a minimum height doesn't apply to an inline box; a standalone link in typography.body is 21 px tall, under size.target-min (24 px), so the room around it is the caller's, said in Do and don't.
• Loops stop when the system asks for less motion: none here; Link has no loop and no transition.

No owned strings: every word comes from the caller, as children.

Link, like LinkButton, owns no "Opens in a new tab" string, draws no external-link icon and takes no external prop, leaving target and rel to the caller. Content design gives no rule on links or new tabs, so the answer LinkButton's spec gives stands for both: a link that leaves Mylder names its destination in its words ("Rejseplanen"), and Mylder's own links open in the same tab. A caller who opens a new tab passes target="_blank" with rel="noopener noreferrer", and both reach the <a> as they are. An owned string and icon can join later, as a new optional prop, without a break, and LinkButton would take the same.

For a caller using the component, with the reason. Each row is a rule: a must row's Don't is never right, a should row's needs a reason, and Checked by says what catches the Don't in a caller's code.