There seems to be some scenario's where <noscript> succesfully assists in graceful degradation. We all learned why the tag's there and how to use it. As far as I am aware, there are 2 major reasons:
- the
disable JavaScriptoption - screen readers.
On the first one, statistics are hard to get hold of, but it's easy to test for yourself. Also, I've never encountered the need for <noscript> myself to fix some graceful degradation scenario, but that might be just me.
Now, for screenreaders, these stats are a bit easier to get hold of, but I'm mostly interested in actual effectiveness of <noscript>. While it is a widely accepted truth that they "just work", sometimes, an alternative truth can (warning: slight overstatement) rock your world. Like when I got to know that navigation items should not be put into lists.
This thought actually makes me curious as to whether there is any testimonial on the use of <noscript> and whether it is a useful tag in the context that we are always told ("providing alternative content for the visually impaired"). Or maybe there's some implementation paradigm that I'm not aware of that often destroys its effectiveness? Maybe there's even someone visually impaired who might confirm or refute such stories?
note: to attribute some authority to answers, it might help to state that you are visually impaired, if applicable and if you want to of course.