Computing and Software Wiki - User contributions [en]

User:Skip

2009-11-23T19:41:32Z

Livierja: /* Topics: */

= Human Computer Interaction =

=='''This is the projects main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==

===Objectives===

===Logistics===
<ul>
<li>
During the middle of term the class will be divided into about 12 (n) groups, each of whom will negotiate amongst
themselves a topic of concentration from the list below with at least three ranked by selected priority.
At an early designated lecture, each group will be linked to a topic of their choice in a first-come/first-served
basis -- only one group per project.
</li>
<li>
Group members should all have their associated member email addresses and use these to generate a wiki in one of the
groups member names. Note that ALL changes made to a wiki are logged by IP address of the machine, as well as time
and date. By law Derek Lipiec MUST always be running an audit trail system which essentially operates as a key logger
in that if any vandalism is done electronically, he can determine who is logged on, from where as well as what was typed.
This is a warning that anyone modifying a group's wiki who is NOT a member of that group will be caught and risk a zero
grade for this assignment exists. Therefore "play safe" and do not fool around. (wfsp)
</li>
<li>
Just after several weeks of class duration, a created wiki from each group will be completed
and marked. As soon as scheduled, these dates will be posted in the ELM calendar for this course.
</li>
<li>
Part of this mark will be composed of 12 other rankings (by three groups of four members each as listed below)
from each of the other group members, done individually, who will rank and provide one sentence
of what is best and one sentence of what is worst about the subject wiki under consideration. This is done
through sending Dr.Poehlman an email with the three marks and single sentences for like and dislike reasons.
The ranking for each wiki will be compiled by the instructor and posted anonymously for class consideration
and discussion near the end of term.
</li>
</ul>

===Topics:===
Reference -- adapted from ACM (Association for Computing Machinery -- but people can join, too!) http://wiki.acm.org/cs2001/index.php?title=HUMAN-COMPUTER_INTERACTION
<OL>
<Li> '''Motivation:''' Why the study of how people interact with technology is vital for the development of most usable and acceptable systems. [[Motivations for the Studying of HCI]] (Taken by Group 10 -- wfsp/15nov09@14:30) </Li>
<Li> '''Contexts for HCI:''' mobile devices, consumer devices, business applications, web, business applications, collaboration systems, games, etc. [[Contexts for HCI]] (Taken by Group 8 -- wfsp/05nov09@14:00)</Li>
<Li> '''[[Process_for_User-centered_Development]]:''' early focus on users, empirical testing, iterative design. (Specified for Group 11 -- wfsp/15nov09@14:30) </Li>
<Li> '''Different measures for evaluation:''' utility, efficiency, learnability, user satisfaction. (Taken by Group 5 -- wfsp/10nov09@13:00)</Li>
<Li> '''Models that inform human-computer interaction (HCI) design:''' attention, perception and recognition, movement, and cognition.</Li>
<Li> '''Social issues influencing HCI design and use:''' culture, communication, and organizations. (Taken by Group 3 -- wfsp/13nov09@15:30) </Li>
<Li> '''[[HCI - Accommodating human diversity]]:''' including universal design and accessibility and designing for multiple cultural and linguistic contexts. (Taken by Group 9 -- wfsp/12nov09@13:30)</Li>
<Li> The most '''[[Common Interface Mistakes]]'''. (Taken by Group 1 -- wfsp/04nov09@17:00)</Li>
<Li> '''[[User Interface Standards]]'''. (Taken by Group 6 -- wfsp/05nov09@19:30)</Li>
<Li> The '''five interaction styles''' as espoused by [[B.Scheidermann]]. (Taken by Group 7 -- wfsp/04nov09@17:30)</Li>
<Li> The '''Object-Action''' (or visa-versa) '''model''' and its applications. [[The Object-Action (or_visa-versa) model and its applications]](Specified for Group 2 -- wfsp/15nov09@14:30) </Li>
<Li> The '''direct manipulation method''' and its importance to CHI. [[Direct Manipulation]] (Taken by Group 4 -- wfsp/06nov09@09:30) </Li>
</OL>
<h4>
Marking Duties for Each Group:
</h4>
<table border="1">
<tr>
<th>
Group Mark1 Mark2 Mark3
</th>
</tr>
<tr>
<td>
1 Group 2 Group 3 Group 4
</td>
</tr>
<tr>
<td>
2 Group 3 Group 4 Group 5
</td>
</tr>
<tr>
<td>
3 Group 4 Group 5 Group 6
</td>
</tr>
<tr>
<td>
4 Group 5 Group 6 Group 7
</td>
</tr>
<tr>
<td>
5 Group 6 Group 7 Group 8
</td>
</tr>
<tr>
<td>
6 Group 7 Group 8 Group 9
</td>
</tr>
<tr>
<td>
7 Group 8 Group 9 Group 10
</td>
</tr>
<tr>
<td>
8 Group 9 Group 10 Group 11
</td>
</tr>
<tr>
<td>
9 Group 10 Group 11 Group 01
</td>
</tr>
<tr>
<td>
10 Group 11 Group 01 Group 02
</td>
</tr>
<tr>
<td>
11 Group 01 Group 02 Group 03
</td>
</tr>
</table>

----

=='''This is the VRML assignment main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==
NOTE: This is NOT required for the 2009-2010 version of this course.
===Some Important References:===

