Set of Heuristics Llcia More

SET OF HEURISTICS LLCIA
WEB
Heuristics for the evaluator & designer

1. ISO ATTRIBUTE
Quality in use model
Effectiveness
Consistency
Do the same elements appear with the same form or format in the whole interactive system?
Are the same elements grouped and located in the same place?
Are persistent and volatile elements distinguished?
Are new functionalities distiguished from old functionalities to avoid confusions between them?
If any kind of inconsistency appeared, is the user warned?
Are the same concepts called equal in whole interactive system?
Are the same colours in the whole interactive system?
If a consistent interactive system is not possible in its domain, is it possible in an upper domain?
Is user warned about the continued use of uppercase letters?
Is the active window correctly displayed?
Do all windows and pages have a title?
Is vertical and horizontal scroll possible in all windows?
Does the menu structure reflect the tasks structure?
Are the sounds identical for the same actions?
Is the movement of the cursor consistent in the whole interactive system?
Are the steps of the interactive process numbered sequentially, if the process has more than one step?
Are the required values always marked using the same method?
Feedback
Does the interactive system inform about the real state of the process?
Are response times appropriate?
Does information about the pending tasks exist?
Is the user warned about any type of block in the process?
Is the user warned about the automatic tasks those the user have not to pay attention?
If a message transmisstion is not successful, is the sender informed including a description of the problem?
Can the sender retrieve a message which is not received by the receiver?
Are messages as explicit, short and clear as possible?
Can user ask for more details about a error message?
Does the progress of a task appear?
Does a clear difference for users between the write key and the overwrite key appear?
Is there visual feedback in menus or dialog boxes about which choices are selectable?
If multiple options can be selected in a menu or dialog box, is there visual feedback about which options are already selected?
Is there visual feedback when objects are selected or moved?
Reducing memory load

Are old actions visible to be able to see the previous actions?
Are the most important elements highlighted?
Are the goals of the every tasks clear?
Are the groups of content clearly differenciated?
Are large blocks of information divided in shorter?
Are the whole set of actions that users can do clear?
Are the required fields and the optional fields clear in a form ?
Are inactive menu items grayed out or omitted?l
Are the needed information to achieve the goals always visible or is it easy to locate them?
Does not appear any more information of the necessary one that could bother to the user?
Do you find the information at the moment and you do not have to remember previous experiences?
Is the first word of the menu the most important word?
Does the data display start in the upper-left corner of the screen?
Are multiword field labels placed horizontally (not stacked vertically)?
Are there menu selection defaults?
Is every element good integrated into each other element?
Does not appear agglomeration of information in some areas?
Lists
Does the system provide with lists to be able to choose options againts remembering them?
Is single menu options clearly differentiated from multiple menu options?
Easy of use
Is user provided with the essential information to carry out each task?
Are tasks easy to learn and do?
Is information shown in the order that user will use it?
If the system supports both novice and expert users, are multiple levels of detail available?
Are users the initiators of actions rather than the responders?
Do field values avoid mixing alpha and numeric characters whenever possible?
Is the cursor located in the first logical element of the task?
Are long tasks divided into shorter tasks?
Is it avoided that user does more than one difficult tasks?
Are every tasks and information familiar to users?
Are selectable options and non-selectable options differentiated?
Shortcuts
Are there clear shortcuts for priority tasks for expert users?
On data entry screens, do users have the option of either clicking directly on a field or using a keyboard shortcut?
On menus, do users have the option of either clicking directly on a menu item or using a keyboard shortcut?
In dialog boxes, do users have the option of either clicking directly on a dialog box option or using a keyboard shortcut?
Is not appear a tool that does the navigation functions as doing a page as a main page of the navigator or aggregate a page in
the favorite pages?
Help
Can users resume their work at the same stage that they had before they had looked in the help section?
Can user look up the essential help or documentation to be able to use the system without problems?
Is it possible to do a search into the help section?
Does the help interface follow the same aesthetic pattern than the rest of the interface?
Is a guide presented to know what is the next step of an interactive process?

Is the help unnoticed for experts but is it noticed for novel users?
Is the help option clearly visible in the interface?
Are the answer of the helps adapted to the context of the interactive system and the tasks?
If helps is needed for a specific case, does the system work with synonims?
Can users easily switch between help and their work?
Does a training mode exist?
Do different detail levels exist in the help documentation?
Does a glossary exist?
The help answer the questions: What can I do with this program, What is this thing for,How do I do this task,Why did that
happen and Where I am?
On line applications
Is the option of on line help appeared?
Version control
If different versions of the system exist, are the changes of each version correctly documented?
Does the system show help messages for its use?
If posters or documentation of help exists, are this help understood?
Is there an extra resource where user can obtain help to use the interactive system?
Search
Search area
Is the acces to the search form possible through any part of the interactive system?
Is the search field long enough? (between 15 and 30 characters)
Is an advanced search possible?
Is there enough options to carry on an accurate search?
Does the search engine include all the system information?
Are links to Internet search engines included?
Search results
Are search results clear and comprehensible for users?
Does the search engine support user if it can not present results?
Is the information of the results enough according to the goals of the search and the interactive system?
Is it possible to navigate between the results of the search?
Content
Forms
Are forms used to present groups of related fields?
Is there differences between data and labels and another features that are shown?
Has any field a label?
Have all fields a different label?
Are all fields shown in a consistent way?in other words, they have the same format.
Tables
Are the titles of the rows and columns representative according to the content of the tables?
Are the labels of the rows and columns distinguished from the other parts of the table and other content?
Is there a consistent space between the columns of a table and between tables?
Are columns in a table enough separated to assure the insertion of information in the cells of the row without problems?
In tables with many rows, is there a specific feature that allows users to scan the table vertically?
If there are columns sorted using alphabetical order, are these columns left-aligned to allow a fast scan?
Lists
Do numerical list start in 1 and not in 0?
Pictures
Are images labeled and this label appears when the mouse is over the image?
Are animated elements avoided?
Do images have a good resolution to achieve a good visualization?
Information
Does the date of last update or the date of publication of the content appear?
Is the acces to different areas of the system easy?
Are news in a highlight position with a link in the title and a clear summary about the content?
Is there a clear information to contact the responsible of the system?
Graphic or charts
Is the visualization of the charts adapted according to the need that users have un their tasks?
If a specific feature would be highlighted, does a textual description appear apart of a highlighted sign in the graphic?
Is the meaning of the symbols standard in the whole system and in different systems with the same users?
If the information of the graph needs of a precise reading: are these values transcribed to obtain an additional information in the
graphic representation?
Do legend and captions appear?
Does the zoom option appear in any part of the graphic?
If the map is an enlargement or a reduction of the reality, does the scale appear?
If a printing of the graphic is possible,is the printing shown to users in the same way that the printing appear through the
printer?
Format
Do all elements have a different format?
Do all the related data appear in the same screen?
Is the visualization started with a title at the top of the system that describes the content or the goals of the system?
Is the most used content situated at the top of the system?
If a comparison is needed, is the comparable information near to each other?
System Interaction
Is the device that user uses as a mouse intuitive and easy to recognize and use?
Are icons understandable?
Screen
Are the screen inclination and the reflected light adequate?
Is it possible to adapt the colour, the brightness and the contrast to the ambiental conditions?
Does the screen offer a device to change the screen position?
Does the screen not blink?
Mouse
Is the use of the mouse universal?
Is the mouse conventional?
If the mouse has additional buttons, is easy to know the goals of these additional buttons?
Keyboard
Do you have to not do an additional effort to push the keys?
Does the keystroke have a tactile sensation and/or a sonorous sensation?
Do the keys have a tactile mark (Braille language)?
Can you touch the keys without an activation of them?
Is the colour not the only option to differentiate the keys?

