This, to me, feels similar to the outdated practice of including all JS in HTML comments for 'older browsers'. Crockford has a good paragraph on this in one of his articles.
"The use of HTML comments in scripts dates further back to a transitional problem between Netscape Navigator and Netscape Navigator 2. The latter introduced the <script> tag. However, users of the former would see the script as text because of the HTML convention that unrecognized markup is ignored. The <!-- comment hack stopped being necessary by the time Netscape Navigator 3 came out. It certainly is not needed now. It is ugly and a waste of space."
People use to turn off JavaScript because the web was new and people were using it improperly. Based on the proliferation of everything JS these days, it feels like we've overcome this barrier, just like we've overcome Netscape 2.
I also feel like the analogy the author makes between 'designing for accessibility' to 'using JavaScript' is improper. I think if the article criticized the usage of Flash, it'd be a different story -- Flash used to be completely inaccessible and it (still) requires someone to download a plugin for it to work. Even so, youtube and the myspace music player (both Flash) are still incredibly popular on the web -- despite that barrier to entry. Something to think about -- maybe prompting to turn on JavaScript solves the problem, just like saying you need to install flash solves the flash problem.
"The use of HTML comments in scripts dates further back to a transitional problem between Netscape Navigator and Netscape Navigator 2. The latter introduced the <script> tag. However, users of the former would see the script as text because of the HTML convention that unrecognized markup is ignored. The <!-- comment hack stopped being necessary by the time Netscape Navigator 3 came out. It certainly is not needed now. It is ugly and a waste of space."
People use to turn off JavaScript because the web was new and people were using it improperly. Based on the proliferation of everything JS these days, it feels like we've overcome this barrier, just like we've overcome Netscape 2.
I also feel like the analogy the author makes between 'designing for accessibility' to 'using JavaScript' is improper. I think if the article criticized the usage of Flash, it'd be a different story -- Flash used to be completely inaccessible and it (still) requires someone to download a plugin for it to work. Even so, youtube and the myspace music player (both Flash) are still incredibly popular on the web -- despite that barrier to entry. Something to think about -- maybe prompting to turn on JavaScript solves the problem, just like saying you need to install flash solves the flash problem.