These guidelines give some basic usability options to follow when developing applications.
It is important for the user to be able to see what is happening within the application/system. The user should be informed, and it is good to let the user feel in control and be forgiven for any mistakes or slips he/she might have committed.
As an example one can use message boxes to convey these system statuses.
When filling in a form and there is an error in one of the text field, provide the necessary details in a message box underneath the text field.
Within an application try to keep consistency in terms of language used, layout and colours. If there is a convention for something and most of the applications work in a particular way, do not try and re-invent the wheel by creating something completely different.
In the EUAA applications consistency is being kept by using custom made components that follow the visual style guide.
If possible try to use the components that are in the list but if a new component is needed try to style it based on the visual style guide.An interface presented to the user should always be simple and easy to use. This means to just have the essential items needed to support the user's primary goal and other secondary elements should have less prominence.
In the EUAA applications when a user wants to create an account he/she will be directed to this page.
As can be seen from this page, the primary goal of the user is to "Create an account" which is placed strategically in the middle of the page. There are other secondary actions that can be done and these are the "login" and "forgot password", but these are given less prominence.These are based on the 10 Usability Heuristics for User Interface Design