Does each different group of keys use a different colour?
Are the labels of the keys readable?
Assistive hardware
If the system has assistive aids, does the system include the needed hardware to user these assistive aids?
Audio
Does the system emit sounds?
If the system emits some sound, is the audio information shown in a visual way on the screen?
Is the volume suitable?
Can user modify the volume?
Indicators
Is the indicator of the printer easy to locate?
Is the indicator of the digital certificate and electronical card easily visible?
Others
Do the system responses arrive in a real and acceptable time?
If the system does not find a concrete answer, does the system have an approximate answer? Is it enough?
Does the set of functions cover all the specified task?
Does the set of functions cover all the user objectives?
Eficiency of use
The system should be efficient according to the use that we can do

It should be possible to customize the interface
It should be possible to reorder or cancel task
There should be support for the basic functions of the keyboard
The basic interaction to the system should be natural
Satisfaction
Usefulnes
Does the set of functions cover all the specified task?
Does the set of functions cover all the user objectives?
Pleasure
Your needs should be satisfied after using the system
Comfort
You should be comfortable using the interface

You should be helped by the interface
Freedom from risk

Economic risk migration
The
The
The
The
The
system
system
system
system
system
should
should
should
should
should
avoid
avoid
avoid
avoid
avoid
mitigating
mitigating
mitigating
mitigating
mitigating
the
the
the
the
the
potential
potential
potential
potential
potential
risk
risk
risk
risk
risk
to
to
to
to
to
finantial status in the intended context of use

efficient operation in the intended context of use
commercial property in the intended context of use
reputation in the intended context of use
other resources in the intended context of use
Health and safe risk migration

The system or the product should avoid mitigating the potential risk to people in the intended contexts of use
The system should be adapted to the context conditions
Environmental risk migration

Users should be provided with a fast way to hide the information that is shown for accidental readers
Log in
A maximum number of times to insert the user and password should exist
Context coverage
Context completeness
[Revisar mismas heursticas que Effectiveness
Feedback
The interactive system should inform about the real state of the process
Response times should be appropriate
Information about the pending tasks should exist
The user should be warned about any type of block in the process
The user should be warned about the automatic tasks those the user have not to pay attention
If a message transmisstion is not successful,the sender should be informed including a description of the problem
The sender should retrieve a message which is not received by the receiver
Messages should be as explicit, short and clear as possible
User should be able to ask for more details about a error message
The progress of a task should appear
A clear difference for users between the write key and the overwrite key should appear
Visual feedback in menus or dialog boxes about which choices are selectable should appear
If multiple options can be selected in a menu or dialog box, visual feedback about which options are already selected should
appear
Visual feedback when objects are selected or moved should appear
Old actions should be visible to be able to see the previous actions?
The most important elements should be highlighted.
The goals of the every task should be clear
The groups of content should be clearly differenciated.
Large blocks of information should be divided in shorter
The whole set of actions that users can do should be clear
The required fields and the optional fields should be clear in a form
Inactive menu items should be grayed out or omitted
The needed information to achieve the goals should be always visible or it should be easy to locate them
More information of the necessary one that could bother to the user should not appear
You should find the information at the moment and you should not have to remember previous experiences
The first word of the menu should be the most important word
The data display should start in the upper-left corner of the screen
Multiword field labels should be placed horizontally (not stacked vertically)
There should be menu selection defaults
Every element should be good integrated into each other element
Agglomeration of information should not appear in any areas
Lists
The system should provide with lists to be able to choose options against remembering them
Single menu options should be clearly differentiated from multiple menu options
Flexibility
Eficiency of use
Minimalist design
Users should be able to use synonymous in the commands
The system shold allow novice users to enter the simplest, most common form of each command, and should allow expert users
to add more parameters
Expert users should have the option of entering multiple commands in a single string
If menu lists are short (seven items or fewer), users should be able to select an item by moving the cursor
If the system uses a type-ahead strategy, the menu items should have mnemonic codes
If the system uses a pointing device, users should have the option of either clicking on fields or using a keyboard shortcut
Only (and all) essential information should appear to decision making displayed on the screen
Groups of items should be separated by a blank space
Each lower-level menu choice should be associated with only one higher level menu
Colors should be used driscreetly
Icons
Every icon should have a simple design
All icons in a set should be visually and conceptually distinct
Each icon should stand out from its background
Icons should be labeled?
there should be no more than twelve to twenty icon types
Icons for essential information of tasks should appear
The use of icons that represent abstract concepts should be avoided
Icons should be concrete and familiar
Control of user
User should be able to pause, stop, replay any action or reproduction of the interactive system
User should be able to move forward and and backward free
User should be warned about tasks to restart or cancel
User should be able to save data as a security copy of the information
User should ask for the information and control its speed of the presentation
User should be able to use every element that the system offers
User feels the total control of the system
In systems that use overlapping windows, it should be easy for users to rearrange windows on the screen
Users should be able to type-ahead in a system with many nested menus
If menu lists are long (more than seven items), users should be able to select an item either by moving the cursor or by typing a
mnemonic code
If the system uses a pointing device, users should have the option of either clicking on menu items or using a keyboard shortcut
Menus should be broad (many items on a menu) rather than deep (many menu levels)
WYSIWYG
The text editor should be a WYSIWYG editor
Easy of use
User should be provided with the essential information to carry out each task
Tasks should be easy to learn and do
Information should be shown in the order that user will use it
If the system supports both novice and expert users, multiple levels of detail should be available
Users should be the initiators of actions rather than the responders
Field values should avoid mixing alpha and numeric characters whenever possible
The cursor should be located in the first logical element of the task
Long tasks should be divided into shorter tasks
It should be avoided that user does more than one difficult tasks
Every tasks and information should be familiar to users
Selectable options and non-selectable options should be differentiated
Shortcuts
There should be clear shourtcuts for priority tasks for expert users
On data entry screens, users should have the option of either clicking directly on a field or using a keyboard shortcut
On menus, users should have the option of either clicking directly on a menu item or using a keyboard shortcut
In dialog boxes, users should have the option of either clicking directly on a dialog box option or using a keyboard shortcut
A tool that does the navigation functions as doing a page as a main page of the navigator or aggregate a page in the favorite
pages should not appear
Version control
If different versions of the system exist, the changes of each version should be correctly documented
The system should show help messages for its use
If posters or documentation of help exists, this help should be understood
There should be an extra resource where user can obtain help to use the interactive system
Search
Search area
The acces to the search form should be possible through any part of the interactive system
The search field should be between 15 and 30 characters
There should be enough options to carry on an accurate search
The search engine should include all the system information
Links to Internet search engines should be included
Search results
Search results should be clear and comprehensible for users
The search engine should support user if it can not present results
The information of the results should be enough according to the goals of the search and the interactive system
To navigate between the results of the search should be possible
Content
Forms
Forms should be used to present groups of related fields
There should be differences between data and labels and another features that are shown
Each field should have a label
All fields should have a different label
All fields should be shown in a consistent way. In other words, they should have the same format.
Tables
The titles of the rows and columns should be representative according to the content of the tables
The labels of the rows and columns should be distinguished from the other parts of the table and other content
There should be a consistent space between the columns of a table and between tables
Columns in a table should be enough separated to assure the insertion of information in the cells of the row without problems
In tables with many rows,there should be a specific feature that allows users to scan the table vertically
If there are columns sorted using alphabetical order, these columns should be left-aligned to allow a fast scan
Lists
Numerical list should start in 1 and not in 0
Pictures
Images should be labeled and this label should appear when the mouse is over the image
Animated elements should be avoided
Images should have a good resolution to achieve a good visualization
Information
The date of last update or the date of publication of the content should appear
The acces to different areas of the system should be easy
There should be a clear information to contact the responsible of the system
Graphic or charts
The visualization of the charts should be adapted according to the need that users have un their tasks
If a specific feature would be highlighted, a textual description should appear apart of a highlighted sign in the graphic
The meaning of the symbols should be standard in the whole system and in different systems with the same users
If the information of the graph needs of a precise reading: these values should be transcribed to obtain an additional information
in the graphic representation
Legend and captions should appear
The zoom option should appear in any part of the graphic
If the map is an enlargement or a reduction of the reality, the scale should appear
If a printing of the graphic is possible, the printing should be shown to users in the same way that the printing appear through
the printer
Format
All elements should have a different format
All the related data should appear in the same screen
The visualization should start with a title at the top of the system that describes the content or the goals of the system
The most used content should be situated at the top of the system
If a comparison is needed, the comparable information should be near to each other
System Interaction
The device that user uses as a mouse should be intuitive and easy to recognize and use
Icons should be understandable
Screen
The screen inclination and the reflected light should be adequate
It should be possible to adapt the colour, the brightness and the contrast to the ambiental conditions
The screen should offer a device to change the screen position
The screen should not blink?
Mouse
The use of the mouse should be universal
The mouse should be conventional
If the mouse has additional buttons, to know the goals of these additional buttonsshould be easy
Keyboard
You should not do an additional effort to push the keys

The keystroke should have a tactile sensation and/or a sonorous sensation
The keys should have a tactile mark (Braille language)
You should touch the keys without an activation of them
The colour should not be the only option to differentiate the keys
Each different group of keys should use a different colour
The labels of the keys should be readable
Assistive hardware
If the system has assistive aids, the system should include the needed hardware to user these assistive aids
Audio
The system should emit sounds
The volume should be suitable
Indicators
The indicator of the printer should be easy to locate
The indicator of the digital certificate and electronical card should be easily visible]
Flexibility
Eficiency of use
Minimalist design
Icons
Control of user
User should be able to modify the information before definitive insert
mnemonic code
Physical distribution
It should be possible to access to the system with wheelchair
External connexions for external devices should be easy to access
The printer should be easy to access
Software of device
The system should have a screen reader for blind people or people with limited visibility
Device interaction
The height of the system should permit the interaction to everybody independently who uses a wheelchair or a very tall or very
short person
The use of the system should not need a hard effort
Product quality model

