Originally Posted by VIPStephan
How do you know what people expect? I’d say the first thing that people expect is a website that’s not broken in terms of layout and functionality. If I don’t have JS for whatever reason and a site is not working therefore then this is what I don’t expect. I expect that I can sign in to a website, for example. I don’t expect that the page reloads partially only (AJAX) when signing in. I don’t care how the site works as long as it works.
As professional web developer, It's my job to know what web users want, so i do a lot of research on the matter. This includes reviewing analytics, article pursuing, conference attending, and more than my fair share of direct user contact.
Once upon i time, it was my express determination to support every visitor to the sites i built. I even went so far as to integrate a restful text-only (ascii, not css) view for the CMS i built for my last job. The point was for users in developing nations with miniscule bandwidth can read the info we published. Since one of the potential destination sites for the framework was the atlas of world hunger, this was a key consideration. Know your audience, ascii and lynx support is not always needed.
When css first came out, a lot of well-respected "experts" advised to continue working with html3 tables, since not all browser supported CSS at the time. Eventually, developers became confident that 98%+ support was "enough" to remove unskinned views from the design iteration cycle.