<UL>
<li>
The Custom Courseware for this course has an Appendix section for VRML beginners so this is a good place to begin studying if you are not familiar with the Virtual Reality Modelling Language. We will be using this to create 3-D interfaces for 3-D worlds, just to get some practice in thinking in more than two dimensions. Although VRML has been around for more than a decade, it is still found as the 3-D layer in MPEG4, has been updated and in a standard in the W3C world known as X3D, which is just VRML with <elements> instead of reserved keywords. If you know VRML, you know X3D.
</li>
<li>
To begin our study of the Virtual Reality Modeling Language (VRML), we need to get setup to view the VRML code (which is in pure ASCII, as is Javascript, etc.) To create VRML, use any ASCII editor that you like best. I use Crimson Editor which has a built-in context sensitive markup that understands VRML, so it is easy to distinguish comments from verbs and nouns, etc.
Go to http://sourceforge.net/projects/emeraldeditor/files/ where Emerald Editor (the newest version of the Crimson editor) can be downloaded freely. To interpret VRML code (nested in HTML code) you need a plug-in. The best that I have found is called Cortona from Parallel Graphics at http://www.cortona3d.com/cortona/ . It works best with Apple Safari Browser version 4 from http://www.apple.com/safari/download/ . All of this information is at the end of the course web site section on VRML at http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML headed with the title "Recommended Client Applications". By the way, Parallel Graphics has an editor called VRMLPad that is not free but can be downloaded as a trial version, which may help the beginner as it provides a thumbnail sketch at the margin right when it recognizes any VRML code shape primitives -- interesting thing to see work.
</li>
<li>
As far as web references go, the best place to start is on the course web site: --
http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML
</li>
<ol>
<li>
Once here you can take the tutorial, done by a senior thesis student Polo Cerone several year's ago.
It can be taken on-line or downloaded and worked through locally -- either is equivalent.
</li>
<li>
Once the tutorial is taken, there are many example VRML code snippets that can be viewed with whatever browser plug-in that you have installed. Pay particular attention to the graduated examples that show how one specifically goes about creating an interface in VRML that controls objects in the main scene graph. This is located back near the beginning of the VRML section titled "Graduated VRML2 Interface Examples".
</li>
</ol>
</UL>

HCI - Accommodating human diversity

2009-11-23T17:27:10Z

