A rectangle with rounded corners can be either a link or a button. Its colour and shape do not settle the question. The more useful distinction is what happens when someone activates it: navigation to a resource, or an action in the interface.
The W3C’s button pattern describes actions such as submitting a form or opening a dialog and distinguishes them from links. Matching the control’s role to its behaviour helps people using keyboards and assistive technology understand it.
Choose the native element first
For navigation to another page, an anchor with a meaningful href is usually the starting point. For an action such as opening a menu or saving a form, use an appropriate button. Native elements provide established behaviour that a styled generic element does not acquire automatically.
A clickable div still needs keyboard support, focus handling and an accessible role. Adding an ARIA label alone does not supply those behaviours. Avoid rebuilding a standard control unless the design genuinely requires it and the implementation is tested.
Within a form, specify a button’s type when needed so that a secondary action does not accidentally submit the form. A control labelled “Preview” should not unexpectedly behave like “Send.”
Review behaviour without a mouse
Move through the interface with the keyboard, check that focus is visible and activate controls using their expected keys. Confirm that the accessible name explains the action or destination. After a dialog opens or closes, verify that focus moves to a sensible place.
A useful review note records the control’s label, element, expected result and observed result. This makes a problem such as “looks like navigation but silently deletes an item” concrete enough to fix.
Visual design can still be expressive. A link may look prominent and a button may look understated, but their semantics should remain honest about their function. That consistency gives users fewer surprises and developers a clearer basis for testing.

