링크는 장소로, 버튼은 동작으로

Here is the rule that solves almost every case: a link takes you somewhere, and a button makes something happen right here. 🧭

A link navigates. Clicking it changes the page or URL, like jumping to another article or a new section.

A button performs an action in place: it submits a form, opens a menu, or toggles a setting without leaving the page.

Screen readers announce the role out loud. Users hear link or button, so the right element sets the right expectation before they act.

This is not just cosmetic. A button fires on Space or Enter, but a link activates only on Enter. The keys follow the role.

Ask one question: does this control change where I am, or change what is on screen? Navigation means link; action means button.

If a control could sensibly open in a new tab or be bookmarked, it is navigation, so use a real link with an href.

Styling does not change meaning. A button can look like a link and a link can look like a button, but the element decides the role.

People reach for a styled div or span and bolt on a click handler. It looks fine but has no role and no keyboard support.

To send a form, use a button of type submit. It is an action, not navigation, so a link here would be wrong.

To send a user to your contact page, use a link. That is pure navigation, and a button would mislead everyone.

You add a control that opens a menu without leaving the page. Which element fits?

Links go places, buttons do things. Match the element to the intent and you get the right role, the right keys, and happy users. 🎉