Every major email client strips <script> tags before rendering a message — no exceptions, no per-sender opt-out. So when an email carries a working carousel, an accordion that expands, or a scratch-off card that reveals a prize, none of it is JavaScript. It's a hidden checkbox, a CSS selector, and a technique the email-development community calls a state machine. Email built this way is known as kinetic email: interactive HTML and CSS that runs where a client supports it and falls back to a static version where it doesn't.
The problem: email clients strip <script>
Web interactivity almost always assumes JavaScript is available. Email can't make that assumption at all — Gmail, Apple Mail, Outlook, and every other major client removes <script> tags on arrival as a baseline security measure, regardless of what a sender includes or how the message is signed. Anything that behaves like an app inside an email has to be expressible entirely in HTML and CSS, because that's genuinely all that's left standing by the time it renders.
The technique: hidden inputs and sibling combinators
The mechanism is the CSS :checked pseudo-class, applied to real HTML form controls:
- A hidden
<input type="radio">or<input type="checkbox">tracks one piece of state — which carousel slide is active, whether an accordion panel is open, whether a scratch-off card has been scratched. - A visible
<label>wraps whatever the recipient should be able to click — a "Next" arrow, an accordion header, a flashcard — and toggles the input's checked state on click, with zero script involved; that's native<label>/<input>browser behavior. A label can point at its input withfor="..."or contain it; containing it is the safer choice, because Yahoo Mail ignoresforand only toggles an input that sits inside the tapped label. MailInApp's accordion, flashcards, scratch-off and spin-to-win all put the input inside its label for that reason. - A CSS sibling combinator (
:checked ~ .panel,:checked + .content) styles other elements based on that input's checked state — showing a slide, expanding a panel, revealing a "you picked B" message.
Stack enough of these — one input per state, one combinator rule per resulting style change — and the result reads as a genuinely stateful interface, built entirely from markup a client's <script>-stripping pass never touches because there's no script to strip.
Real-world support: a client-by-client breakdown
Per caniemail.com's tested client panel:
| Support level | Clients |
|---|---|
| Full support | Gmail (all platforms, since March 2020), Apple Mail (macOS 12.4+ / iOS 13.3+), Yahoo Mail, ProtonMail |
| Partial support | Outlook.com, New Outlook, and mobile Outlook ("only supported on type selectors"); Samsung Email (Android 7.0+) |
| No support | Classic Windows Outlook (2007–2019); Orange and SFR webmail (strip input elements outright) |
In MailInApp's own tests in real inboxes (October 2026), several of those entries didn't hold up. Every Gmail app (web, iOS and Android) kept the email's <style> block but dropped the :checked rules, so the blocks showed their fallback. Yahoo Mail ran the rules but ignored <label for>, toggling only an input inside its label. Outlook.com and the Outlook apps for iOS and Android dropped them.
Mail on iPhone and iPad, iCloud Mail on the web and Thunderbird ran them. We haven't measured Apple Mail on macOS, new Outlook for Windows or Samsung Email. The full results are in Email client support.
So don't plan on a single reach percentage for this technique. Market share alone can't give one: Litmus counts Apple Mail on iPhone, iPad and Mac as one bucket, and Gmail, the second-largest client, doesn't run it at all. The 2026 State of Email Client Rendering puts the measured support next to market share. What drives a design decision is that a large share of any real list will see the fallback, so the fallback has to be complete.
What happens where :checked isn't honored
In a client that doesn't support :checked at all, the hidden inputs and extra markup simply render inert — no error, no broken layout, just no interaction. The block falls back to whatever its default markup shows, so that default has to hide nothing. In MailInApp, a carousel shows its first slide and a link to the rest, an accordion shows every item expanded, a flashcard shows both sides, and a scratch-off card shows the prize. Designing that fallback deliberately, rather than letting an unsupported client show something half-broken, is the fallback engine's actual job — see How fallbacks work for the full three-tier model this technique sits inside.
How MailInApp uses it
MailInApp's studio writes this markup for you, and pairs every block with a version that reads complete where the technique isn't honored. How fallbacks work shows each block in every tier, and Email client support lists what each app does. For market share and reach, see The 2026 State of Email Client Rendering.