☕

Rainbow Glow

0 viewshard
Background:
Rainbow Glow
1
2
3
4
5
<label class="container1">
  <input type="checkbox" />
  <div class="checkmark1"></div>
  <span class="label1">Rainbow Glow</span>
</label>
Was this helpful?

What is inside Rainbow Glow

Rainbow Glow is a CSS checkbox built with transforms, layered shadows, defined in 61 lines across 9 selectors.

24
CSS properties
9
Selectors
61
Lines of CSS
3
Formats

Techniques used

TransitionsTransformsShadowsChecked stateFlexboxCustom properties

CSS properties in this component

align-itemsbackgroundborderborder-radiusborder-widthbox-shadowcolorcontentcursordisplayfont-familyfont-sizefont-weightgapheightinputleftopacitypositiontoptransformtransitionuser-selectwidth

Accessibility check1 to fix

  • Built on a native <label> 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, Tailwind and adapt it freely.

About Rainbow Glow

Rainbow Glow is a checkbox built with transforms and layered shadows. Its stylesheet runs to 61 lines across 9 rules, declaring 24 distinct properties. It styles checked 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

How it works

The base rule sets the shape with border-radius, display, height and position. 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. Colours are held in custom properties, so retheming means editing the variables at the top rather than hunting through the rules.

Accessibility

Keyboard navigation
Supported
Screen reader
Friendly
Contrast ratio
2:1 (below WCAG AA)
ARIA
Native element semantics, no extra attributes needed

Built on a native <label> 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
49+
Firefox
31+
Safari
10+
Edge
16+

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

Frequently asked questions