usability - Kelly Norton
========================
- goal is great product / happy users
- unachievable without good usability
- great product / happy users = maximizing user experience
- do task analysis up front
- design, implement, test, design, implement, test …
task analysis
- what does a user need to be done?
- need dictates design, not system elegance
- what does the user need to carry this out?
-
- what are the steps involved?
- give users feedback through loading or saving indication
- reduce the chance of errors “undo” — where can errors occur?
- disable double click, use white space
- let the user be in control
- human attention
- 0.1 perceived as instantaneous.
- 1 second - maintains the feeling that a single task is being carried out.
- 10 seconds - limit for keeping the attention of user.
- start fast
- reduce # of http requests
- cache aggressively
- construct ui incrementally
get ui events done in under 100 miliseconds
- do it the web way
users do…
- hit the back and forward buttons
- copy url’s and paste them to emails
- right click on pages to get a context menu
- use visuals effectively
- animation
- some good uses:
- changes not made by user
- reinforcing diret manipulation (drag and drip)
- progress indication
- code red level attention grabbing
- bad uses:
- trying to impress
- consider folks using assistive technology
- use native widgets
- WAI-ARIA
- focus and keyboard support
- test in a screen reader (JAWS)
- update state appropriately
- test now or later
- use professional testers - they pay for themselves
Loading ...