FRENVersion française

Conversion & pricing

Billing toggle

Bascule mensuel / annuel

Demo

Loading demo…

The period picker at the top of a pricing page: Monthly or Annual. Despite the name, it is rarely an on/off switch: it is a two-option segmented control, often with a savings badge ("−20%"). Changing it updates every price on the page.

Story

Did you know

Tickets often ask for "the annual switch". The result: on/off toggles where nobody knows whether "off" means monthly. And "2 months free" sometimes gets labeled "−20%", although 2 months out of 12 is 16.7%.

Timeline

  1. 2003Mac OS X 10.3 introduces NSSegmentedControl, the native segmented control.
  2. 2008The iPhone SDK ships UISegmentedControl: the pattern spreads to mobile.
  3. 2010sAs subscription SaaS becomes the norm, the monthly / annual toggle becomes a pricing page staple.
  4. 2023WCAG 2.2 adds criterion 2.5.8: targets of at least 24 × 24 px.

Vocabulary

Names

FR
Bascule mensuel / annuel, sélecteur de période de facturation, bascule de facturation
EN
Billing toggle, monthly/annual switch, billing period toggle, billing cycle selector, pricing toggle

Common uses

  • SaaS pricing page with several plans side by side
  • In-app upgrade screen
  • Checkout page, to switch period before paying
  • Subscription settings (switch to annual)

Often paired with

The components it usually sits with, by page type, in reading order.

Code

<!-- Style the labels as a segmented control: label:has(:checked) { ... } -->
<fieldset class="billing">
  <legend>Billing period</legend>
  <label><input type="radio" name="billing" value="monthly"> Monthly</label>
  <label>
    <input type="radio" name="billing" value="annual" checked> Annual
    <span class="badge">-20%</span>
  </label>
</fieldset>
<p aria-live="polite" aria-atomic="true">
  <strong id="price">$10</strong> / month · <span id="note">billed $120 yearly</span>
</p>

<script>
  const plans = {
    monthly: { price: '$12.50', note: 'billed monthly' },
    annual: { price: '$10', note: 'billed $120 yearly' },
  }
  // Radios give arrow keys and a single tab stop for free
  document.querySelector('.billing').addEventListener('change', (e) => {
    const plan = plans[e.target.value]
    document.getElementById('price').textContent = plan.price
    document.getElementById('note').textContent = plan.note
  })
</script>

Good to know

  • It is not a switch: it is a choice between two values. Two input type="radio" styled as a segmented control give the right role, arrow keys and a single tab stop with no JS.
  • Show the monthly equivalent and the amount actually charged ("$10/mo, billed $120 yearly"). Showing only "$10/mo" hides what the card will be charged: that is a dark pattern.
  • Pick the default on purpose. Many pricing pages preselect annual to anchor the lower price; if you do, say so clearly next to the price.
  • The badge must be honest: "2 months free" is 16.7%, not 20%. Compute the percentage from the real prices.
  • Keep the choice in the URL (?billing=annual) with history.replaceState: shared links and the back button keep the period.
  • Keep the card the same height in both states (reserve the "billed …" line) to avoid layout shifts.

Accessibility

Must have

  • A named group: <fieldset> + <legend> ("Billing period"), or role="radiogroup" + aria-label.
  • Announce the new price: aria-live="polite" and aria-atomic="true" on the price or the summary, otherwise the change is silent for screen readers.
  • The active option must not rely on color alone: solid fill, weight, check mark. It needs 3:1 contrast against the background (WCAG 1.4.11).

Often forgotten

  • Put the savings badge inside the <label>: it is then read with the option ("Annual −20%") instead of floating on its own.
  • Avoid a real on/off switch: "Annual, on" does not say what "off" means. If you keep a switch, label both sides visibly.
  • Don't hide the radios with display: none: they would no longer be focusable. Make them invisible but present (opacity 0, absolute position).

Nice to have

  • Targets of at least 24 × 24 px (WCAG 2.5.8), ideally 44 px on mobile.
  • A visible focus ring on the whole option (label:has(:focus-visible)).

Who uses it