Skip to content

CSS-Only Tabs & Toggles

When to Use

When a client needs tab navigation, toggle panels, or content switchers — without JavaScript tab libraries.

Decision

Client asks for... Use... Why
Tab interface Radio inputs + :checked + sibling selectors CSS-only state management
Toggle panel (show/hide) <details> or checkbox + :checked Built-in toggle
Segmented control Radio inputs styled as buttons Same pattern as tabs
Content switcher (A/B) Checkbox :checked + sibling selectors Binary toggle
Dark mode toggle Checkbox :checked + :has() on html See Modern CSS: :has()

Pattern: CSS-Only Tabs

<div class="tabs">
  <input type="radio" name="tab" id="tab1" checked class="tabs__input">
  <label for="tab1" class="tabs__label">Tab 1</label>
  <input type="radio" name="tab" id="tab2" class="tabs__input">
  <label for="tab2" class="tabs__label">Tab 2</label>
  <input type="radio" name="tab" id="tab3" class="tabs__input">
  <label for="tab3" class="tabs__label">Tab 3</label>

  <div class="tabs__panel" id="panel1">Content 1</div>
  <div class="tabs__panel" id="panel2">Content 2</div>
  <div class="tabs__panel" id="panel3">Content 3</div>
</div>

.tabs__input { position: absolute; opacity: 0; pointer-events: none; }

.tabs__label {
  display: inline-block;
  padding: 0.75rem 1.5rem;
  cursor: pointer;
  border-bottom: 2px solid transparent;
  transition: border-color 0.2s, color 0.2s;
}

.tabs__input:checked + .tabs__label {
  border-bottom-color: var(--color-primary);
  color: var(--color-primary);
}

.tabs__input:focus-visible + .tabs__label {
  outline: 2px solid var(--color-primary);
  outline-offset: 2px;
}

.tabs__panel { display: none; padding: 1.5rem 0; }

/* Show panel when corresponding radio is checked */
#tab1:checked ~ #panel1,
#tab2:checked ~ #panel2,
#tab3:checked ~ #panel3 {
  display: block;
}

/* Animated with @starting-style */
.tabs__panel {
  opacity: 0;
  transition: opacity 0.2s, display 0.2s allow-discrete;
}

#tab1:checked ~ #panel1,
#tab2:checked ~ #panel2,
#tab3:checked ~ #panel3 {
  display: block;
  opacity: 1;
}

@starting-style {
  #tab1:checked ~ #panel1,
  #tab2:checked ~ #panel2,
  #tab3:checked ~ #panel3 {
    opacity: 0;
  }
}

Pattern: Toggle Switch

.toggle {
  position: relative;
  width: 48px;
  height: 28px;
}

.toggle__input {
  position: absolute;
  opacity: 0;
  width: 100%;
  height: 100%;
  cursor: pointer;
}

.toggle__track {
  width: 100%;
  height: 100%;
  background: oklch(80% 0 0);
  border-radius: 14px;
  transition: background 0.2s;
}

.toggle__input:checked + .toggle__track {
  background: var(--color-primary);
}

.toggle__track::after {
  content: '';
  position: absolute;
  top: 2px;
  left: 2px;
  width: 24px;
  height: 24px;
  background: white;
  border-radius: 50%;
  box-shadow: 0 1px 3px oklch(0% 0 0 / 0.2);
  transition: transform 0.2s var(--ease-standard);
}

.toggle__input:checked + .toggle__track::after {
  transform: translateX(20px);
}

Pattern: Dark Mode Toggle with :has()

html:has(#dark-toggle:checked) {
  color-scheme: dark;
  --bg: oklch(15% 0 0);
  --text: oklch(90% 0 0);
}

Accessibility Notes

  • Radio tabs need role="tablist" on container, role="tab" on labels, role="tabpanel" on panels for screen readers
  • Hidden inputs must remain focusable (use opacity: 0, not display: none)
  • focus-visible on labels for keyboard navigation
  • Toggle switches need role="switch" and aria-checked

Common Mistakes

  • Using display: none on radio inputs — breaks keyboard navigation; use opacity: 0 with positioning
  • Missing focus styles — hidden radio inputs need :focus-visible + label styling
  • Not adding ARIA roles — CSS-only tabs need ARIA attributes for accessibility
  • Too many tabs — CSS-only tabs with >5 panels get unwieldy; use JS at that point

See Also