I haven't implemented a client-side setting on my sites yet, but it's in the plans. I can tell you why I plan to do it, and also why I test with no-JS support a

I haven't implemented a client-side setting on my sites yet, but it's in the plans. I can tell you why I plan to do it, and also why I test with no-JS support and in text-mode browsers, implement status indicators and back-to-top buttons, and why I consider Netscape 2.0 a first-class citizen on my domains. Sure, the user-agent "should" provide all of that stuff, but the reality is that most don't have all the features I would want as a visitor to my site, so I have to bend over backwards to accommodate their specific abilities. The user-experience is a combination of three abilities: the ability of the user, the ability of the user-agent, and the ability of the Web site. Combined together they form the ACCESS-ABILITY landscape.