Livierja: /* Accessibility */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Gender'''
::Males and females tend to interact differently with computers; ideally, interfaces should be designed to be gender-neutral. Study in this field has uncovered gender differences relating to user confidence/behaviour and hardware interaction. [http://en.wikipedia.org/wiki/Gender_HCI R5]
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect. See also [http://www.cas.mcmaster.ca/wiki/index.php/HCI_-_Accommodating_human_diversity#Cultural_Context Cultural Context].
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::When designing for special populations, the capabilities of the user must be taken into account. An interface for such a population should be as straightforward and easy to learn as possible.
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=See Also=
:# [http://en.wikipedia.org/wiki/List_of_human-computer_interaction_topics List of HCI Topics]
=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]
:# [http://en.wikipedia.org/wiki/Gender_HCI Gender HCI]

HCI - Accommodating human diversity

2009-11-23T16:19:54Z

Livierja: /* Human Properties */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Gender'''
::Males and females tend to interact differently with computers; ideally, interfaces should be designed to be gender-neutral. Study in this field has uncovered gender differences relating to user confidence/behaviour and hardware interaction. [http://en.wikipedia.org/wiki/Gender_HCI R5]
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect. See also [http://www.cas.mcmaster.ca/wiki/index.php/HCI_-_Accommodating_human_diversity#Cultural_Context Cultural Context].
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::When designing for special populations, the capabilities of the user must be taken into account. An interface for such a population should be as straightforward and easy to learn as possible.
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=See Also=
:# [http://en.wikipedia.org/wiki/List_of_human-computer_interaction_topics List of HCI Topics]
=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]
:# [http://en.wikipedia.org/wiki/Gender_HCI Gender HCI]

HCI - Accommodating human diversity

2009-11-23T16:18:51Z

Livierja: /* Human Properties */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Gender'''
::Males and females tend to interact differently with computers; ideally, interfaces should be designed to be gender-neutral. Study in this field has uncovered gender differences relating to user confidence/behaviour and hardware interaction. [http://en.wikipedia.org/wiki/Gender_HCI R5]
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::When designing for special populations, the capabilities of the user must be taken into account. An interface for such a population should be as straightforward and easy to learn as possible.
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=See Also=
:# [http://en.wikipedia.org/wiki/List_of_human-computer_interaction_topics List of HCI Topics]
=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]
:# [http://en.wikipedia.org/wiki/Gender_HCI Gender HCI]

HCI - Accommodating human diversity

2009-11-23T16:18:09Z

Livierja: /* References */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Gender'''
::Males and females tend to interact differently with computers; ideally, interfaces should be designed to be gender-neutral. Study in this field has uncovered gender differences relating to user confidence/behaviour and hardware interaction.
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::When designing for special populations, the capabilities of the user must be taken into account. An interface for such a population should be as straightforward and easy to learn as possible.
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=See Also=
:# [http://en.wikipedia.org/wiki/List_of_human-computer_interaction_topics List of HCI Topics]
=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]
:# [http://en.wikipedia.org/wiki/Gender_HCI Gender HCI]

HCI - Accommodating human diversity

2009-11-23T16:12:36Z

