Link
A link is text or media that opens another page, file, or place.
A real example
“View invoice” opens the invoice page. You can also copy its address or open it in a new tab.
Main parts
- 01Current location
- 02Destination labels
- 03Focus order
- 04Responsive behavior
Use it when
Use a link when a destination has a web address or belongs in browser history.
Do not use it when
Never make a harmful action look like a link just to make it less noticeable.
Name used in code
<a href> Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Link to solve this user need without losing the current context. User context: “View invoice” opens the invoice page. You can also copy its address or open it in a new tab. Recommended pattern: Link. Why it fits: Use a link when a destination has a web address or belongs in browser history. Do not use it when: Never make a harmful action look like a link just to make it less noticeable. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Link. Definition: A link is text or media that opens another page, file, or place. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.