Functional suitability
Functional completeness
The set of functions should cover all the specified task

The set of functions should cover all the user objectives
Functional correctness
The used technology should be transparent for the user

The system should provide the correct results with the needed degree of precision
Functional appropriateness
It should be possible to reject default values in a fast and easy way

The expresions \"by default\", \"standard\", \"using usual values\" or \"restablish the initial values\" should be avoided
The functions should facilitate the accomplishment of specified tasks and objectives
Preformance efficiency
Time behaviour
Feedback
Resource utilization

The system should be using the needed CPU resources when is performing its functions
Capacity
Log in
Compatibility
Co-existence
The product should perform its required functions efficiently while sharing a common environment and resources with other
products
Interoperability
Usability
Appropriateness recognizability
Consistency
The same elements should appear with the same form or format in the whole interactive system
The same elements should be grouped and located in the same place
Persistent and volatile elements should be distinguished
New functionalities should be distiguished from old functionalities to avoid confusions between them
The user should be warned if any kind of inconsistency appeared
The same concepts should be called equal in whole interactive system
The same colours should be in the whole interactive system
If a consistent interactive system is not possible in its domain, it should be possible in an upper domain.
User should be warned about the continued use of uppercase letters
The active window should be correctly displayed
All windows and pages should have a title
Vertical and horizontal scroll should be possible in all windows
The menu structure should reflect the tasks structure
The sound should be identical for the same actions
The movement of the cursor should be consistent in the whole interactive system
The steps of the interactive process should be numbered sequentially, if the process has more than one step
The required values should be marked using the same method
Feedback
appear
Lists
Flexibility
Eficiency of use
Minimalist design
Icons
Control of user
mnemonic code
WYSIWYG
Easy of use
Shortcuts
Search
Search area
An advanced search should be possible
Search results
Content
Forms
Tables
Lists
Pictures
Information
News should be in a highlight position with a link in the title and a clear summary about the content
Graphic or charts
the printer
Format
System Interaction
Screen
Mouse
Keyboard
Assistive hardware
Audio
If the system emits some sound, the audio information should be shown in a visual way on the screen
The user should be able to modify the volume
Indicators
The indicator of the digital certificate and electronical card should be easily visible
Navigation
Positioning
There should be in the top and the bottom of the page information about where are the users and the last page visited
Links should show where they go using a good title to achieve that users know where they will go if they choose the option
Navigation area
The main navigation area should be situated in an important location or closed to the main content to be an easy and findable
area
Navigation elements should be grouped to get that similar elements are together
There should be an active link to the main page in all pages except in the main page
The menu should be use easily identifiable terms
Every navigation option should be visible without the interaction of the user
A Web map should be exist
Options to navigate forward and behind should appear
If a hierarchy of menus exists, the hierarchy options should be labeled to help user to follow the structure
It should be possible to navigate with the cursor easily and visiblely
Shopping process
If the system presents a shopping cart, a link to the cart should appear in the main page
Emergency exits
User should be able to identify the exits of the application only doing a glance at the interface
If a list has an exit option, this option should be the last one
Learnability
[Los mismos Effectiveness]
Operability
Easy of use
Shortcuts
User error protection

Error management
A confirmation should be required for critical operations
The same error messages should appear in the same situations

The error sounds should be always the same and they should go with a description of the problem?
The validation of the data should be done in a real-time, when user insert the data
Multiple levels of error-message detail should be available
The data should be stored after an occurred error
Error messages should be written in affirmative sentences, positive tone, short, precise, polite and non-offensive
There should be an error prevention
The user should be warned when there is data for storing and the user wants to exit
Errors should be marked and the cursor should be in the first error that has to be solved
the required fields shouls be marked to prevent that users can forget to fill in
Error messages should be deleted when user solve the error
If messages have different levels of urgency, user should be advised about the priority of the problems
Errors should be stored while we are interacting to the system
User should be able to insert a specific character in a required field to postpone the insertion
User interface aesthetics

