I turned JavaScript off, opened a demo built to work without it, and went looking for the one thing that broke.
I found it in the sidebar. The user's email address reads "[email protected]". The copy of the same page in its GitHub repo says alex@example.com. Cloudflare rewrote the address on its way out and added the page's only <script> tag to decode it again.
Everything else on the page worked. The demo is the example page for Alloy CSS, a stylesheet that hit 181 points on Show HN yesterday with a simple pitch: dialogs, menus and tabs that keep working with scripts off. The author, Fandy Pradana, ended his post with "Tell me where it breaks." So I did what he asked, and I think the answer draws a line every server-rendered app can use.
What I clicked, with scripts off
The example is one screen of a made-up invoicing app: a sidebar, a table of invoices, a "New invoice" modal, five popover menus and drawers, tabs over four lists, a bulk action bar and a toast. I drove it with headless Chromium 151 through Playwright, JavaScript disabled for the whole session, and logged what each click did:
script requests with JS off: 0 dialog open after click: true page scroll locked: hidden dialog open after Esc: false range menu open: true row ticked: true bulk bar visible after tick: true toast open: true toast open after its close button: false panels visible after Overdue: [false,true,false,false] Zero script requests, so Cloudflare's decoder never loaded either. That's why the email stayed scrambled.
None of this is a trick. The browser does the work, and the stylesheet styles it. A button opens a real <dialog> with two attributes:
<button type="button" commandfor="confirm" command="show-modal">Delete</button> <dialog id="confirm" closedby="any" class="dialog">...</dialog> The menus are popover elements placed under their button with CSS anchor positioning (position-area). The page stops scrolling behind the modal because of one rule, html:has(dialog:modal). The bulk bar appears because its wrapper matches :has(input:checked) once you tick a row. The open animations come from @starting-style. The whole kit is 164,694 bytes minified, about 23.5 KB gzipped by my measure, close to the 24 KB the README quotes.
The line is who owns the state
Here's the part I think matters beyond this one library.
Look at what each working part rests on. A dialog's open. A popover's :popover-open. A checkbox's :checked. That's state the browser owns. It changes the state when you click, and it tells the accessibility tree about it, because those are native elements with native meaning. CSS only reads the state and paints.
When HTML has no element for the job, CSS can still paint the right picture. What it can't do is change what the page means. Meaning lives in roles and ARIA attributes, and a stylesheet can't write an attribute.
So the rule I'd take from Alloy is this: if the browser owns the state, you don't need JavaScript anymore. If only ARIA can describe the state, you still do.
Dialogs, menus, drawers and disclosures fall on the first side now. Tabs fall on the second.
What a screen reader gets
Alloy's tabs are labels wrapped around radio buttons that share a name. Twelve generated :has() rules show the panel at the same position as the checked radio, so a tab bar tops out at 12 tabs. It works with a mouse, and the arrow keys move between radios. Here's the accessibility tree Chromium built for the tab row after I clicked "Overdue":
- radio "All 24" - radio "Review them Overdue 3" [checked] - radio "Paid 10" - radio "Drafts 2" Radios, not tabs. The author raised that one himself in the HN thread as the weak spot he knows about. The name on the second radio is one I haven't seen anyone mention. The "Review them" button in the overdue alert above the table isn't a button. It's a <label for="tab-overdue"> styled to look like one, since a label can check a radio from elsewhere on the page with no script. So the button reads as plain text, and its words get glued onto the tab's name.
The bulk bar has a related gap. In the thread, lopis pointed out that a screen reader user never learns the "Selected invoices" bar appeared. I checked: the bar carries no role and no aria-live.
A real tab pattern needs role="tab" and aria-selected flipping as you move. Nothing in CSS can flip it. That's why tabs still need a script, however clever the stylesheet gets. Keithamus, who works on Open UI, noted in the thread that popover itself came out of that group. The fix for tabs looks the same: another native element, not a better hack.
Where else it gets shaky
Your browser floor is higher than the README's headline. It lists Chrome 123, Firefox 125 and Safari 17.5 for the interactive parts, then says dialogs need commandfor, which means Chrome 135, Firefox 144 and Safari 26.2. On older browsers the button that opens a dialog does nothing. The menus lean on position-area, which MDN's compatibility data puts at Chrome 129, Firefox 147 and Safari 26. I didn't test where a menu lands in a browser without it.
The checker checks names, not wiring. Alloy's pitch for AI is a fixed class scale, an llms.txt file, a Claude skill and alloy-check, which lists every class the kit doesn't define. I wrote a test page using only kit classes, by my own tally against alloy.css, with two wiring mistakes: a menu button with popovertarget="sort-menu" pointing at id="sort", and a <div class="dialog"> where a <dialog> belongs. With scripts off, the menu never opened, and the fake dialog sat in plain view from the start. By its source, the checker only scans class attributes, so it would pass that page. I read it; I didn't run it. An AI that writes valid classes on broken markup gets a pass.
The public tests cover the checker, not the CSS. The repo's test folder holds one file with six tests, all for alloy-check. Nothing in the public repo tests that a dialog opens or a panel shows.
And the class names are plain (.button, .dialog, .flex, .hidden), so dropping it into an app with its own CSS will collide, which the README admits and the author confirmed in the thread. It's built for new projects.
Try it
Open the example, then turn scripts off: in Chrome DevTools, press Cmd+Shift+P (Ctrl+Shift+P on Windows), type "Disable JavaScript" and reload. Click everything. Then open the accessibility pane on the tab row and see what it calls them.
To use it, link one file:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@alloyhtml/css@1/dist/alloy.min.css"> If your app is server-rendered (Rails, Django, Laravel, htmx), the native parts are worth taking as they are. Spend your script, or at least your screen reader testing, where the browser has no element yet: tabs, and anything that should be heard when it appears.
If browsers shipped one more native element next year, which one would delete the most JavaScript from your app?
