another tip: consider adding a splash page/landing page to your website to let people know about any content warnings as well as if they need to have javascript enabled to use any accessibility features ^^
Delete
Are you sure you want to remove this comment from the news feed?
many people (such as myself) often have JavaScript disabled by default, so it's nice to know if I'm gonna need to turn it on to be able to pause gifs/change layout/etc.
curious, what's the reason for disabling js by default? im pretty pro-js (probs also bc i make browser games and js is often a backbone for that) and i dont really understand the aversion
as a pro-JS person, i think the main issue is with privacy and security, since JS can is also used for tracking visitors if a webmaster has analytics enabled; CDNs also collect user data from the sites they're installed on. and if the CDN is ever compromised, that also poses a risk to every site running those scripts.
of course, this can be mitigated by setting the appropriate security headers and hashes, but this isn't common knowledge for a lot of people, let alone novice web devs.
pretty much what Jasmine said! I often forget to turn JS on for individual sites so it's a nice reminder, and I'm sure I'm not the only one. I'm okay turning it on as long as I feel the site is safe or it has features that require JavaScript to function
of course I would say people with things like photosensitivity may feel like they can't afford to turn off JavaScript because of things like that, but I think it's just a nice to have just in case you know :^)
I've been considering implementing a splash page, even though I don't love them personally. This is a good argument for doing so since I use JS for major features that I don't know how to code without it. Thanks for the tip!
many people (such as myself) often have JavaScript disabled by default, so it's nice to know if I'm gonna need to turn it on to be able to pause gifs/change layout/etc.
curious, what's the reason for disabling js by default? im pretty pro-js (probs also bc i make browser games and js is often a backbone for that) and i dont really understand the aversion
as a pro-JS person, i think the main issue is with privacy and security, since JS can is also used for tracking visitors if a webmaster has analytics enabled; CDNs also collect user data from the sites they're installed on. and if the CDN is ever compromised, that also poses a risk to every site running those scripts.
of course, this can be mitigated by setting the appropriate security headers and hashes, but this isn't common knowledge for a lot of people, let alone novice web devs.
pretty much what Jasmine said! I often forget to turn JS on for individual sites so it's a nice reminder, and I'm sure I'm not the only one. I'm okay turning it on as long as I feel the site is safe or it has features that require JavaScript to function
of course I would say people with things like photosensitivity may feel like they can't afford to turn off JavaScript because of things like that, but I think it's just a nice to have just in case you know :^)
The noscript tag can let you inform users if JavaScript is required on a page
I've been considering implementing a splash page, even though I don't love them personally. This is a good argument for doing so since I use JS for major features that I don't know how to code without it. Thanks for the tip!