[los mismo effectiveness]
Accessibility
Software of device
The software should permit users to customize the interface according to the standard configuration of the navigator
Device interaction
short person
Reliability
Maturity
Protection
The encryption of data should be used for the secure transmission of information
Users should be provided with conformation messages before deleting information
The benefits of the registration should be presented
Users should be informed about the periodicity of the information publication before users give system their email
Protected areas should be completely inaccessible
User should confirm any data entry
The system should provide users with the information that the system has stored about the user
Users should be able to update stored data with a previous warning
Data transmission
User should be able to confirm the data transmission before the transmission
A copy of the transmitted message should be saved
it should be possible to print entrance messages and salient messages
Log in
The login process should be consistent, simple and it should protect from a unauthorized use
Users should be able to modify their passwords as they want

The characters of the password should be directly hidden in the form
If the system needs more than one password, the system should use easy techniques to reduce the cognitive load of the user
Availability
The system should be visible where it is located
There should be indicators of the existence of the system close the system
The location of the system should not be a constant walking of people
Software of device
Device interaction
short person
It should be possible to do an update and not another insert after an error
User should be provided with default values that he has to confirm
Fault tolerance
Protection
Data should be stored when users need help
Data which users can not modify should be disabled
Data transmission
Recoverability
Protection
In multiple data entrance, to do a parcial storage should be possible
Data transmission
Security
Confidentiality
Protection
Log in
Integrity
Protection
Log in
Users should be able to access and update data that they have privileges during the session
Non-repudiation
Protection
Data transmission
Accountability
Log in
Authenticity
Some identity of the subject or resource should be the one claimed

The interface should have a copyright
The information should be original and not copied from another source
Maintainability
Modularity
The system or the computer program should be composed of discrete components
It should be possible to change one component getting the minimal impact on other components
Reusability
An asset should be used in more than one system
An asset should be used building other assets
Analysability
Modifiability
Software of device
Protection
Log in
Testability
Portability
Adaptability
Software of device
Device interaction
short person
Installability
The system or the product should be successfully installed and/or unistalled in a specified environment
Replaceability
The system or the product should be upgraded in an easy way and without any problem
2.
UX FACETS
Dependability
Protection
Data transmission
Log in
The system should avoid mitigating the potential risk to finantial status in the intended context of use
The system should avoid mitigating the potential risk to efficient operation in the intended context of use
The system should avoid mitigating the potential risk to commercial property in the intended context of use
The system should avoid mitigating the potential risk to reputation in the intended context of use
The system should avoid mitigating the potential risk to other resources in the intended context of use

Do not add alternative text to avoid robots access
Distorted text should be presented to difficult the text recognizition
Graphic Captcha
Quality standard
Accessibility
Software of device
The system should use in all cases the same operating system
The system should use the same navigator in all cases
Device interaction
short person
Quality standard
Extraordinary users
The application should provide alternative mechanisms for visually impaired users (using Braille keyboard, translation of text to
speech, etc.).
The application should allow users to configure the display of colors restricted.
The application should provide alternative mechanisms for hearing impaired users (using subtitles or translation of the text to
sign language).
The application should allow the configuration of alternative mechanisms for users with hearing problems.
Usability
Consistency

Feedback
appear
Error management

Lists
Flexibility
Eficiency of use
Minimalist design
Icons

Control of user
mnemonic code
WYSIWYG
Easy of use
Shortcuts
Help
Users should be able to resume their work at the same stage that they had before they had looked in the help section
User should look up the essential help or documentation to be able to use the system without problems
It should be possible to do a search into the help section

The help interface should follow the same aesthetic pattern than the rest of the interface
A guide should be presented to know what is the next step of an interactive process
The help should be unnoticed for experts but it should be noticed for novel users
The help option should be clearly visible in the interface
The answer of the helps should be adapted to the context of the interactive system and the tasks
If helps is needed for a specific case, the system should work with synonims
Users should be able to switch between help and their work easily
A training mode should be exist
Different detail levels should exist in the help documentation
A glossary should exist
The help should answer the questions: What can I do with this program, What is this thing for,How do I do this task,Why did that
The option of on line help should be appeared
Version control
Search
Search area
Search results
Content
Forms
Tables
Lists
Pictures
Information
Graphic or charts
the printer
Format
System Interaction
Screen
Mouse
Keyboard