Livierja: /* Human Properties */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Gender'''
::Males and females tend to interact differently with computers; ideally, interfaces should be designed to be gender-neutral. Study in this field has uncovered gender differences relating to user confidence/behaviour and hardware interaction.
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::When designing for special populations, the capabilities of the user must be taken into account. An interface for such a population should be as straightforward and easy to learn as possible.
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T15:47:09Z

Livierja: /* Human Properties */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. Visual considerations are discussed above.
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
::
:*'''Other Conditions'''
::Epilepsy (covered above) is one example of a condition that does not fall under any other heading. Any other such common issues in the user population must be accounted for.

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T15:41:14Z

Livierja: /* Linguistic Context */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*'''Equitable use'''
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*'''Flexibility in use'''
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*'''Simple and intuitive'''
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*'''Perceptible Information'''
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*'''Tolerance for Error'''
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*'''Low Physical Effort'''
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*'''Size and space for approach and use'''
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*'''Expert'''
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*'''Occasional'''
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*'''Novice'''
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*'''Frequency'''
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*'''Volume'''
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*'''Colour Contrast''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*'''Colour Blindness''' [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*'''Animated Visuals'''
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*'''Resizing'''
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*'''Visual Queues'''
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*'''Photo sensitivity'''
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*'''Visual Conditions'''
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*'''Previous knowledge'''
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*'''Symbols'''
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*'''Terminology'''
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*'''Traditions'''
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*'''Imagery'''
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*'''Training Techniques'''
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
Additionally, understanding the natural language of a region is vital to the system's usability. If the users cannot understand the interface, the system will not function as they wish.

Some example considerations:

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Grammar and Syntax'''
::Ensuring proper grammar, spelling, punctuation etc. is vital for the interface's usability.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*'''Slang'''
::Use of slang should be avoided, similarly to idioms, as it is too easy to misunderstand without proper context.

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complicated visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:54:10Z

Livierja: /* Linguistic Context */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*Novice
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==

'''I SEE YOU DAVE'''

:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*etiquette
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complication visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:53:22Z

Livierja: /* End User Diversity */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequent use of shortcut keys and command line input.
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*Novice
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
:*'''Multi-Language Support'''
::If an interface is to be employed in a region with multiple dialects, the interface should support multiple languages for its display, or make use of common visual cues. Switching between supported languages should also be as intuitive as possible. For example, the option to change the current language setting to French should not be displayed only in English.
:*'''Character Variation'''
::Some languages may share characters and/or words that are visually the same, but pronounced differently. For the sake of ease-of-use it is important to ensure all textual information is grammatically correct.
:*etiquette
:*'''Idioms and Metaphors'''
::Different languages and cultures may have phrases or words that hold a unique meaning in a specific context and not well understood by others. When designing an interface textual elements should be written in plain language (whatever that language may be) without the use of common expressions or sayings.
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complication visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:51:13Z

Livierja: /* Human Properties */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties. This type of user likely makes frequency use of shortcut keys and command line input.
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks.
:*Novice
::User is new, requires as much feedback, help files, and hints as possible. Visual representation of objects and the use of natural language is important for this type of user.
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
:*language character variation
:*etiquette
:*idioms/metaphors
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. Interfaces likely to be utilized in emergency situations should be as simple and direct as possible, whereas educational software interfaces can be more complex and entertaining, as they must hold the users attention in a meaningful way.
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
::Accommodations for physically disabled users should be provided wherever possible. This could include anything from larger buttons to voice activation and touch-screen interfaces.
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complication visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:41:50Z

Livierja: /* Platform Type */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks
:*Novice
::User is new, requires as much feedback, help files, and hints as possible
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
:*language character variation
:*etiquette
:*idioms/metaphors
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. [EXPANDING]
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==
::An interface must be designed with the actual device it will run on in mind. An interface designed to run on a standard desktop, for example, would likely be unusable on a mobile device such as a cell phone. In addition, time-sensitive systems (the interface for a plane's avionics suite, say) should provide information as directly as possible, rather than relying on complication visuals which may slow response time.

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:26:47Z

Livierja: /* Designing for context */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks
:*Novice
::User is new, requires as much feedback, help files, and hints as possible
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

avoid cultural symbols, use universally understood metaphors. Ex: Don't use stop light. They aren't the same everywhere.
other stuff like globalization issues that it talks about pg 27 as well maybe

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==
It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
:*language character variation
:*etiquette
:*idioms/metaphors
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. [EXPANDING]
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

==Platform Type==

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]

HCI - Accommodating human diversity

2009-11-23T03:21:06Z

Livierja: /* Designing for context */

As graphical and general processing capabilities improve, the growing need for research into human computer interfaces becomes more evident.
Designers are expected to provide a transparent interface to the core of their software that can facilitate work for all levels of users.
When designing a user interface many aspects of human diversity must be taken into account. Depending on the purpose of the software, designer must take into account factors such as but not limited to:

:*Age
:*Race
:*Physical Attributes/Disabilities
:*Mental Disabilities
:*Educational Background
:*Computer Expertise
:*Geographical Location
:*Cultural Background 

=Universal Design=

In general, universal design is a cross discipline approach to design that helps create products that are usable and effective for everyone. The design principles for Universal Design are as follows.[http://www.design.ncsu.edu/cud/ R1]

:*Equitable use
::Use of the object or software must be as "fair" as possible. This means that regardless of user type, they can all perform the same actions and receive the same benefits form the product. This however seems to be a fairly lofty goal with regards to complicated software. Instead this can be interpreted in the sense that regardless of the type of users, given a reasonable amount of time, they will gain the same benefits from the product. Software and it's interface should provide all the necessary tools to aid beginners in reaching an adequate level competency within a reasonable amount of time.

:*Flexibility in use
::The design should be able to accommodate a wide range of users based on factors such as preference and ability. For example, expert users should not be held up by an interface designed for beginners, likewise, a beginner should not be expected to use expert style interactions.

:*Simple and intuitive
::Use of the product is easy to understand, regardless of the user's experience level or background. Keep the interface simple by reducing unnecessary complexity, and be consistent with user's expectations. Offering prompt informative feedback will eliminate frustration as well as reduce learning times.

:*Perceptible Information
::Necessary information should be effectively communicated to the user regardless of any disabilities the user may have. Any feedback given to the user should have adequate contrast against the surrounding information. In general elements should be distinguishably different to clearly convey the message of difference or importance to the user.

:*Tolerance for Error
::When designing an interface, or functionality of software, designers should always strive to minimize faults or error that may be caused through inadvertent actions by the user. There are many techniques to help with this issue. Grouping objects based on functionality or confirmation of action are useful tools. It would be unwise to say, place the "load" and "delete" buttons side by side.

:*Low Physical Effort
::Although this principle is stated for real world objects, it carries over quite well. Users should not have to dig through multiple menus or perform an excessive amount of actions to obtain a given functionality. The number of actions required to perform a task should be fairly proportional to how often that action is used. Very common functionality should be readily available to the user at all times, or be made readily accessible with ease.

:*Size and space for approach and use
::Once again, although this principle is stated for the real world, it applies very well to HCI. A simple interface is an efficient interface. Important elements should be easily visible regardless of the user's physical abilities. Positioning of the elements should also be intuitive. Grouping of elements and clear separation of the interface based on functionality can help with this.

==8 Golden Rules==
The 8 Golden Rules proposed by [http://en.wikipedia.org/wiki/Ben_Schneiderman Ben Shneiderman] also provide a very good basis when thinking about interaction design.[http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html R2] 
<ol start="1">
<li>'''Strive for consistency'''</li>Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.
<li>'''Enable frequent users to use shortcuts'''</li>As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.
<li>'''Offer informative feedback'''</li>For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.
<li>'''Design dialog to yield closure'''</li>Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.
<li>'''Offer simple error handling'''</li>As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.
<li>'''Permit easy reversal of actions'''</li>This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.
<li>'''Support internal locus of control'''</li>Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.
<li>'''Reduce short-term memory load'''</li>The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.
Although some of these principles cross over, they lend themselves to universal design with regards to software.
</ol>

==Interaction Styles==
There are a set of at least five primary interaction styles:

<ol start="1">
<li>'''Visual Representation'''</li>A visual representation of the world of actions which the user can manipulate, such as desktop icons. Allows easy learning and avoids errors, but is difficult to program and may require additional graphics displays and devices.
<li>'''Menus'''</li>Menus can help the user to navigate through all available options, most likely progressing in a nested fashion. Shortens learning and allows easy support of error handling through structured decision making, but may deter frequent users and presents a danger of many layered menus leading to confusion.
<li>'''Fill in the blanks'''</li>Suitable for data input where a menu may be inadequate or too complex. Provides simple data entry and requires only modest training, however this method can consume a large amount of screen space.
<li>'''Command prompt'''</li>Using a command line prompt provides easy and fast access to functions for advanced users. Novice users, however, will find this interaction style to be quite hostile. Very flexible but has poor error handling.
<li>'''Natural Language'''</li>Natural language can be used easily by typing commands. If clarification is needed it can be done in that language. Relieves burden of learning correct syntax or command language, but requires clarification dialog and is unpredictable.

A combination of any of the above may also be useful.
</ol>

=Accessibility=
------------------------STUFF TO COVER
Concerns

Age: Font size , Macular Degeneration

Physical Disabilities: [http://en.wikipedia.org/wiki/Color_blindness Color Blindness] Optical Seizures

Education: Mental Model of the user, What we can assume the user will understand - Time to learn
Language: Terminology, Certain words may have different meaning
-----------------------DELETE IF YOU DONT NEED

When creating a Human Computer Interface, it is important to take a step back and consider who is going to be using it. The physical, mental, and cultural state of the end user will vary, and knowing how this could effect how they perceive your interface is critical. Addressing these different characteristics of the possible end user, there are several categories which designers need to consider.

==End User Diversity==
As stated in Principle #1 of Human Factor Considerations in Human Computer Interface, it is necessary to recognize the diversity in the abilities of the user. The ability of the user can be categorized into three levels of skill types:
:*Expert
::User that uses the computer and applications as part of regular job duties
:*Occasional
::User that is not a frequent user and may need prompting from time to time to accomplish computer based tasks
:*Novice
::User is new, requires as much feedback, help files, and hints as possible
By knowing who your end users may be for your interface, you may have to take into account all three users, or specifically make it for one of the three types of users.

==Audio Considerations==
Another factor that must be considered in the diversity of the end user is their hearing. Users will have varying ability to hear or recognize audio output from an interface.
:*Frequency
::As both men and women grow older (to a greater extreme men)[http://www.agingsociety.org/agingsociety/pdf/hearing.pdf R3] we lose the ability to discern different frequencies of sound, especially at higher frequencies. The interface must take into account that the end user may have a smaller range of identifiable sounds, and make any audio queues within the audio range of any user.

:*Volume
::It is also necessary to have any of the audio output from the interface to be loud enough for the user to understand. It may be necessary to have the volume of any audio outputs to be variable to allow any user comfortable audio output.

==Visual Considerations==
[[Image:macular_degeneration.jpg|frame|Age related Macular Degeneration]]
It is also a necessary requirement that any user is able to visually understand what is displayed on the screen. Some factors that need to be considered are:
:*Colour Contrast [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::To make any text displayed to be as legible as possible, it is necessary to have sharp contrast between background and text. The best suited background colours are achromatic colours: black, white and grey, with the textual colours fall within the middle colours of the spectrum: yellow, green and orange. Red, blue and violet are on the extremes of the human visual spectrum so our eyes are not as sensitive to them, making them difficult colours to contrast with others.
:*Colour Blindness [http://www.colorsontheweb.com/colorcontrasts.asp R4]
::A portion of users may suffer from [http://en.wikipedia.org/wiki/Color_blindness colour blindness] and be unable to detect slight variations in colour, making certain aspects of an interface unreadable to them. This can be avoided by using a sharp contrast between background and text. As well, for this reason an interface should not rely on visual cues alone.
:*Animated Visuals
::Objects on a screen that are non static, being blinking, moving, updating etc. can cause the users that are screen read challenged difficult in reading or understanding the object. These objects must have the option to be frozen or paused for the user to understand its message.
:*Resizing
::For users with limited visual ability, it is necessary to allow the user to change the size of the what is being displayed. This could include changing font sizes, resizing object sizes, or any other method to make an object understandable for a user with diminished visual ability.
:*Visual Queues
::Timed pop up menus or hints that are not read and understood before they hide again also need to be considered. If the end user has a problem understanding the message before it disappears for any reason, be it age or visual impairment, then the queue needs to appear for a longer duration to the user.
:*Photo sensitivity
::[http://en.wikipedia.org/wiki/Epilepsy Epilepsy] is a neurological disorder characterized by recurrent convulsions. [http://en.wikipedia.org/wiki/Photosensitive_epilepsy Photosensitive epilepsy] is a form of epilepsy in which seizures are triggered by visual stimuli such as flashing lights or moving patterns. Epilepsy occurs in approximately 1 in every 200 people and photo epilepsy occurs in approximately 1 in every 4000 people. About 96% of people while photo epilepsy are sensitive to light flashes between 15-20 flashes per second. For this reason blinking or updating of a CRT screen should be avoided, as this can cause flickering between 4 and 59 Hz and will likely trigger a convulsion.
:*Visual Conditions
::For users with limited vision due to age it is important to take into account the position and size of objects, text and visual cues. For example, [http://en.wikipedia.org/wiki/Macular_degeneration macular degeneration] is a condition resulting in loss of central vision. Should the software be intended for the aged, positioning the locus of control to the left or right of the screen may prove to be a benefit.

=Designing for context=

avoid cultural symbols, use universally understood metaphors. Ex: Don't use stop light. They aren't the same everywhere.
other stuff like globalization issues that it talks about pg 27 as well maybe

When designing a system for widespread use, it is important to understand the region an interface is being implemented in. When an interface is contextually valid, it reduces the chance of the system being misused due to simple misunderstandings in language and visuals.

==Cultural Context==

It is crucial to understand the culture and customs of the region a system is to be implemented in. Doing so can greatly reduce the amount of learning time needed by users of the system.

Some important aspects to consider:
:*Previous knowledge
::It is possible that a previous method of complete the task the software is being designed for existed for some time. The design of the previously used equipment should be taken into account in order to make the transition to new software as easy as possible.
:*Symbols
::Avoid use of symbols and/or colours that have some cultural significance in the area the interface is being designed for.
:*Terminology
::Certain terms and phrases may have different meanings to different cultures. Instructions and commands should be made as plainly and clearly as possible.
:*Traditions
::Certain cultures may have standing traditions related to either a previous edition of software, or to an area where new software is being implemented. An interface should be designed to be as consistent as possible with these traditions.
:*Imagery
::Use universally understood visual metaphors, as different cultures may have different meanings for the same image. For example, a red traffic light may mean stop to one person and not to another.
:*Training Techniques
::Consider the mental strategies which will be adopted by operators and the resources required in terms of background knowledge. These resources should be made clear and readily available to minimize the learning curve.

==Linguistic Context==
:*language character variation
:*etiquette
:*idioms/metaphors
:*slang

==Human Properties==
:*'''Handedness'''
::This mainly comes into play when designing physical interfaces – control panels, for example. An interface should always be designed such that both right handed and left handed operators can make use of the system with minimal inconvenience.
:*'''Age'''
::Note that the senses, particularly hearing and vision, degenerate with age (see above). A good interface takes this fact into consideration, and provides utilities to deal with decreasing physical faculties (i.e. increased volume, text size).
:*'''Intellect (Educational background, profession, experiences)'''
::For certain applications (for example, control systems interface in a nuclear reactor), a certain baseline level of education can be assumed. However, in general, it is poor design methodology to assume that the end user will have the same education, training, or life experience as the designer. Interfaces should be designed in such a way that they do not require a great deal of specialized knowledge to use.
:*'''Emotional/Mental Characteristics'''
::When designing for a specific demographic, aspects such as attention span, emotional state, and motivation must be taken into account. [EXPANDING]
:*'''Culture'''
::When deploying an interface in an unfamiliar region, it is imperative that none of the symbols used be offensive in the local culture. As well, no element should be incomprehensible to the locals. Idioms and colloquialisms are to be avoided for this reason. An outside specialist may be required to advise on this aspect.
:*'''Size/Spatial Aspects'''
::The height, weight, and reach of the end-user must be taken into account. Interfaces should be designed to accommodate a range of physiques.
:*'''Visual Capability'''
::Conditions to be considered include blindness, near/farsightedness, and colourblindness. [EXPANDING]
:*'''Auditory Capabilities'''
::Deaf users should be taken into account. If the interface relies heavily on sound, accompanying visual indicators should be included.
:*'''Physical Disability'''
:*'''Mentally/Learning Disabled'''
:*'''Other Conditions'''
::Epilepsy (covered above)

=References=
:# [http://www.design.ncsu.edu/cud/ Center for Universal Design]
:# [http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html 8 Golden Rules]
:# [http://www.agingsociety.org/agingsociety/pdf/hearing.pdf Hearing Loss]
:# [http://www.colorsontheweb.com/colorcontrasts.asp Colour Contrasts]