> yet users who want or need to disable JS are often left out in the cold.
Isn't that just a preference of the user, that has repercussions? In fact the WCAG 2.0 specifically says that a JS fallback is _not_ a requirement for accessibility - a common misconception is that disabled users disable JavaScript - this isn't actually true.
Fair enough if you want to turn off JS for tracking reasons or whatever, but you have to accept that some things might not work without it.
Isn't that just a preference of the user, that has repercussions? In fact the WCAG 2.0 specifically says that a JS fallback is _not_ a requirement for accessibility - a common misconception is that disabled users disable JavaScript - this isn't actually true.
Fair enough if you want to turn off JS for tracking reasons or whatever, but you have to accept that some things might not work without it.