Assistive hardware
Audio
Indicators
Others
The system responses should arrive in a real and acceptable time
If the system does not find a concrete answer, the system should have an approximate answer and it should be enough
Match between the system and the real world
The application elements (interface controls, instructions, etc.) should use familiar words, phrases and concepts to user.
Is the information of the application presented in a simple form?
Information on the application elements should be presented in a natural form.
The steps sequence of the application should follow the mental processes of users.
The application should use icons and user interface controls that correspond with reality.
Icons should help users to better understand (the meanings of) the application.
Icons should be used only for simple concepts and/or tasks.
Important interface controls should be presented on the screen.
The relationship between the interface controls and the real controls should be intuitive.
In the application each option or element should not be over-explained.
Information should be presented in a logical order.
Simplicity
The application interface should be simple, not overloaded with information, options or other elements that distract the user.
The alternatives that the user needs to perform a task should be visible.
The information presented in the application should be simple, concise and clear.
The application elements (interface controls, instructions, etc.) should be clear and intuitive.
The instructions should be preferably in the bottom of the screen.
The long-length text should be divided into sections.
In the application should not have icons, controls, menus, graphics, text or other redundant elements.
The application should not have solely ornamental elements.
The use of icons that represent abstract concepts should be avoided.
Consistency and standards
The use of controls and graphic elements should be consistent in the application interfaces.
Interface controls that appear on different screens should be used whenever the same way.
Each screen that makes up the application should have a consistent visual appearance.
In similar situations should be repeated sequences of actions.
The instructions, error messages, navigation menus, among others, should appear in the same place of the screens that make
up the application.
Interface controls that are repeated throughout the application should have the same functionality and retain the same location.
The size of the text (titles, subtitles, normal text or others) should be consistent in the screens that make up the application.
The application should not be used more than two fonts on a screen.
The text of the application should use Tiresias font.
The text should have a minimum size of 18 points.
Text length should not exceed 90 words on the screen.
Text length should not exceed 45 words per quarter of the screen.
Colors should mantein RGB values within a range of 16-240. That is, strong colors (e.g. red and orange) should have low
intensity and should not use pure black and white colors.
The data entry forms should maintain consistency.
The results of the execution of the tasks should be presented consistently.
The transition from one state to another should be readily apparent to users.
The application should respond clearly to user actions.
The application should show clearly where the user is located.
Each screen that makes up the application should display your relationship with others.
Response times of the application should be appropriate to the mental processes of the users.
The user should be informed if a process requires a long waiting time.
The application should allow users to turn off warnings of feedback that are not considered necessary.
Physical constraints
The size of screen elements should be proportional to the distance between them.
The length and text size should be proportional to the size of device interaction.
The application text should be properly observed in a range of distances from 3 to 5 meters.
Screen elements should be properly observed in various types of illumination.
In the application should be avoided very light or very dark colors.
The application should use dark text on a light background.
Extraordinary users
The application should use properly restrained colors (green and red, in the case of colorblind).
Structure of information
The structure of the elements on the screen should be simple.
The information should be organized hierarchically (e.g. from general to specific, by thematic, etc.).
Related interface controls should be grouped and organized.
The application should use similar colors to group related elements.
The elements on display should be divided into L-shaped (L) inverted ("").
Application elements such as titles and logos should be on the top left corner of the screen.
Navigation options in the application should be located preferably at the bottom of the screen.
Large amount of text should be located to the left of multimedia content.
Small amount of text should be located to the right of multimedia content.
Recognition rather than recall
The main interface controls, instructions, among others, should be always available, visible and easily accessible.
The application should tell the user the data format and units of the values to enter.
The options and / or functions should be easy to find.
The information fields completed by users should be kept in memory.
The application should be customizable according to the needs, characteristics, personal preferences, etc. of the users. The
application should offer users the ability to adjust the size, location, brightness, contrast, transparency, among other
characteristic
The application should allow users to return to the default configuration (or an earlier one) of the elements that comprise it.
The application configuration should be related to the device configuration.
The application should be readily available for connections at different speeds.
The actions performed for the user should not take a long time.
The application should inform to the user whether the execution of an action requires a long time.
The application should respond to the speed of navigation imposed by the user, based on their learning pace.
The application should offer the possibility of data auto input to the user to minimize the time entering data and the possibility
of entering incorrect data.
The application should minimize the use of heavy images (large size in bytes) that influence the time of application load.
The application should suggest programs to users based on their preferences, history of options selected, etc.
The application should offer options to "redo" actions or tasks.
Tasks canceled in the application should immediately stop, providing a proper feedback.
The application should allow the user to override an action in progress.
The application should offer options for returning to a point just before from anywhere.
The application should ask the user to confirm actions that will have drastic consequences, negative or destructive.
Users should have the ability to reverse an application configuration easily.
After agreeing to help, users should continue their activities from where they left broken.
The application should be easy to control by the user, at any time the user should have the ability to hide or quit the application,
to view the program in full screen.
User should be able to identify the exits of the applications only doing a glance at the interface.
The application should provide easily understood messages that prevent errors.
The application should provide selection methods to user (e.g. selecting elements from a list of options) as alternatives for data
entry.
Input fields should indicate the length of the data and values units.
The application should provide wizards for common tasks.
The validation of data should be done in a real-time, when user insert the data.
Recovering from errors
Error messages should be simple and easy to understand.
Error messages should be written in a language familiar to the user.
Error messages should use a terminology and consistent design.
Error messages should suggest the cause of the problem that caused it.
Error messages should indicate what action the user must perform to correct the underlying problem.
Error messages should be written in a constructive way, so it should not attribute blame or insult the user.
Error messages should not use violent or hostile words.
The application should offer a clear and simple help.
Help should be expressed in the user's language, free of jargon and slang.
Help should be easy to find, understand and apply.
Help should be always available.
The sections and information structure of the help should be easily distinguished.
The instructions of the help should follow the actions sequence to realize by the user to achieve a task.
The help interface should be consistent with the application interfaces.
The information should be easy to find in the help.
The information presented in the help should be accurate, complete and understandable.
The help should describe correctly the options that offers the application.
In complex functionalities should be offered help in that same place and time.
The application should have context-sensitive help that guides the user regarding the use of various existing elements.
Playability
Plasticity
products
Quality standard
Emotional
Body expressions
The system should express any emotion through any gesticulation
The system should show different kind of emotions
Emotions should be related to the textual content
The virtual assistant should have a good behaviour according to the receivers of the information
The virtual assistant should include a logo or corporative image that represents the company
Quality standard
Desirable
Findable
Navigation
Positioning
Navigation area
area
Shopping process
Emergency exits
The application should allow a simple navigation, clear and predictable.

It should show the user's location within the application, and basic navigation options.
The application should provide to users a natural way of return in each of the screens that comprise it.
The application should maintain a consistent and coherent navigation across the screens that comprise it.
The application should combine several methods of navigation (e.g. linear and trees, among others).
The application should clearly differentiate a selected option over others.
A selected option should help the user to realize that can move to other options.
The application should provide menus that use the remote control buttons to directly select an option, without any navigation
menu.
The navigation design should be based on the up/down, left/right and OK buttons.
If a user reaches the end of the navigation area, pressing the down arrow button should move the cursor to the initial position of
navigation.
The colored buttons on the Set-Top-Box remote control listed on the application should be presented horizontally and in the
same order they appear on the remote control.
Each color button should have a single label and navigation function.
There should be an active option to the main interface in all screens except in the main interface.
Useful

Quality standard
Comunicability
Dialog
The system should use affirmative sentences
Sentences should be without any ambiguity?
Vocabularyshould be familiar for the users
Terms form a jargon should not appear
Information should be presented in a consistent way with consistent structures and correctly grammatically
Information should be presented in a logical way
Uppercase mode should be used only when it is essential
Punctuation should be used correctly avoiding exclamation signs
The use of prefixes that qualify the sense of the sentence should be avoided
The dialogs with the main information should be shown as simplified as possible?
End lines with broken words should be avoided
If it is essential to remember an item, it should be located in a highlighted and unusual position
Whole text should be presented in the same page to avoid the broken text in more than one page
Sentences should be short and simple
The main ideas should be in the first lines of the text
Sentences should be in active voice
The repetition of the content should be avoided
If the content is enough clear, the part of content should not labeled
Lists and categories with one option should be avoided
An imperative mode for required actions should be used
The system should has an understandable URL
Abbreviations
Abbreviations should be used only if they have a minor meaning

A different abbreviation should be used for each word
The way for doing the abbreviation should be always the same
A dictionary of abbreviations should be provided
The abbreviations should use only with the needed information
Less clear abbreviations should be avoided
The meaning of the abbreviations should be immediately presented after the first occurence
Abbreviations should not include punctuation?
Conversation
The system should permit to insert question in different languages
The system should present audio
The system should inform about the information that it has
The messages of the system should be rotary, always different or they are changing constantly
Sentences should be coherent and they should suit with the questions
If the system does not have the needed information, the system should inform to user about it
User should be able to contextualize the question and the system should present the same results
The system should be able to relate different questions to delimit the results of the search
The system should identify a change of the topic
Cross-cultural
Dates and times

Update dates and time should appear in essential cases as prices
The last time and date that the information is updated should appear
The time zone should appear
a.m and p.m abbreviations should be used
The month should be written or abbreviated but not in a numerical form
Numerical values
The points should line up to the right and the real ones in the decimal comma
The system should use arabic numbers(1,2,3,4,5,6,7,8,9,0)
Each numerical value should add the specific metric unit
Specific applications
The monetary sign should appear
Numbers should be formated using points for thousands
Cross- cultural
Used techniques to the data transfer should be adapted to any culture
Multilanguage option should appear?
3.
FUNCTIONALITY
To look up information

Icons
mnemonic code
Easy of use

Search
Search area
Search results
Content
Information
Graphic or charts
the printer
Format
Navigation
Positioning
Navigation area
area
Dates and times
Numerical values
Cross- cultural
To do procedures
[same]
To register
Flexibility
Content
Forms

Dates and times
Cross- cultural
To log in
Content
Forms
Log in
Cross- cultural
To fill in forms
Error management

Lists
Control of user
WYSIWYG
Help
Content
Forms
Lists
Format

Data transmission
Dates and times
Cross- cultural
To print conformations
Device interaction
short person
4.
FEATURES
It has software part
Feedback

appear
Error management

Lists
Flexibility
Eficiency of use
Minimalist design
Icons
Control of user
mnemonic code
WYSIWYG
Easy of use
Shortcuts
Help
Version control

