Menu for site navigation.
Site navigation should be disabled during data transactions.
Menu for data navigation.
Data navigation menus and options are presented only when appropriate.
Extensive use of title attributes.
For images, a detailed description of the image.
For controls, a description of what the control accomplishes.
A tip message box, displaying the alternative (or title) attribute.
Proper use of pointing graphic (cursor).
other notes …
Uncluttered, no distractions. Animated GIFs distract the users attention from the content or task. Use only if the GIF supports the application.
Tight control of any page ads. If you give up control, you may get an inappropriate or distracting ad presented to your users.
Avoid the request/response model as it pertains to the user interface. Use only for transactions or application changes.
Window, Document, Portal, Application
Window refers to the window object. Under common circumstances, the “window status bar” is used for messaging the user regarding control objects. However, in some modern interfaces, that status bar is unavailable or “non-viewable”, nor “controllable”.
Document refers to the Document Object Model, upon which all user interface components are presented. Most websites today have the interface built in with the data. Search engine optimization (SEO) programs import the entire page for analysis, thereby including words such as “Enter, Last, Name,” in the word cross-reference for your site, hindering your site from being listed in the top tier.
Portal refers to an “outer” skin within the Document object, that you create. Typically a <DIV> tag, it serves as a base for all applications. Upon loading, it’s CSS is rendered, and all styles within it are then rendered appropriately (fonts, window sizes, etc).
(work in progress)