I'm curious about how web developers approach site design considering that some users might have a "Disable JavaScript" plugin. Is this something that developers worry about? How do they go about accommodating those users, if at all? Or do most just assume that users who disable JavaScript understand that parts of the site might not work properly? I'd like to hear different perspectives on this!
5 Answers
Most places I've worked have kind of overlooked this. The percentage of users disabling JavaScript is super small. Occasionally, we’ll add a noscript message, but that's about it.
In my case, if users don’t run scripts, they just get a very basic interface. I focus more on ensuring that my mobile view looks good since most of our traffic is from mobile devices. Those who disable JS simply get a stripped-down version.
Honestly, I mostly use the `` tag to inform users that the site requires JavaScript to function properly. It’s a simple way to address the issue without going overboard.
It seems like the majority of developers simply don’t consider it, since most users have JavaScript enabled. If someone disables it, it’s more on them if the site doesn’t work.
Exactly! If someone doesn't have JS on the types of sites I build, it's likely they don’t need the site anyway.
Right, it's really not our problem at the end of the day.
If a site doesn't need JavaScript, I build it to work with just HTML and CSS. That way, even users with JS disabled have a functional experience. But if it’s a web app that relies on JS, then I’ll just inform users that it won’t work without it.
That’s a smart approach! Plus, with modern CSS, you can accomplish a lot without needing JavaScript.
I usually ensure everything works well across major browsers, but I don’t have the time to handle every edge case.