Search
Search area
Search results
Content
Forms
Tables
Lists
Pictures
Information
Graphic or charts
the printer
Format
System Interaction
Audio
Others
Software of device
Protection

Data transmission
Log in
Abbreviations
Dates and times

Numerical values
Cross- cultural
products
Public administration
It has hardware part
Screen
Mouse
Keyboard
Assistive hardware
Audio
Indicators
Device interaction
short person
products
It simulates the human behaviors

Others
Body expressions
Dialog
5.
Software
COMPONENTS
Consistency

Feedback
appear
Error management

Flexibility
Eficiency of use
Minimalist design
Control of user
mnemonic code
Easy of use
Others
Software of device
Protection
Data transmission
Log in
Navigation
Positioning
Navigation area
area
Shopping process
Emergency exits

Abbreviations
Dates and times
Cross- cultural
products
Type of content
Forms
Easy of use
Content
Forms
Log in

entry.
Tables
Consistency
Content
Tables
Lists
Lists
Content
Lists
Dates
Dates and times

Times
Dates and times
Numerical values
Numerical values

Money signs
Consistency
Simplicity
Information
Content
Information
Pictures
Consistency
Content
Pictures
Simplicity
News
Simplicity
Graphics
Consistency
Content
Graphic or charts
the printer
Simplicity
Format
Content
Format
Text
Consistency
Control of user
WYSIWYG

Cross- cultural
Simplicity
The long-length text should be divided into sections.
The length and text size should be proportional to the size of device interaction.
Large amount of text should be located to the left of multimedia content.
Small amount of text should be located to the right of multimedia content.
URL
Simplicity
Abbreviations
Consistency
Abbreviations

Simplicity
Audio
Consistency
Audio
Simplicity
Nomenclature
Consistency
Simplicity
Colours
Consistency
Screen
Software of device
Colors should mantein RGB values within a range of 16-240. That is, strong colors (e.g. red and orange) should have low
intensity and should not use pure black and white colors.
Extraordinary users
The application should use properly restrained colors (green and red, in the case of colorblind).
Icons
Consistency
Flexibility
Icons
System Interaction
Simplicity
Data management
Protection

Information transmission
Data transmission
Log in
Sign in form
Consistency
Simplicity

Log in form
[lo mismo que antes]
Updating information
Consistency
Simplicity
Information validation
Consistency
Simplicity
Information recovery

Search
Search form
Consistency
Search
Search area

Simplicity
Results of search
Consistency
Search
Search results
Simplicity

Navigation rea
Consistency
Navigation
Positioning
Navigation area
area
The steps sequence of the application should follow the mental processes of users.

Important interface controls should be presented on the screen.
In the application each option or element should not be over-explained.
Simplicity
The application interface should be simple, not overloaded with information, options or other elements that distract the user.
The alternatives that the user needs to perform a task should be visible.
The instructions should be preferably in the bottom of the screen.
The use of controls and graphic elements should be consistent in the application interfaces.
Interface controls that appear on different screens should be used whenever the same way.
Each screen that makes up the application should have a consistent visual appearance.
In similar situations should be repeated sequences of actions.
The instructions, error messages, navigation menus, among others, should appear in the same place of the screens that make
up the application.
Interface controls that are repeated throughout the application should have the same functionality and retain the same location.
The results of the execution of the tasks should be presented consistently.
The transition from one state to another should be readily apparent to users.
The application should respond clearly to user actions.
The application should show clearly where the user is located.
Each screen that makes up the application should display your relationship with others.
Response times of the application should be appropriate to the mental processes of the users.
The user should be informed if a process requires a long waiting time.

The elements on display should be divided into L-shaped (L) inverted ("").
Navigation options in the application should be located preferably at the bottom of the screen.
The application should allow a simple navigation, clear and predictable.
It should show the user's location within the application, and basic navigation options.
The application should provide to users a natural way of return in each of the screens that comprise it.
The application should maintain a consistent and coherent navigation across the screens that comprise it.
The application should combine several methods of navigation (e.g. linear and trees, among others).
The application should clearly differentiate a selected option over others.
A selected option should help the user to realize that can move to other options.
The application should provide menus that use the remote control buttons to directly select an option, without any navigation
menu.
The navigation design should be based on the up/down, left/right and OK buttons.
If a user reaches the end of the navigation area, pressing the down arrow button should move the cursor to the initial position of
navigation.
The colored buttons on the Set-Top-Box remote control listed on the application should be presented horizontally and in the
same order they appear on the remote control.
Each color button should have a single label and navigation function.
There should be an active option to the main interface in all screens except in the main interface.
The options and / or functions should be easy to find.
The actions performed for the user should not take a long time.
The application should inform to the user whether the execution of an action requires a long time.
The application should respond to the speed of navigation imposed by the user, based on their learning pace.
The application should offer options to "redo" actions or tasks.
Tasks canceled in the application should immediately stop, providing a proper feedback.
The application should allow the user to override an action in progress.
The application should offer options for returning to a point just before from anywhere.
The application should ask the user to confirm actions that will have drastic consequences, negative or destructive.
The application should be easy to control by the user, at any time the user should have the ability to hide or quit the application,
to view the program in full screen.
entry.
Window

Pages
Navigation
Positioning
Titles
Cursor
Consistency
Error management
Flexibility
Control of user
mnemonic code
Easy of use
Navigation
Shortcuts
Shortcuts
Emergency exits
Consistency
Emergency exits
Simplicity
Hardware
Device interaction
short person
products
Operating System
Software of device
Navigator
Software of device
In/out devices
Software of device
Printer
Digital certificate
Indicators
Electronic card
Indicators
Mouse
System Interaction
Mouse
Screen
Screen
Software of device
Keyboard
Keyboard

Assistive aids
Software of device
Assistive hardware
Assistive hardware
Audio
Volumen
Indicators
Indicators
Help and documentation

Help
Version control

The application should offer a clear and simple help.
Help should be expressed in the user's language, free of jargon and slang.
Help should be easy to find, understand and apply.
Help should be always available.
The sections and information structure of the help should be easily distinguished.
The instructions of the help should follow the actions sequence to realize by the user to achieve a task.
The help interface should be consistent with the application interfaces.
The information should be easy to find in the help.
The information presented in the help should be accurate, complete and understandable.
The help should describe correctly the options that offers the application.
In complex functionalities should be offered help in that same place and time.
The application should have context-sensitive help that guides the user regarding the use of various existing elements.
Localization
Indicators
Human behaviour
Body expressions
Dialog
Conversation
Graphic captcha
Do not add alternative text to avoid robots access
Distorted text should be presented to difficult the text recognizition
Graphic Captcha
Buttons
Consistency
Simplicity
Settings
Restricted colours
Extraordinary users
The application should provide alternative mechanisms for visually impaired users (using Braille keyboard, translation of text to
speech, etc.).
Restricted sounds
Extraordinary users
The application should provide alternative mechanisms for hearing impaired users (using subtitles or translation of the text to
sign language).
The application should allow the configuration of alternative mechanisms for users with hearing problems.
Error management
Error message
Recovering from errors
Error messages should be simple and easy to understand.
Error messages should be written in a language familiar to the user.
Error messages should use a terminology and consistent design.
Error messages should suggest the cause of the problem that caused it.
Error messages should indicate what action the user must perform to correct the underlying problem.
Error messages should be written in a constructive way, so it should not attribute blame or insult the user.
Error messages should not use violent or hostile words.
Configuration
Consistency
The application should be customizable according to the needs, characteristics, personal preferences, etc. of the users. The
application should offer users the ability to adjust the size, location, brightness, contrast, transparency, among other
characteristic
The application should allow users to return to the default configuration (or an earlier one) of the elements that comprise it.
The application configuration should be related to the device configuration.
Users should have the ability to reverse an application configuration easily.
Xerox Usability Evaluation (296 heuristics)

