what's more fair is to use javascript and flash and the like appropriately, but to provide at least some sort of fallback for the users who cannot access it for whatever reason, even if it's only to spit out an error saying "sorry this page requires x, y, z to be enabled".
I do a lot of work for and with visually disabled folks, and it's usually the lack of any sort of fallback that's a problem. Can't tell if something changed, can't read captchas..you get the idea.
The problem with that situation is, of course, that a lot of them are using javascript-enabled modern browsers like ie7 and firefox and safari and usually not a cli browser like links, so they come across these huge webapps like the new yahoo mail that they cannot navigate at ALL very often. It's quite frustrating.
I do a lot of work for and with visually disabled folks, and it's usually the lack of any sort of fallback that's a problem. Can't tell if something changed, can't read captchas..you get the idea.
The problem with that situation is, of course, that a lot of them are using javascript-enabled modern browsers like ie7 and firefox and safari and usually not a cli browser like links, so they come across these huge webapps like the new yahoo mail that they cannot navigate at ALL very often. It's quite frustrating.