Changes between Version 20 and Version 21 of DeveloperGuidelines/Usability


Ignore:
Timestamp:
08/12/11 07:22:52 (10 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Usability

    v20 v21  
    3333 * Should pages start as "Read" and have a button to edit (ideally without a JS call) or is it OK to default straight to the update form?
    3434
     35== Usability Feedback ==
     36Some feedback from IBM's UX team:
     371. Selected tabs can have a changed color {other than non selected} to indicate which part of website we are in.
     382.  "More" Tab  has too many links, If possible, few section from "More" tab should be clubbed together.
     393. The hover (drop-down menu) appears only in the "More" part of the top menu. So perhaps it may be good to put that in another font or, if possible, put a arrow besides "More"
     404. Most pages usually have "News" in the top section of the main page.
     415. The twitter items can actually be just shown through a twitter icon such as the one in http://www.rolandgarros.com/en_FR/index.html at the bottom. (just a suggestion).
     426. A neat footer can be given in all pages, so as to enable direct link to section. Since this is a current trend - it will be making the visual composition more balanced as well as usable. An example of a footer is at the bottom of: http://www.ibm.com/us/en/
     43
    3544----
    3645DeveloperGuidelines[[BR]]
    3746
    3847Projects/Advanced/Usability
    39 Projects/Advanced/Usability