1. Visibility of System Status
The system should always keep user informed about what is going on, through appropriate feedback within reasonable time.
#
1.1
Review Checklist
Does every display begin with a title or header that describes
screen contents?
1.2
Is there a consistent icon design scheme and stylistic treatment

across the system?
1.3
Is a single, selected icon clearly visible when surrounded by

unselected icons?
1.4
Do menu instructions, prompts, and error messages appear in

the same place(s) on each menu?
1.5
In multipage data entry screens, is each page labeled to show its

relation to others?
1.6
If overtype and insert mode are both available, is there a visible

indication of which one the user is in?
1.7
If pop-up windows are used to display error messages, do they

allow the user to see the field in error?
1.8
Is there some form of system feedback for every operator

action?
1.9
After the user completes an action (or group of actions), does the
feedback indicate that the next group of actions can be started?
1.1
0
Is there visual feedback in menus or dialog boxes about which

choices are selectable?
1.1
1
Is there visual feedback in menus or dialog boxes about which

choice the cursor is on now?
1.1
2
If multiple options can be selected in a menu or dialog box, is

there visual feedback about which options are already selected?
1.1
3
Is there visual feedback when objects are selected or moved?
1.1
4
Is the current status of an icon clearly indicated?
Review Checklist
1.1
5
Is there feedback when function keys are pressed?
1.1
6
If there are observable delays (greater than fifteen seconds) in

the systems response time, is the user kept informed of the
system's progress?
1.1
7
Are response times appropriate to the task?
1.1
8
Typing, cursor motion, mouse selection: 50-1 50

milliseconds
1.1
9
Simple, frequent tasks: less than 1 second
1.2
0
Common tasks: 2-4 seconds
1.2
1
Complex tasks: 8-12 seconds
1.2
2
Are response times appropriate to the user's cognitive

processing?
1.2
3
Continuity of thinking is required and information must be

remembered throughout
several responses: less than two seconds.
1.2
4
High levels of concentration aren't necessary and

remembering information is
not required: two to fifteen seconds.
1.2
5
Is the menu-naming terminology consistent with the user's task

domain?
1.2
6
Does the system provide visibility: that is, by looking, can the
user tell the state of the system and the alternatives for action?
1.2
7
Do GUI menus make obvious which item has been selected?
1.2
8
Do GUI menus make obvious whether deselection is possible?
1.2
9
If users must navigate between multiple screens, does the

system use context labels, menu maps, and place markers as
navigational aids?
2. Match Between System and the Real World

The system should speak the users language, with words, phrases and concepts familiar to the user, rather than systemoriented terms. Follow real-world conventions, making information appear in a natural and logical order.
#
Review Checklist
2.1
Are icons concrete and familiar?
2.2
Are menu choices ordered in the most logical way, given the
user, the item names, and the task variables?
2.3
If there is a natural sequence to menu choices, has it been used?
2.4
Do related and interdependent fields appear on the same

screen?
2.5
If shape is used as a visual cue, does it match cultural

conventions?
2.6
Do the selected colors correspond to common expectations

about color codes?
2.7
When prompts imply a necessary action, are the words in the

message consistent with that action?
2.8
Do keystroke references in prompts match actual key names?
2.9
On data entry screens, are tasks described in terminology

familiar to users?
2.1
0
Are field-level prompts provided for data entry screens?
2.1
1
For question and answer interfaces, are questions stated in

clear, simple language?
2.1
2
Do menu choices fit logically into categories that have readily

understood meanings?
2.1
3
Are menu titles parallel grammatically?
2.1
4
Does the command language employ user jargon and avoid

computer jargon?
2.1
5
Are command names specific rather than general?
2.1
6
Does the command language allow both full names and

abbreviations?
2.1
7
Are input data codes meaningful?
2.1
8
Have uncommon letter sequences been avoided whenever

possible?
2.1
9
Does the system automatically enter leading or trailing spaces to

align decimal points?
2.2
0
Does the system automatically enter a dollar sign and decimal

for monetary entries?
Review Checklist
2.2
1
Does the system automatically enter commas in numeric values

greater than 9999?
2.2
2
Do GUI menus offer activation: that is, make obvious how to say
now do it"?
2.2
3
Has the system been designed so that keys with similar names
do not perform opposite (and potentially dangerous) actions?
2.2
4
Are function keys labeled clearly and distinctively, even if this

means breaking consistency rules?
3. User Control and Freedom

Users should be free to select and sequence tasks (when appropriate), rather than having the system do this for them. Users
often choose system functions by mistake and will need a clearly marked emergency exit to leave the unwanted state without
having to go through an extended dialogue. Users should make their own decisions (with clear information) regarding the costs
of exiting current work. The system should support undo and redo.
#
Review Checklist
3.1
If setting up windows is a low-frequency task, is it particularly

easy to remember?
3.2
In systems that use overlapping windows, is it easy for users to

rearrange windows on the screen?
3.3
In systems that use overlapping windows, is it easy for users to

switch between windows?
3.4
When a user's task is complete, does the system wait for a

signal from the user before processing?
3.5
Can users type-ahead in a system with many nested menus?
3.6
Are users prompted to confirm commands that have drastic,

destructive consequences?
3.7
Is there an "undo" function at the level of a single action, a data

entry, and a complete group of actions?
3.8
Can users cancel out of operations in progress?
3.9
Are character edits allowed in commands?
3.1
0
Can users reduce data entry time by copying and modifying

existing data?
3.1
1
Are character edits allowed in data entry fields?
3.1
2
If menu lists are long (more than seven items), can users select
an item either by moving the cursor or by typing a mnemonic
code?
3.1
3
If the system uses a pointing device, do users have the option of

either clicking on menu items or using a keyboard shortcut?
3.1
4
Are menus broad (many items on a menu) rather than deep

(many menu levels)?
3.1
5
If the system has multiple menu levels, is there a mechanism

that allows users to go back to previous menus?
Review Checklist
3.1
6
If users can go back to a previous menu, can they change their

earlier menu choice?
3.1
7
Can users move forward and backward between fields or dialog

box options?
3.1
8
If the system has multipage data entry screens, can users move
backward and forward among all the pages in the set?
3.1
9
If the system uses a question and answer interface, can users go

back to previous questions or skip forward to later questions?
3.2
0
Do function keys that can cause serious consequences have an

undo feature?
3.2
1
Can users easily reverse their actions?
3.2
2
If the system allows users to reverse their actions, is there a

retracing mechanism to allow for multiple undos?
3.2
3
Can users set their own system, session, file, and screen
defaults?
4. Consistency and Standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform
conventions.
#
Review Checklist
4.1
Have industry or company formatting standards been followed

consistently in all screens within a system?
4.2
Has a heavy use of all uppercase letters on a screen been

