☕

watchOS Toggle

0 viewsmedium
Background:
watchOS Toggle
1
2
3
4
5
6
7
<div class="watchos-container">
  <input type="checkbox" id="watchos-toggle" class="watchos-input" />
  <label for="watchos-toggle" class="watchos-label">
    <span class="watchos-thumb"></span>
  </label>
  <span class="watchos-text">Apple Watch</span>
</div>
Was this helpful?

What is inside watchOS Toggle

watchOS Toggle is a CSS toggle switch built with gradient fills, transforms, layered shadows, defined in 42 lines across 7 selectors.

21
CSS properties
7
Selectors
42
Lines of CSS
3
Formats

Techniques used

TransitionsTransformsGradientsShadowsChecked stateFlexbox

CSS properties in this component

align-itemsbackgroundbackground-colorborderborder-colorborder-radiusbox-shadowcolorcursordisplayfont-familyfont-sizefont-weightgapheightleftpositiontoptransformtransitionwidth

Accessibility check1 to fix

  • Built on a native <input> 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 watchOS Toggle

watchOS Toggle is a toggle switch built with gradient fills, transforms and layered shadows. Its stylesheet runs to 42 lines across 7 rules, declaring 21 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. 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
17:1 (passes WCAG AA)
ARIA
Native element semantics, no extra attributes needed

Built on a native <input> 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