There's a lot of selection bias in collecting statistics with a package that'll only execute properly in the latest browsers and those running JS (as opposed to looking at webserver logs directly). I'll grant that vox probably only cares about serving content to people that can also see it's ads so it's a legitimate cut corner in this context. Their demographic is accessible eyes on ads and wallets, not people.
If you want to serve content to human people and not just to eyes or wallets then at least be aware that most modern browser share statistics collected with JS don't reflect the reality you'd see in your webserver logs.
I'd be very shocked if the percentage of all human users that have JS disabled is more than <0.1%. Even web crawlers and other bots can (and do) execute JS these days.
I don't think the demographic is realistically relevant.
Some crawlers execute JS, but last I heard or checked even Bing’s crawler seldom did, and Google’s clearly tried to avoid doing so.
Of humans that deliberately disable JS, certainly going to be under 0.1%. (I’m one of them, incidentally, because on average it makes the web much better, lighter and faster.)
Of humans where various JS doesn’t run, due to having an older browser, a corporate proxy that blocks some things, a content blocker like uBlock Origin that incidentally blats your script, unreliable network conditions, and more things… well, that number is regularly quite a lot higher than 0.1%, often above 1%.
As for something like the Statcounter tracker, which these specific stats are built from, their methodology is obviously stupidly broken and has been for many years: ad blockers will tend to block it. (uBlock Origin does by default, and I expect others to as well.) And that number is generally agreed to be well above 10% (some say as high as 40%, though I’m sceptical of that), and heavily overrepresents users of less common browsers like Firefox.
If you want to serve content to human people and not just to eyes or wallets then at least be aware that most modern browser share statistics collected with JS don't reflect the reality you'd see in your webserver logs.