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.
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.
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.
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.
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.
Cognitive friction results in a digital divide between the software development community and software users. The digital divide, in turn, has a direct correlation with the usability of the application: how well can the software users learn and use the application or the product to perform their tasks and accomplish their goals. Today's Technical Communicators can help bridge this divide and reduce cognitive friction by applying industry-acclaimed usability techniques to the documentation they produce toward accelerating user acceptance of the product. Less cognitive friction means better user adoption that results in fewer calls to tech support, higher customer satisfaction, and in the long run, better brand loyalty.
An increasing number of STC members now have usability programs as part of their job responsibilities, although they’re not always full-time usability specialists. Many STC members have been performing usability activities for several years.
The concept of an affordance was coined by the perceptual psychologist James J. Gibson in his seminal book The Ecological Approach to Visual Perception. The concept was introduced to the HCI community by Donald Norman in his book The Psychology of Everyday Things from 1988. There has however been ambiguity in Norman's use of the concept, and the concept thus requires a more elaborate explanation.
Here they come. Nightmare web sites that, from a usability perspective, are horrid monsters. When you're tired and in a hurry, you want a web site to quickly and easily provide relevant content to you, so you can solve a problem or perform some task. Discover common hideous impediments to web usability. WARNING: Not for the faint hearted!
It doesn't replace information architecture. And it's really not a school or brand of information architecture. Findability is about recognizing that we live in a multi-dimensional world, and deciding to explore new facets that cut across traditional boundaries.
For the most part, information architects are communicators and strategists. While others merely tolerated the mishmash of responsibilities, they relished it. Designers often put up with having to write HTML but jumped at the chance to 'just do design.' Programmers were forced to meet with clients and work on strategy, but all along probably wanted to just write code. When these two ends of the spectrum split off, the empty middle was a perfect place to be. At the same time, there was an increased (but still hidden) need for information architecture. As the average web project process matured, more problems arose. Formal documentation was needed, business objectives were taking on increased importance, and, as the size increased exponentially, information organization became a much more important role. (The fact that this evolution took place during the 'dot.com fallout' is not insignificant, as this led to the placement of web projects under the same microscope as other business endeavors.) Some of these positions could be filled by existing disciplines; project managers, business analysts, and usability specialists transitioned from 'traditional' work and were added to web teams. Still, there was something missing. The connection between 'the big picture' (business strategy, high-level user tasks, basic structural architecture) and the nitty-gritty (categorization, labeling, bottom-up information hierarchies) often wasn't being made. This is where information architects fit in.
Agile methods aim to overcome usability barriers in traditional development, but pose new threats to user experience quality. By modifying Agile approaches, however, many companies have realized the benefits without the pain.