If the purpose of the website isn't clear than the website standards won't be clear either. Making a web checklist with the right questions applied will help.

This guide checklist should show this list of items:

extensive web standards

in the production phase, as a useful tool

web standard aid

Accessibility standards are important in developing a website. Having a good framework allows projects to naturally fit together. Depending upon the complex modules are the standards and conventions need to be well-defines and easy to understand.



This Jakob Nielson tells of application-design mistakes as follows:



GUI Controls as non-standard includes - appearing like a button but not usable.

Inconsistent Design includes using non-standard GUI controls

Lack of Understanding Actions just by visually looking at the site confusion sets in

Click Targets are too small to use and get lost defeating the purpose

Bad Error Message Feedback

Asking or Repeating Info more than once

Null Default Values

An App Causing User Confusion by placing the customer in the middle of a confusing screen with no instructions

Not Clearly Defining Info Usage - Example: Some sites will ask for personal account information before viewing a site or even a trial version of a product causing you to be charged at the end of the 30 day trial

Centric Features of the System - answering vital questions on a site and mis understanding the question on the app. Example having to answer Yes or No questions and not knowing what the question is asking due to double negatives.

http://www.useit.com/alertbox/application-mistakes.html