Site MapUser Experience for a Better World | Each month Dr. Eric Schaffer answers selected questions on usable interface design. | Recent Questions |
| Archived questions and answers about ... |
|---|
|
August 16, 2007 – submitted by Boniface Okila of Kenya |
|
| Question: Can you explain the constraints of human aural serial processing and the potential of human visual parallel processing in a multimedia-based system in relation to usability considerations? | Eric's response: Sure. Put the person in a car blindfolded and have a friend try to tell him what he would be seeing so he can drive. NOT "turn left". But say "the speedometer is 30mph. The road is moving to the right. There is a car close in the rearview mirror." Etc. With vision, numerous displays can be accessed in any sequence needed, just based on eye movement. There is no need to try to memorize the content and context because it is always available. There are some more subtle issues that relate to "sensory memory" (also called "iconic memory"). This is like an image (or sound track) that stays in your head for a very short time. Look it up on the net if you like. |
| Top | |
August 16, 2007 – submitted by Joann Schissel of West Des Moines, IA |
|
Question: I think I understand the concept and differences of globalization, localization, and internationalization. Can you please explain this formula? G11N=I18N+L10N. Also, do you have any recent statistics / research about English / non-English uses among internet visitors? |
Eric's response: Here is an answer from Apala Lahiri Chavan. She is head of Asian operations at HFI and a leading light in cross cultural issues. * * * * * * * * I18N Internationalization: A development process of creating a base design to support various human languages and to behave in a culturally-sensitive manner. L10N Localization: The process of making changes to a internationalized product to make it usable and viable in a particular market. Technical L10N: Technical aspects of adapting a product to a local market, e.g. double-byte conversion, OS support, etc. National L10N: Making the product behaviors / designs appropriate for a national setting, e.g. written language, punctuation, formats, etc. Cultural L10N: Beyond functionality and correct language – cultural specific values, tastes, and conventions need to be addressed. G11N Globalization: The design, development and creation of fully localized products to meet the cultural and linguistic requirements of a particular market. G11N =I18N +L10N |
| Top | |
July 23, 2007 – submitted by Diane Albert of Altoona, PA |
|
Question: The topic of Section 508 compliance has been floating around our office. We are not currently marketing software to any Federal folks, only county or state agencies. I think we may need to address this before we choose to be competitive on any Federal contracts. I've read the list of things that compliant software should do, but I'm unsure what each of those items translates to when designing an interface. Could you discuss things that I should specify in my functional design specifications, including recurring items that could be listed globally as a guideline? I'm also seeking any articles that I can continue to reference. I don't think a compliant application is much more difficult to design, but I think there is more attention to detail until both designers and developers become familiar with the concepts. Thanks! Diane |
Eric's response: Good to hear you have interest in accessibility. I think companies are increasingly ignoring the topic, with the exception of companies that work for the Feds. In a way that makes sense from a business viewpoint. I have seen situations where it would be cheaper to send a limo to pick up the dozen blind users and bring them to the bank. But at the same time one really does hope we can make more inclusive applications. I think that will happen when the bulk of people get the idea of using web pages through their phone, with a voice interface. That will solve the problem nicely for the visually impaired anyway. Section 508 is pretty well documented and WC3 also has good guidelines. Most of the basics are really coding conventions; NOT interface design conventions. Of course if you want to go beyond the letter-of-the-law and make the accessible interface USABLE, then that takes some serious work. At least DO try a few readers yourself. You will be shocked at how bad they are for using sites. |
| Top | |
July 23, 2007 – submitted by Julius Oyeleke of Windhoek, Namibia |
|
Question: Hi Eric. Please I would like to ask you about ATM usability. 1) What are the new enhancement that need to be incorporated into the ATM system (Automatic Teller Machine). Thank you for the the assistance. Julius |
Eric's response: The ATM machines have been having more and more functionality added to them. The challenge is that with increased functionality comes increased complexity. So the usability work gets much tougher. At the same time ATMs are progressively being moved into more and more emerging markets and pushed to the "bottom of the pyramid" (poor users). We have often found that poor users LOVE the ATMs because they can avoid the denigrating attitude of bank employees. So that is a plus. But then you have to design for the more limited skills of this population. A cognitive walkthrough of ATM operation is useful. Though I would be certain to also do usability testing. Just in case YOUR cognitive ideas don't match the actual users. Research on ATMs should follow the guidelines of the publication they are planned for. For example you might see the American Psychological Association's style manual. Without other input, they probably have the best structure for academic papers. |
| Top | |
July 23, 2007 – submitted by Dafna Mardix of Israel |
|
Question: The client of a new application for Clinics Management would like to come up with a concept of a touch screen. There are lots of good reasons why it should be done in the clinic itself, when the user has his hands full, but the application needs to control the clinic, which means that the manager and secretary should use it: add, edit and control more then basic tasks including writing input. Could you please direct me to good material on the subject and also give your opinion? Thanks a lot. |
Eric's response: Hmm, I think you have two key issues. First, typing text on a touch screen is impractical beyond a few characters for keys and such. Second, a touch screen is good to avoid when people may have sticky material on their hands. I would think a touch screen could work for remote terminal to check some data quickly. But for back office operations it won't work well at all. |
| Top | |
May 30, 2007 – submitted by Maja Mkinga of Dar Es Salaam, Tanzania |
|
Question: I want to design a try out model of a user interface for blind people. Could you please tell me the important principles to consider when designing one? |
Eric's response: If you are designing a Web interface for use with a screen reader, then first look at the W3C accessibility guidelines. These are basic design and programming conventions that make it possible for a screen reader to access the interface. However, designing for a screen reader by no means ensures a usable interface. This takes real attention to the design. You can start by being sure to test the interface with a screen reader. Even just using one yourself will help. If you are designing in a different environment you will be designing a non-visual interface. This probably does NOT mean a Braille interface (actually only a small fraction of blind users can read Braille). Instead, you will probably have a voice interface and apply the extensive literature on voice applications. |
| Top | |
April 2, 2007 – submitted by Nitin Mehta of Bangalore, India |
|
Question: Please help me to understand what are the constraints we have to keep in mind while designing the User Interfaces of application or Web sites for different geographical locations. |
Eric's response: Constraints are not so much the issue. The issue is cultural diversity. This includes differences in decision making (in the USA decisions are taken more by individuals than you are used to). Differences in social structures (in the USA families are not as tightly knit and have less impact on decision making). Differences in style of communication (Americans talk louder and are more direct than you are used to, they won't understand subtext that is VERY obvious to you). There are also major differences in physical environment (in America the power stays on and does not fluctuate much, and there is no monsoon). There are also differences in business rules and data conventions. Oh, and of course language! But NEVER think that translation of text alone is adequate localization to a culture. It rarely is. |
| Top | |
March 12, 2007 – submitted by Harikrishna VP of Kerala, India |
|
Question: I have a doubt regarding, what date format should be followed for a international software product. Is it YYYY-MM-DD or DD-MM-YYYY. Can you please help me out. Thanks in advance. |
Eric's response: Sure, I'll help. When you DISPLAY a date (in display only situations) then you can use 12 SEP 2008 and feel very safe. If the data is to be entered, or entered and displayed, it is harder. One very good method is to provide drop down fields in the '12 SEP 2006' format. This is good for a mouse-primary interface, but can be too slow for heavy data entry. If dropdowns are not advisable then it is best to adapt to the local convention of the user. Microsoft does a fine job of doing this adaptation. So the USA uses MMDDYYYY and Europe DDMMYYYY (etc). The YYYY-MM-DD is easy to sort inside the computer, but the only real value for users is that it tends to equally confuse everyone. I would avoid this "international" format as, after all, we really don't have any international users. Everyone operates from their own cultural context. |
| Top | |
March 2, 2007 – submitted by Berit Molander of Oslo, Norway |
|
Question: Can you recommend books on perception of colours in different cultures? |
Eric's response: Surya Vanka from Microsoft wrote one, but we have not been able to get a copy. If you find where to get one, please let me know. That is the only book we know about. |
| Top | |
January 30, 2007 – submitted by Carol Hall of Connecticut, USA |
|
Question: Hi, I'm an instructional designer interested in how companies are using MS Word readability/grade level scoring. I realize these are not a guarantee of understandability, however, it's quick and easy to do. Is it valuable to do? What grade level works in an insurance company for example? Thanks. |
Eric's response: Calculations of reading grade level (RGL) are VERY valuable when you need to point out to someone that their writing is awful. I remember analyzing some legal documents and finding that you needed four doctorates to read them comfortably. It made an impression all the way to the executive level. The RGL calculations are not precise. To REALLY know how difficult the text is to read you need to consider how common a word is. The RGL calculations assume a short word is easier, but if the short word is uncommon it might be much harder then a long common word. In terms of target RGL, it is a question of your user population. A call-center population may need a lower RGL target than the lawyers in the legal department, or the underwriters. (Sorry I have to do math...) |
| Top | |