Icon Minimal Button

0 viewseasy
Background:
1
2
3
4
5
<button class="icon-minimal-btn">
  <svg class="icon" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
    <path d="M19 14c1.49-1.46 3-3.21 3-5.5A5.5 5.5 0 0 0 16.5 3c-1.76 0-3 .5-4.5 2-1.5-1.5-2.74-2-4.5-2A5.5 5.5 0 0 0 2 8.5c0 2.29 1.51 4.04 3 5.5l7 7Z"/>
  </svg>
</button>
Was this helpful?

What is inside Icon Minimal Button

Icon Minimal Button is a CSS button built with transforms, defined in 28 lines across 5 selectors.

13
CSS properties
5
Selectors
28
Lines of CSS
2
Formats

Techniques used

TransitionsTransformsHover stateActive stateFlexbox

CSS properties in this component

align-itemsbackgroundborderborder-colorborder-radiuscolorcursordisplayheightjustify-contenttransformtransitionwidth

Accessibility check1 to fix

  • Built on a native <button> element, so keyboard focus and screen reader semantics work without extra attributes.
  • No focus style is defined. Add one before shipping, or keyboard users lose track of position.

These notes are generated by reading this component's own source, so they describe what it actually does rather than what a template says. Copy the code above in HTML, CSS and adapt it freely.

About Icon Minimal Button

Icon Minimal Button is a button built with transforms. Its stylesheet runs to 28 lines across 5 rules, declaring 13 distinct properties. It styles hover and active states explicitly, so the component responds to interaction rather than sitting still. Every format shown on this page is the same component, so you can take HTML and CSS depending on how your project is set up. Nothing is minified and nothing depends on a framework.

When to use

How it works

The base rule sets the shape with border-radius, display, height and width. Movement is done with transforms rather than by changing position or size, which is what keeps it smooth: transforms are composited and do not force the browser to lay the page out again. State changes are eased with a transition, so hovering does not snap.

Accessibility

Keyboard navigation
Supported
Screen reader
Friendly
ARIA
Native element semantics, no extra attributes needed

Built on a native <button> element, so keyboard focus and screen reader semantics work without extra attributes. No focus style is defined. Add one before shipping, or keyboard users lose track of position. That is one thing to fix before this ships in front of users.

Browser support

Chrome
26+
Firefox
16+
Safari
9+
Edge
12+

Everything this component uses has been supported across browsers for years, so no fallback is needed.

Frequently asked questions