Please enable JavaScript.

Coggle requires JavaScript to display documents.

LEC6 - Coggle Diagram

- - - - make text readable +understandable
        
        simple terms and simple language on UI
      - make content appear and operate in a predictable logical way
      - help users avoid and correct mistakes
      - give more time- for people with cognitive difficulties
    - - maximise compatibility with currrent and future user tools
      - interpreted by any agents like screen readers
    - - make all functionality available for a keyboard
      - giver users enough time to read and use content
      - avoid content that causes seizures or physical reactions
      - make it easier for users to use
        
        UI elements must be able to operate the interface
        
        navigation should not discriminate(tabbing feature)
        
        need to multimodal
        
        short cuts enabled
    - - provide captions and other alternatives for multimedia
      - create content that can be presented diff waysl assistive tech without loosing meaning
      - Provide text alternatives for non-text content
        
        Alternative text must be specific and meaningful.
      - make it easier for users to see and hear content
        
        use of colour to increase perceivability
        
        re-sizable
        
        hi contrast
- - - - standardise the way info is conveyed
      - familiar with digital landscape- internal consistency
      - break only if necessary
      - SAME as "Consistency and Standards"- 10H
      - utilize familiar icons, colors, menu hierarchy, call-to-actions, and user flows when designing similar situations and sequence of actions
    - - Users with all sorts of differences
        
        disabilities, language, age, cognitive capacities, different devices, internet connections, arthritis) should be able to use the product
        
        Cater to both newbies and expert users
        
        enable shortcuts to frequent users
      - Similar idea to "Flexibility and Efficiency of use" from 10H
    - - for every action there should be appropriate and human readable feedback
      - users should know what is going on
    - - confirmation message.. "Thank you"..
        
        satisfied and sure that the transaction was successful
      - Similar to "Visibility of system status" from 10H
      - better to divide action into a sequence
    - - design should be as fool-proof as possible
        
        clear labelling/ formatting + much options so users don't make errors
      - help users avoid errors and offers good and understandable suggestions.
      - Try your best to ensure that users don't make errors
    - - allow users to go back if they'd like to or if they have made a mistake
      - If someone have made an error they should be able to reverse it
      - user friendly.. friendly error messages
    - - allow users to be initiators of actions.
      - earn trust
      - similar to "User control and Freedom"-10H
      - sometimes system should make a decision for user's benefit.
        
        but should never interfere
    - - interfaces should be as simple as possible
      - recognition over recall- 10H
        
        recog-perceives cues
        
        eg. system should keep track of number of items bought