Usability is a term used to denote the ease with which people can employ a particular tool or other human-made object in order to achieve a particular goal. Usability can also refer to the methods of measuring usability and the study of the principles behind an object's perceived efficiency or elegance. The field of usability is often felt to be related to user-centered design, interaction design and experience design.
Most abstract information spaces work poorly in 3D because they are non-physical. If anything, they have at least a hundred dimensions, so visualizing an information space in 3D means throwing away 97 dimensions instead of 98: hardly a big enough improvement to justify the added interface complexity.
It's hard to imagine a form that could be simpler: two fields, two buttons, and one link. Yet, it turns out this form was preventing customers from purchasing products from a major e-commerce site, to the tune of $300,000,000 a year. What was even worse: the designers of the site had no clue there was even a problem.
Fare Accessibilità significa avere delle conoscenze tecniche, avere dimestichezza con Standard e Raccomandazioni del W3C. Ma non solo. Significa conoscere il target dell´Accessibilità, erroneamente ed ingenuamente precluso ai soli disabili. Significa conoscere chi sono le persone disabili, che prima di essere disabili, sono Persone. Sono coloro che vivono sulla propria pelle ogni giorno le conseguenze di scelte strategiche sbagliate di coloro che hanno il potere, con un sì o con un no, di creare o abbattere le barriere tecnologiche che ostacolano il libero accesso alle informazioni ed ai servizi online.
Study participants searched websites for background information ranging from company history to management biographies and contact details. Their success rate was 70%, leaving much room for usability improvements in the 'About Us' designs.
How you ask a question strongly determines the type of answer that you will obtain. For effective documentation reviews, whether they are conducted internally or externally as part of usability testing, it's important to use precise questions that will provide concrete information on which to base revisions. This paper proposes an approach to obtaining useful feedback that emphasizes negative, 'what did we do wrong?' questions. This approach focuses limited resources on areas that need improvement rather than areas that already work well and that don't require immediate improvement.
The purpose of this document is to provide information and resources for those interested in learning more about accessibility issues and current and next-generation information systems. The current focus of this document is on the National Information Infrastructure (NII), sometimes known as the 'information superhighway.' This document contains both information presented at a very introductory level and information which is more technical in nature. Wherever possible, all of the technical discussions are broken out and presented separately, so that readers may course through the material at a level which is comfortable to them, and which meets their information needs. This is a living document which will be continually revised and added to as more information is collected and as the efforts in the area of research, development, and public policy continue to evolve. The most recent form of this document can be found on the Internet via our ftp, gopher, or WWW servers. All of these are located at: trace.wisc.edu The document can be viewed on-line or downloaded in one of several forms to facilitate accessibility.
The idea of accessibility is to make websites (or other things) more easily usable by people, most frequently specifically “people who are disabled”. This is emphatically not just about using alt tags (note: always call them tags, it annoys the purists). Accessibility is not just about the blind.
An article discussing how the needs of all users must be addressed, including the varying level of computer literacy and competence. It is conjectured that building sites which address the specific needs of these audiences will benefit the general public as a whole.
Frontend has recently completed the delivery of the first version (1.1) of the Irish National Disability Authority (NDA) IT Accessibility Guidelines. In the course of our work for the NDA over the last year we’ve talked to a wide variety groups and individuals who have an interest in accessibility and as a result of their input, our approach has shifted a little. Here’s what we found out.
In trying to build accessible products, it is sometimes difficult to find key components. This is particularly true when building prototypes or coordinating small volume productions. This resource listing is provided to assist people in finding sources for key accessibility components such as accessible telephone handsets (for use on kiosks, etc.), voice technology products and other accessible components. It is maintained on an 'as we find it basis.' In other words, when we locate particular components or they are brought to our attention, we wll include them here.
This paper identifies challenges for a user–centered design process with respect to infusing accessible design practices into electronic and information technology product development. Initially, it emphasizes that when user–centered design is paramount and concurrent with accessible design, electronic and information technology can be accessible for all. Next, it provides an overview of the Americans with Disabilities Act (ADA) Section 508. Last, it provides basic accessible design heuristics that can be integrated into the design process. It concludes with recommendations for a paramount and concurrent user–centered design approach to product development.
The natural language interface (NLI) is a module that allows the user to access the information stored in the underlying database by typing requests expressed in a natural language.
Worldwide, there are more than 750 million people with disabilities and this number is increasing. It is critical that the Web be usable by anyone, regardless of individual capabilities and disabilities since the World Wide Web is supposed to be a place where everyone has the ability to find information or shop. Website designers should be sure that the web pages can be accessible by everyone no matter who or where. Accessibility, a category of usability, is a software product's ability to be used by people with disabilities, such as motion impairment.
Focus on your users, all of them. Learn from mistakes currently made on the Web. If a user can't fill out a form, they can't buy anything from your site. People turned away by unusable sites will probably try a competitor's site. Don't be the site that turned people away. Make your Web site as usable and accessible as possible. It's the business savvy thing to do. It's the right thing to do. If you don't, someone just might force you legally to do it or threaten to sue.
The Principle of Least Astonishment, in shorthand, encompasses what we, as designers, must achieve to ensure consistency in our designs. Consistency is a fundamental design principle for usable user interfaces. But the thing that astonishes me is that it’s actually necessary to explain this principle. Surprise implies the unexpected. Of course, users want the response to a given action to be what they expect; otherwise, they would have done something else. In user interactions, the unexpected is pretty much the same as the unwanted. Surprise usually implies something bad rather than something positive—unless users already have such dismally low expectations of their software that they might think, Wow! It worked. I’m so astonished.
I have judged a fair number of national and international product design competitions (five in the past three years alone) and each has made the same procedural mistake: products are assembled and categorized, judging criterion are devised, reputable judges are assembled, and yet we judges never see or touch the products in person. Instead, we receive a set of written documents describing each product, its intended function, and its design process. Imagine an art contest conducted by email and you get the gist of what's going on out there.
One of the most common implementations of menu views has been the “side drawer,” “basement,” or “side menu” made popular in apps such as Facebook and Path. When a user taps the “Hamburger” icon to open a side menu, the main screen slides to the right (or left in some implementations) to reveal another screen below.
One of the things I noticed about circus performers was that they are always practicing and always learning. Why? Because audiences demand acts that delight them. Therefore, to keep their routines fresh and interesting to themselves as well as to the audience, performers are always learning something new, something more difficult, or something fresh. You, as a technical communicator, need to have the same passion for adding new tricks to your performance. A great place to start is with usability: design, testing, and analysis. Why? If you make sure that your documents are well written, doesn’t that automatically make them usable? Of course not. Well-written documents are simply that—well written. Your prose may be technically accurate, clear, and succinct, but if people can’t find it, or don’t know about it, or if it documents a hard-to-use product, then no one will use it. As Judy Glick-Smith says: 'It’s communication, not literature.'
Many of the 'PDF Usability Crimes' Nielsen cites have nothing to do with Acrobat or PDF but are the result of poor design choices. Most of same arguments about poor navigation, large file sizes, and excessive text blocks can be used to describe poorly designed HTML as well. There are some very valid reasons for using PDF's online as opposed to HTML.
Usability is the combination of effectiveness, efficiency, and satisfaction with which the users accomplish defined goals in a given environment. User-centered documentation matches the users' mental model, thereby helping the users find information they want quickly and easily in their hour of need. The list of documentation usability criteria is fairly subjective at this time, and various opinionated discussion groups have contributed to this. Usable documentation is based on a deep understanding of the users' tasks, and this understanding can only be gained through interviewing representative users. Applying information architecture techniques, the content within documentation should be properly chunked so that the users can assimilate the information properly. Procedural guides should have a well-defined and searchable index that enables users to connect key application terms to their correct context. User-friendly documentation is always succinct, but never at the expense of omitting critical/useful information. It should be developed using a structured process so that it starts with the big picture and gradually adds lower level of details, addressing the needs of every unique group of users. Finally, the documentation must be tested among a representative group of users, and their feedback should be incorporated to make sure that it has met all of the major usability criteria.