blind user | is a subtopic of 7.5 - Usability Principles | ![2001-08-30 14:54:40.0](facet.gif) |
is a kind of user with a disability | ![2001-08-30 14:54:40.0](facet.gif) |
needs a program that converts text to Braille or speech | ![2001-08-30 14:54:40.0](facet.gif) |
user | can learn an application quickly if it is similar to an application they already know | ![2001-08-30 14:58:15.0](facet.gif) |
can notice a single small spot of red or orange on an entire screen | ![2001-08-30 14:58:15.0](facet.gif) |
does not fear bad consequences of what he does if he can undo any action | ![2001-08-30 14:58:15.0](facet.gif) |
does not feel that the computer is in control of her time if response time is adequate | ![2001-08-30 14:58:15.0](facet.gif) |
feels that he or she has enough information to make decisions if the system informs her of what it is doing, has done and is about to do | ![2001-08-30 14:58:15.0](facet.gif) |
has a perception of acceptable response time based on the other applications she uses | ![2001-08-30 14:58:15.0](facet.gif) |
has characteristics that vary from one user to another including: - goals for using the system, depending on job function or roles
- potential patterns of use such as how often the system is used
- demographics such as age
- knowledge of the domain and of computers
- physical ability
- psychological traits and emotional feelings
| ![2001-08-30 14:58:15.0](facet.gif) |
has goal doing enjoyable or interesting work, and gaining recognition for the work they have done | ![2001-08-30 14:58:15.0](facet.gif) |
is concerned with efficiency | ![2001-08-30 14:58:15.0](facet.gif) |
is concerned with reliability | ![2001-08-30 14:58:15.0](facet.gif) |
likes software that is easy to learn and use, makes their life easier, helps them achieve more, or allows them to have fun | ![2001-08-30 14:58:15.0](facet.gif) |
makes mistakes | ![2001-08-30 14:58:15.0](facet.gif) |
may be affected by information overload | ![2001-08-30 14:58:15.0](facet.gif) |
may be frustrated when they seek help | ![2001-08-30 14:58:15.0](facet.gif) |
may fear that new software could jeopardize their job | ![2001-08-30 14:58:15.0](facet.gif) |
may judge utility^2 and usability differently from another user depending on her level of computer experience and the tasks she is performing | ![2001-08-30 14:58:15.0](facet.gif) |
may work for customer | ![2001-08-30 14:58:15.0](facet.gif) |
must be involved in the development of software | ![2001-08-30 14:58:15.0](facet.gif) |
must like a system or they will not use it, even if it has high learnability and efficiency of use | ![2001-08-30 14:58:15.0](facet.gif) |
often welcomes new or improved software | ![2001-08-30 14:58:15.0](facet.gif) |
should be able to understand everything that appears on the screen | ![2001-08-30 14:58:15.0](facet.gif) |
should be involved in all decision-making that relates to the requirements and to the user interface design and to a limited extent in requirements analysis | ![2001-08-30 14:58:15.0](facet.gif) |
should be involved in requirements analysis, user interface design and deployment, and also may play a role in design, quality assurance and project management | ![2001-08-30 14:58:15.0](facet.gif) |
should be made to feel involved in the software engineering process resulting in fewer mistakes being made and greater acceptance of the finished product | ![2001-08-30 14:58:15.0](facet.gif) |
should feel in control of the computer, not the other way around | ![2001-08-30 14:58:15.0](facet.gif) |
should give feedback on prototypes, on-line help and draft user manuals | ![2001-08-30 14:58:15.0](facet.gif) |
should not be expected to participate in detailed low-level internal design decisions | ![2001-08-30 14:58:15.0](facet.gif) |
wants software that is easy to learn | ![2001-08-30 14:58:15.0](facet.gif) |
wants software that is easy to learn, efficient to use, and which helps get work done | ![2001-08-30 14:58:15.0](facet.gif) |
stakeholder | must agree on requirements | ![2001-08-30 14:57:46.0](facet.gif) |