How do I use Card Section Button in my project?

Copy whichever of HTML, CSS and Tailwind matches your setup and paste it in. There is no build step, no dependency and no framework requirement. The three formats produce the same component, so pick the one that fits and ignore the rest.

How do I change the colours?

Edit the colour stops inside the gradient declaration. Keeping the same number of stops preserves the transition, and changing their positions changes where the colours meet.

Can I use Card Section Button commercially?

Yes. The code is free to use in personal and commercial projects, with no attribution required and no licence to accept.

What makes Card Section Button different from a plain button?

It uses transitions, transforms, gradients and shadows, where a default button uses none of them. That is the whole difference: the behaviour is the same and the presentation is not.

Card Section Button

0 viewsmedium

Background:

<button class="card-section-btn">
  <div class="card-icon-section">
    <span class="card-icon">📊</span>
  </div>
  <div class="card-content-section">
    <span class="card-title">New Report</span>
    <span class="card-arrow">→</span>
  </div>
</button>

Was this helpful?

About Card Section Button

Card Section Button is a button built with gradient fills, transforms, layered shadows and CSS filters. Its stylesheet runs to 48 lines across 8 rules, declaring 19 distinct properties. It styles hover state 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, CSS and Tailwind depending on how your project is set up. Nothing is minified and nothing depends on a framework.

When to use

Product pages and dashboards built in the current flat and layered idiom, where a card and section button fits the surrounding design
Repeated use across a page, since there is no animation to become tiring when several appear together
Palettes built around green, white and gray, where this button can be dropped in without retheming
Places where one control is meant to be memorable, since 48 lines of CSS is a real investment for a single element

How it works

The base rule sets the shape with border-radius, display, height and padding. The fill is a gradient rather than a flat colour, so it is a single background declaration with no image to load. 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

Contrast ratio

1:1 (below WCAG AA)

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

Edge

12+

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

Related components

kawaii star button kawaii rainbow button lightning bolt button crystal gem button security shield button trophy achievement button

Frequently asked questions