avoided?
4.3
Do abbreviations not include punctuation?
4.4
Are integers right-justified and real numbers decimal-aligned?
4.5
Are icons labeled?
4.6
Are there no more than twelve to twenty icon types?
4.7
Are there salient visual cues to identify the active window?
4.8
Does each window have a title?
4.9
Are vertical and horizontal scrolling possible in each window?
4.1
0
Does the menu structure match the task structure?
4.1
1
Have industry or company standards been established for menu

design, and are they applied consistently on all menu screens in
the system?
4.1
2
Are menu choice lists presented vertically?
4.1
3
If "exit" is a menu choice, does it always appear at the bottom of

the list?
4.1
4
Are menu titles either centered or left-justified?
4.1
Are menu items left-justified, with the item number or mnemonic
preceding the name?
4.1
6
Do embedded field-level prompts appear to the right of the field

label?
4.1
7
Do on-line instructions appear in a consistent location across

screens?
4.1
8
Are field labels and fields distinguished typographically?
4.1
9
Are field labels consistent from one data entry screen to

another?
4.2
0
Are fields and labels left-justified for alpha lists and right-justified
for numeric lists?
Review Checklist
4.2
1
Do field labels appear to the left of single fields and above list
fields?
4.2
2
Are attention-getting techniques used with care?
4.2
3
Intensity: two levels only
4.2
4
Size: up to four sizes
4.2
5
Font: up to three
4.2
6
Blink: two to four hertz
4.2
7
Color: up to four (additional colors for occasional use only)
4.2
8
Sound: soft tones for regular positive feedback, harsh for

rare critical conditions
4.2
9
Are attention-getting techniques used only for exceptional

conditions or for time-dependent information?
4.3
0
Are there no more than four to seven colors, and are they far
apart along the visible spectrum?
4.3
1
Is a legend provided if color codes are numerous or not obvious

in meaning?
4.3
2
Have pairings of high-chroma, spectrally extreme colors been

avoided?
4.3
3
Are saturated blues avoided for text or other small, thin line
symbols?
4.3
4
Is the most important information placed at the beginning of the

prompt?
4.3
Are user actions named consistently across all prompts in the
system?
4.3
6
Are system objects named consistently across all prompts in the

system?
4.3
7
Do field-level prompts provide

restatement of the field name?
4.3
8
For question and answer interfaces, are the valid inputs for a
question listed?
4.3
9
Are menu choice names consistent, both within each menu and
across the system, in grammatical style and terminology?
4.4
0
Does the structure of menu

corresponding menu titles?
4.4
1
Are commands used the same way, and do they mean the same
thing, in all parts of the system?
4.4
2
Does the command language have a consistent, natural, and

mnemonic syntax?
4.4
3
Do abbreviations follow a simple primary rule and, if necessary,

a simple secondary rule for abbreviations that otherwise would
be duplicates?
more
choice
information
names
than
match
their
Review Checklist
4.4
4
Is the secondary rule used only when necessary?
4.4
5
Are abbreviated words all the same length?
4.4
6
Is the structure of a data entry value consistent from screen to

screen?
4.4
7
Is the method for moving the cursor to the next or previous field
consistent throughout the system?
4.4
8
If the system has multipage data entry screens, do all pages

have the same title?
4.4
9
If the system has multipage data entry screens, does each page
have a sequential page number?
4.5
0
Does the system follow industry or company standards for

function key assignments?
4.5
1
Are high-value, high-chroma colors used to attract attention?
5. Help Users Recognize, Diagnose, and Recover From Errors

Error messages should be expressed in plain language(NO CODES).
#
Review Checklist
5.1
Is sound used to signal an error?
5.2
Are prompts stated constructively, without overt or implied

criticism of the user?
5.3
Do prompts imply that the user is in control?
5.4
Are prompts brief and unambiguous.
5.5
Are error messages worded so that the system, not the user,
takes the blame?
5.6
If humorous error messages are used, are they appropriate and

inoffensive to the user population?
5.7
Are error messages grammatically correct?
5.8
Do error messages avoid the use of exclamation points?
5.9
Do error messages avoid the use of violent or hostile words?
5.1
0
Do error messages avoid an anthropomorphic tone?
5.1
1
Do all error messages in the system use consistent grammatical

style, form, terminology, and abbreviations?
5.1
2
Do messages place users in control of the system?
5.1
3
Does the command language use normal action-object syntax?
5.1
4
Does the command language avoid arbitrary, non-English use of

punctuation, except for symbols that users already know?
5.1
5
If an error is detected in a data entry field, does the system

place the cursor in that field or highlight the error?
5.1
Do error messages inform the user of the error's severity?
6
5.1
7
Do error messages suggest the cause of the problem?
5.1
8
Do error messages provide appropriate semantic information?
5.1
9
Do error messages provide appropriate syntactic information?
5.2
0
Do error messages indicate what action the user needs to take

to correct the error?
5.2
1
If the system supports both novice and expert users, are

multiple levels of error-message detail available?

Set of Heuristics Llcia More

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Set of Heuristics Llcia More

Transféré par

Droits d'auteur :

Formats disponibles

SET OF HEURISTICS LLCIA

Heuristics for the evaluator & designer

Reducing memory load

Is a guide presented to know what is the next step of an interactive process?

Is the colour not the only option to differentiate the keys?

The system should be efficient according to the use that we can do

You should be comfortable using the interface

Freedom from risk

finantial status in the intended context of use

Health and safe risk migration

The system should be adapted to the context conditions

Environmental risk migration

You should not do an additional effort to push the keys

Product quality model

The set of functions should cover all the specified task

The used technology should be transparent for the user

It should be possible to reject default values in a fast and easy way

The used technology should be transparent for the user

User error protection

The same error messages should appear in the same situations

User interface aesthetics

Users should be able to modify their passwords as they want

Some identity of the subject or resource should be the one claimed

The interface should have a copyright

Persistent and volatile elements should be distinguished

Errors should be stored while we are interacting to the system

Each icon should stand out from its background

It should be possible to do a search into the help section

The keys should have a tactile mark (Braille language)

The application should allow a simple navigation, clear and predictable.

The set of functions should cover all the specified task

Abbreviations should be used only if they have a minor meaning

Dates and times

The same colours should be in the whole interactive system

Users should be the initiators of actions rather than the responders

Forms should be used to present groups of related fields

The same error messages should appear in the same situations

Users should be provided with conformation messages before deleting information

It has software part

Response times should be appropriate

There should be menu selection defaults

The system should show help messages for its use

Users should be able to update stored data with a previous warning

The time zone should appear

It simulates the human behaviors

Persistent and volatile elements should be distinguished

Errors should be stored while we are interacting to the system

The main ideas should be in the first lines of the text

Text length should not exceed 90 words on the screen.

Information on the application elements should be presented in a natural form.

Information should be presented in a logical order.

The repetition of the content should be avoided

A dictionary of abbreviations should be provided

Data should be stored when users need help

The structure of the elements on the screen should be simple.

[lo mismo que antes]

Data which users can not modify should be disabled

Information on the application elements should be presented in a natural form.

The text should have a minimum size of 18 points.

Icons should be used only for simple concepts and/or tasks.

The application should use similar colors to group related elements.

All windows and pages should have a title

The keystroke should have a tactile sensation and/or a sonorous sensation