Don’t Break the Back Button
Description of the problems associated with breaking the back button in rich web UI. Supporting web standards in whole requires that the page work functionally without javascript enabled.
The adoption of Section 508 accessibility guidelines has been a controversial issue at best. depending on the site involved, and those developing and using it.
Breaking the back button means that traditional browsing with forward and backward buttons will be rendered useless.
Too many times I’ve seen sites that have a rich UI experience, but only tested in one or two browsers (usually IE and FF). As a web developer, I often cringe at sites who have not adopted standard-based DOM scripting techniques, or worse yet throw an error page if I am not using one of their supported browsers, as is the case with Konquerer and weightwatchers.com.
I often bring up my favorite sites on my mobile phone as well. The more popular web sites have started to realize the potential of mobile phone usage and accomodated either with standards-compliant markup and scripting, or offering a dedicated WAP 2.0 site.



















